One customer across phone and WhatsApp

The problem this page addresses is not really a technology problem, and Salesforce’s long-running State of the Connected Customer research is a useful, if slightly humbling, way to see that: 76% of customers expect consistent interactions across departments, and yet 54% say it generally feels like sales, service and marketing don’t share information — a 22-point gap between what a customer assumes about a business that has spoken to them multiple times and what most businesses actually deliver. A small business is not immune to this just because it is small; it is often more exposed, because the same one or two people handle the phone, the WhatsApp thread and the DM, and are trusting their own recall to connect them rather than a system doing it for them.

What the page title promises is narrower than it sounds, and worth being precise about. The unification is number-level: a phone number normalises to one canonical form, so a call and a WhatsApp message from that number resolve to the same person. A website visitor who types a phone number mid-chat has it passed to your team as a contact to follow up on. The visit stays a separate record and is not connected to an existing customer automatically, and a later WhatsApp message or call from that number is recorded under the sender’s own customer record. What it is not, today, is inference on top of that history — there is no layer that reads a customer’s past conversations and derives a trait like “price-sensitive” or “prefers evening appointments” with a confidence score attached. That derived-attribute layer is designed and scoped in the schema, and it is honest to say so rather than imply the platform already reasons about customers the way the identity resolution suggests it might.

Compared against a dedicated CRM, the honest framing runs the other way from most competitive copy: Kooday is not trying to be one. HubSpot’s free CRM tier caps out at two users and one deal pipeline before you pay, with its Starter tier at $7/seat/month (billed annually) unlocking more; Zoho CRM’s Standard edition runs 800 rupees/user/month and its Professional edition, the one that talks about building “end-to-end, dynamic customer journeys,” runs 1,400 rupees/user/month. Both are built to be the system of record for a sales team that manages deals, quotes and pipelines by hand. Kooday’s customer-profile layer is built for a narrower and different job: resolving who is messaging you, automatically, from conversations that already happened across the phone, WhatsApp, webchat, Instagram and Messenger — not replacing the CRM a sales-led business already runs, and for many small businesses, not needing one at all because the assistant is already the front door.

The contact-ownership model is the design decision worth sitting with, because it is the one that avoids the failure mode this whole category is prone to: an automated system quietly overwriting a business’s own customer list with what it observed. Kooday keeps two layers deliberately separate — the contacts you gave it, CRUD-managed, never touched by the platform’s own observations, and the persons/identities the assistant builds from watching conversations across channels. A CRM sync tags what it owns so a scheduled pull can never sweep away a contact you typed in by hand, and it deactivates only what was actually deleted upstream rather than assuming silence means deletion. That separation is slower to build than one merged table, and it is also the reason an import you ran two years ago is still trustworthy today.

Unifying a customer record, three ways

Tool	Price	What it unifies	Built from
Kooday (Customer 360 add-on)	₹1499/mo, bundled on Enterprise	Phone and WhatsApp identity from one number; webchat, Instagram and Messenger visitors stay separate records	Conversations the assistant already had
HubSpot CRM (Free → Starter)	Free (2 users, 1 pipeline) → $7/seat/mo	Contacts, deals, one pipeline	Manual entry and integrations you configure
Zoho CRM (Standard → Professional)	800–1,400 rupees/user/mo	Contacts, leads, multiple pipelines, quotes	Manual entry, forms, and integrations you configure

Kooday’s rows are resolved from the pricing registry at build time; the HubSpot and Zoho CRM rows are read from each vendor’s own pricing page on 2026-09-09. HubSpot and Zoho CRM are general-purpose CRMs priced per seat; Kooday’s customer record is narrower and resolves identity from conversations that already happened.