Part of WhatsApp automation
No more month-old CSV exports
A CSV you exported last month is a customer list that is wrong in exactly the ways that matter — the people who left, the numbers that changed, the ones who joined since. Sync pulls the list from your system instead, on a schedule you set.
- Pulled from your own system
- On a schedule you set
- Never overwrites your list
Your customer list, without the export
- Pulls contacts from one of your own HTTP endpoints, on a schedule or the moment you ask it to.
- Maps each record into a contact using a mapping you configure, and pages through as much as your endpoint returns.
- Tags every row the sync created, so a contact you added by hand is never swept away by it.
- Deactivates contacts that have disappeared upstream on a full sync, rather than leaving you calling people your CRM no longer has.
- Keeps the credential encrypted, rotatable in one place, and out of every log and error message.
- Gives you a dry-run test and a delivery log, so a broken sync is something you can see rather than something you infer.
Set up once, then it runs
- Save your endpoint as a named read connector under Integrations, with its credential alongside it.
- Configure the mapping — which field in your records is the phone number, the name, and anything else worth carrying.
- Test it. The dry run shows you what a record would become before anything is written.
- Set the schedule, or run it on demand. Synced contacts then feed campaign audiences, segments and customer profiles like any other contact.
Want to see this doing your job, with your prices?
Ask on WhatsAppThe things this does not do
Every product page in this market lists capabilities. This is the other half. If one of these is a dealbreaker, we would much rather you found out on this page than in month two.
- It is your REST endpoint, not a named integration. There is no one-click Salesforce, HubSpot or Zoho app — a Zoho CRM worked example ships in the dashboard, but you are configuring an endpoint, not installing a connector from a marketplace.
- The sync only reads. Kooday does not write contacts, deals or notes back into your CRM, and deal write-back is not built.
- Nothing is looked up live. Contacts are synced ahead of time and read locally, so Kooday never calls your system mid-call to work out who is ringing. The one deliberate exception is a tool you give your assistant to fetch something during a conversation.
- A full sync deactivates upstream-deleted rows rather than deleting them, so the history attached to that person survives. If you need hard deletion, that is the erasure path, not this one.
- Sync needs two things on your plan, not one. Contact sync itself, and API access — because the connector that points at your endpoint is a generic REST connector, and those are governed by the API product. Check both are on your plan before you count on it.
What people ask us
What happens to contacts I added by hand?
Nothing. Sync-created rows are tagged as sync-owned and a sync only ever touches those. A contact you typed in, or imported from a CSV, is invisible to it.
Does it work with my CRM?
It works with any system that can serve your contacts over HTTP with a credential — which most can, including via an automation platform sitting in front of one that cannot. What it is not is a pre-built app for a named CRM. If your system cannot expose an endpoint at all, a CSV import is the honest answer.
How current is the data during a call?
As current as the last sync. Kooday deliberately does not call your CRM while a customer is on the line — a lookup that hangs is a call that hangs. If you need live data mid-conversation, that is a tool your assistant calls for one specific question, not the contact system.
What it works alongside
- Customer profiles A phone call and a WhatsApp thread from the same number resolve to one customer with one history. Website chat, Instagram and Messenger visitors get their own records, kept apart from the phone and WhatsApp customer record.
- Outbound calling Voice campaigns over your own contacts, previewed before they dial, paced and windowed, with a brief the assistant follows and a do-not-call list it cannot cross.
- API & events Forty events delivered as signed, retried, replayable webhooks; scoped API keys; inbound hooks so your systems can answer back; and actions your assistant calls mid-conversation.
If this sounds like your week
Would this work for your business?
Message us and say what your week actually looks like. You will be talking to our own assistant — the thing this page describes, doing the job on our side of the conversation.
Plans from ₹99/month.