Why CRMs miss WhatsApp completely

Salesforce has just announced a new WhatsApp integration. So has HubSpot. So has Microsoft Dynamics. Good.

The problem is that these integrations all look the same: one more channel in a dropdown. One more pipe for sending outbound messages. A checkbox on a product roadmap. WhatsApp treated like email, with the same logic, the same workflows, the same limitations.

Meanwhile, the brands that genuinely use WhatsApp are getting 80% open rates and halving their cost per lead. Customers who reply, who ask questions, who buy. Not because they have one more CRM, but because they have understood that WhatsApp is not a channel like the others.

A CRM is built to manage data, not to hold a conversation

This is the heart of the problem, and nobody says it plainly.

A CRM is a relational database with a commercial interface. It is extraordinarily good at what it does: centralising customer information, tracking opportunities, automating sequences. That is its nature.

WhatsApp is a conversation space. Real time, two-way, asynchronous. With implicit expectations of speed, personalisation and fluidity that have nothing to do with a nurturing email scheduled for 10am on a Tuesday.

When a CRM integrates WhatsApp, it integrates a channel into pipeline logic. The message becomes a touchpoint in a sequence. You can send, you can log the reply, you can create a follow-up task.

What you cannot do: build a non-linear conversational journey, adapt the message in real time to what the prospect answers, send a product carousel, an interactive menu, an embedded form. Nor let a marketing team run the channel without going through IT.

That is not a flaw. It is the logical consequence of an architecture designed for something else.

The finesse WhatsApp demands, CRMs do not have

The WhatsApp Business API is not a broadcast channel. It is a dialogue channel, with its own rules, formats and Meta constraints, and if you don't understand them, you get blocked. A few concrete examples:

• Rich formats. WhatsApp supports interactive buttons, carousels, dropdown lists, messages with clickable calls to action. These formats multiply engagement rates. In a classic CRM, sending that kind of message takes technical configuration that neither marketing nor sales can do alone.
• The 24-hour window. Meta enforces a strict rule: beyond 24 hours after the customer's last message, only pre-approved templates can be sent. That mechanic changes follow-up logic radically. CRMs either ignore it or treat it as a constraint to work around, rather than a variable to manage.
• Inbound flow. A customer replies to a campaign and asks a question. In a CRM, that reply lands in an inbox nobody really watches, or triggers an alert with no conversational context. There is no automated journey to qualify the request, propose an answer, route it to the right agent.
• Conversational qualification. A well-built WhatsApp agent qualifies a prospect in three questions before handing them to a sales rep. It collects the budget, the project, the timing. Not with a form: with a real conversation, in natural language, with quick-reply buttons. No CRM on the market offers that natively.

What it actually costs

A brand running WhatsApp from its CRM, with no dedicated platform, generally does the same thing: outbound broadcast. It sends templates, it measures opens, it believes it is using WhatsApp. What it is actually using is a slightly improved SMS with a green logo.

The cost of that under-use is real. Every conversation that could have been automated and isn't ties up an agent. Every qualified prospect who doesn't get a reply within five minutes loses most of their probability of converting. Every campaign sent without fine behavioural segmentation generates opt-outs, and a WhatsApp opt-out is final.

What it means for the teams

The other problem nobody mentions: who actually operates WhatsApp inside a company? In the vast majority of cases, marketing, sometimes support. Rarely the CRM administrator.

Yet in a CRM, building a new WhatsApp journey means going through IT, a partner integrator, or three days of training on the automation studio. It is not built to be operated by a marketing team that wants to launch a campaign before the sales.

A dedicated platform is built so that marketing is autonomous: no code, a visual interface, live in a few hours rather than a few weeks. That is not a user-experience detail, it is the difference between a brand that keeps WhatsApp active and a brand that uses it twice a year because it is too complicated.

The conclusion CRM vendors will never draw

CRMs will remain indispensable. They will remain the backbone of customer data, and they will keep improving their WhatsApp integrations, which will keep meeting the minimal use case: send a message, log a reply.

But to turn WhatsApp into a real acquisition, conversion and retention channel, you need a platform designed for it. The good news: a dedicated platform doesn't replace the CRM. It connects to it, enriches it, does what it cannot do and passes back the data it needs.

It is not a choice between the two. It is a question of which of the two was built for the job you are asking of it.