WhatsApp CRM: customer records from your chats.
A WhatsApp CRM keeps a record of every customer you talk to on WhatsApp — who they are, what they asked, what happens next — next to the conversation itself. The WhatsApp Business app gives you labels and quick replies on one phone; a real CRM needs software connected to the WhatsApp Business Platform, which Meta now lets you do without giving up the app on the same number.
WhatsApp CRM, in short
- App alone
- Labels, quick replies, catalog — on the phone
- Connected
- Cloud API + webhooks into your CRM
- Keep the app
- Yes, with Meta's “coexistence” onboarding
- History synced
- Contacts and the last 6 months of 1:1 chats
- Free-form replies
- Within the 24-hour customer service window
What a WhatsApp CRM actually is
A CRM is the list of your customers and everything you know about them. A WhatsApp CRM is the same list, filled from WhatsApp conversations: a new chat becomes a contact, a question becomes a lead or a ticket, and the next step — a quote, a reminder, a follow-up — is attached to the person, not lost in a phone.
There are two ways to get there. You can organise customers inside the WhatsApp Business app itself, with no other software. Or you connect your number to the WhatsApp Business Platform, where Meta's Cloud API delivers every incoming message to your own server as a webhook, and your CRM stores it. The second is what lets a team, a dashboard or an AI agent work on the same conversations.
From the app alone to a connected CRM
| Set-up | What you get | What you give up |
|---|---|---|
| WhatsApp Business app only | Labels, quick replies, greeting and away messages, catalog, broadcast lists — all on the phone, no extra software | No customer record outside WhatsApp; no reporting; the team shares the account through linked devices |
| Business app + Cloud API (coexistence) | The same number in the app and in your CRM; messages mirrored both ways; contacts and recent 1:1 history synced | Broadcast lists become read-only; disappearing, view-once and live-location messages are turned off; group chats do not sync |
| Cloud API only | Your CRM or agent sends and receives everything; templates for messages outside the 24-hour window | No WhatsApp Business app on that number |
Keeping the app while adding a CRM
Since Meta opened onboarding for WhatsApp Business app users — called “coexistence” in its support channels — a business can connect its existing app number to the Cloud API through a provider's Embedded Signup flow. It keeps answering one-to-one from the app, while software sends at volume, and WhatsApp keeps the history of both in sync.
Meta lists precisely what moves across. Individual chats and contacts are supported on the API side; the most recent 6 months of chat messages can be synchronised. The app's own tools — labels, quick replies, greeting and away messages, catalog, business profile — keep working in the app but are not exposed through the Cloud API. So labels you set on the phone will not appear in your CRM: the CRM needs its own fields.
One enquiry, from chat to customer record
Take a small furniture shop that answers on WhatsApp and has connected its number to a CRM.
- 01
The customer writes
“Does the oak table come in another colour?” Meta sends the message to the shop's server as a messages webhook, with the sender's WhatsApp ID and profile name.
- 02
The CRM files it
No contact with that number exists, so the CRM creates one, attaches the message and marks it as a product question. The 24-hour customer service window is now open.
- 03
Someone answers
A salesperson replies from the CRM — or from the WhatsApp Business app, since both are in sync. Inside the window, a free-form reply needs no approved template.
- 04
The follow-up is scheduled
The salesperson sets a reminder for when the new colour is in stock. By then the window has closed, so the CRM will send it as an approved message template.
What the 24-hour window means for a CRM
When a customer messages or calls you, a 24-hour customer service window opens, and resets each time they write again. While it is open, your CRM can send any free-form message. Once it closes, only pre-approved message templates can go out. Messages sent from the WhatsApp Business app are not bound by that window and do not open or extend it on the API side.
On cost, Meta does not charge for messages customers send you, and each business phone number gets its first 1,000 service messages a month free; templates are charged per message by category. The rates and the October 2026 changes are in our article on WhatsApp Business API pricing.
Pitfalls to check before you connect
- The history sync has a deadline. After onboarding an app number, the provider has 24 hours to synchronise contacts and history; otherwise the business must be offboarded and go through the flow again. Keep the app open on the phone while it runs.
- Broadcast lists stop. Existing lists become read-only and new ones cannot be created; campaigns move to templates sent from the CRM.
- Linked devices are unlinked. All companion devices are disconnected at onboarding and must be re-linked; WhatsApp for Windows and Wear OS are not supported as companions, and a customer writing from one of them triggers no webhook, so the message never reaches your CRM.
- Throughput is capped. A number used in both the app and the Cloud API has a fixed throughput of 20 messages per second.
- Group chats stay out. Only one-to-one chats are synchronised; customer groups remain in the app.
When a connected CRM is worth it
If one person answers a few customers a day, the WhatsApp Business app with labels is often enough. A connected CRM pays off when several people answer, when follow-ups slip, when you need to know which enquiry became a sale, or when an AI agent should answer, book or qualify before a person steps in. That is the layer we build in our WhatsApp AI agents — for example the guest CRM and WhatsApp booking assistant of a restaurant group's booking platform, or BrokerPilot for insurance brokers.
Sources
- Meta for Developers — Onboard WhatsApp Business app users — coexistence, feature comparison, 6-month history sync, 24-hour sync deadline, linked devices, 20 mps — checked 22 October 2026
- Meta for Developers — Send messages — service messages and the 24-hour customer service window — checked 22 October 2026
- Meta for Developers — Webhooks — incoming messages and statuses delivered to your server — checked 22 October 2026
- Meta for Developers — Pricing — free incoming messages, 1,000 free service messages a month — checked 22 October 2026
Related
Frequently asked questions
What is a WhatsApp CRM?
A customer record filled from WhatsApp conversations: each chat is attached to a contact, with what they asked and the next step. It can be as simple as labels in the WhatsApp Business app, or a CRM connected to the WhatsApp Business Platform that receives every message through webhooks.
Can I use WhatsApp as a CRM without other software?
Partly. The WhatsApp Business app has labels, quick replies, greeting and away messages and a catalog, which is enough to organise a few customers on one phone. It does not keep customer records outside WhatsApp or report on them; for that you need software connected to the Cloud API.
Can I keep the WhatsApp Business app if I connect a CRM?
Yes. Meta lets an existing WhatsApp Business app number onboard to the Cloud API through a provider's Embedded Signup flow. You keep replying from the app, messages are mirrored with the CRM, and contacts and the last 6 months of one-to-one chats can be synchronised.
Do WhatsApp Business app labels sync to a CRM?
No. Meta's feature comparison lists labels, quick replies, greeting and away messages as not supported on the Cloud API. They keep working in the app, but the CRM needs its own fields.
Can a CRM message a customer on WhatsApp at any time?
Only inside the 24-hour customer service window that opens when the customer writes or calls. Outside it, the CRM must send a pre-approved message template.
Turning WhatsApp chats into customer records?
We connect your number to the WhatsApp Business Platform and build the CRM and the agent on top of it.