For a lot of businesses, a large share of the sales conversation now happens on WhatsApp. The problem is that conversation lives on a salesperson's phone, while customer data lives in the CRM. Two worlds that don't talk to each other — and the context gets lost in between.
In This Article
- The three versions of WhatsApp and which one you need
- What actually gets synced
- Where AI comes in
- What it really costs
- Mistakes that get your account blocked
The three versions of WhatsApp and which one you need
This is the confusion almost everyone runs into, and it determines whether the project is even viable:
| Regular WhatsApp | WhatsApp Business (app) | WhatsApp Business API | |
|---|---|---|---|
| Simultaneous users | 1 | Up to 5 devices | Unlimited |
| CRM integration | No | Not really | Yes, native |
| Automation | No | Manual quick replies | Full |
| Cost | Free | Free | Per conversation + provider fee |
Only the third option makes what we're describing here possible. It's contracted through a Meta-authorized provider and requires business verification. That's a process that takes days, not months — but it needs to be part of the plan.
What we always say before starting a project like this: if the goal is for the CRM to log every conversation, the WhatsApp Business app won't cut it, no matter how much "Business" is in the name. There's no shortcut.
What actually gets synced
Once the integration is running, here's what happens without anyone lifting a finger:
- Contact created or enriched. If the number isn't in the CRM yet, a record is created; if it already exists, the conversation gets linked to it.
- Full message history on the contact record, visible to anyone on the team. No more "ask Sarah, she was handling that one."
- Lead status updated based on what happens in the conversation.
- Triggers into other workflows: booking a meeting, sending a quote, opening a task for the sales rep.
- Real metrics: response time, volume per agent, conversion rate for the channel.
That last point tends to catch people off guard. Most companies selling through WhatsApp have no idea how well the channel actually converts, because it was never measurable before.
Where AI comes in
The integration on its own just logs the conversation. AI is what answers it.
An AI agent connected to this channel handles the first message within seconds, asks the qualifying questions, checks availability, and books the meeting. When it detects that a case needs human judgment, it hands the conversation off to the sales rep with the context already summarized.
The difference from an automated menu of options is that the customer writes the way people actually write — "hi, I'd like pricing info for about 20 people" — and the system understands it without forcing them to pick option 3.
What it really costs
The cost has three layers, and only the first one shows up on Meta's website:
- Conversations. Meta charges per 24-hour conversation window, with different pricing depending on who starts it and why. Typical rates run to a few cents per conversation.
- API provider. Between €30 and €100/month depending on volume and features.
- Implementation. Defining flows, templates, and escalation rules. This is where the real work is.
For a business handling 300-500 conversations a month, recurring costs usually land between €80 and €200/month. Compare that to what an hour of your sales team's time costs, and the math works itself out — as we cover in our article on ROI.
Mistakes that get your account blocked
Meta is strict, and suspensions are hard to reverse. The three mistakes we see most often:
- Messaging first outside the 24-hour window without an approved template. Once that window closes, you can only start a new conversation with a Meta-reviewed template. Skipping this triggers blocks.
- Importing purchased contact lists. If people mark your messages as spam, your number quality drops — and so does your sending limit.
- Treating the channel like a newsletter. WhatsApp tolerates frequency far worse than email does. Burning out the channel costs months to recover from.
Conclusion
Connecting your CRM to WhatsApp isn't a complicated technical project — it's a channel decision. The hard part isn't the integration; it's defining what the system responds to, when a human steps in, and how often it's acceptable to message.
Get it right, and you gain a complete history, measurable response times, and a channel that finally converts in a trackable way. Get it wrong, and you lose the number.
Want to set this up without risking your account? Tell us about your case.
