...And why it ends up being costly for those who trust them on this channel.
Salesforce has just announced a new WhatsApp integration. HubSpot too. Microsoft Dynamics as well.
Good.
The problem is that these integrations all look the same: one more channel in a dropdown list. An additional pipe to send outbound messages. A checkbox in a product roadmap.
WhatsApp treated like email. With the same logic, the same workflows, the same limitations...
And meanwhile, the brands that truly use WhatsApp, the ones that understand what this channel can do, are achieving 80% open rates. Cutting their cost per lead in half. Customers who reply, who ask questions, who buy.
Not because they have one more CRM. Because they understood that WhatsApp is not a channel like the others.
This is the core of the problem, and no one says it clearly.
A CRM is a relational database with a commercial interface. It is extraordinarily good at what it does: centralizing customer information, tracking opportunities, automating sequences. That is its core nature.
WhatsApp is a conversation space. In real time. Bidirectional, asynchronous. With implicit expectations of speed, personalisation, and fluidity that have nothing to do with a nurturing email scheduled at 10 a.m. on a Tuesday.
When Salesforce integrates WhatsApp, it integrates a channel within a pipeline logic. The WhatsApp message becomes a “touchpoint” in a sequence. You can send. You can log the response. You can create a follow-up task.
What you cannot do: build a non-linear conversational flow. Adapt the message in real time based on what the prospect replies. Send a product carousel, an interactive menu, an embedded form. Let a marketing team operate this channel without going through IT.
This is not a bug. It is a logical consequence of an architecture designed for something else.
WhatsApp Business API is not a push channel. It is a dialogue channel, with its own rules, its own formats, its own Meta constraints, which, if you don’t understand them, will get you blocked.
Here are some concrete examples of what CRMs do not handle well:
Rich formats. WhatsApp supports interactive buttons, carousels, dropdown lists, and messages with clickable CTAs. These formats multiply engagement rates. In a traditional CRM, sending this type of message requires technical configuration that neither marketing nor sales teams can handle alone.
The 24-hour window. Meta enforces a strict rule: beyond 24 hours after the last customer message, only pre-approved templates can be sent. This mechanism radically changes follow-up logic. CRMs either ignore it or treat it as a constraint to bypass, not as a lever to manage.
Inbound flow. A customer replies to a WhatsApp campaign. They ask a question. They want to know if their model is available in red. In a CRM, this reply lands in an inbox that no one really checks, or triggers an alert without conversational context. There is no automated flow to qualify the request, propose a response, or route it to the right agent if needed.
Conversational qualification. A well-designed WhatsApp chatbot qualifies a prospect in 3 questions before handing them to a salesperson. It collects budget, project, timeline. It does not do this with a form. It does it through a real conversation, in natural language, with quick reply buttons to facilitate interaction. No CRM on the market offers this natively on WhatsApp
A brand managing WhatsApp from its CRM, without a dedicated platform, generally does the same thing: outbound broadcast. It sends templates. It measures opens. It believes it is using WhatsApp.
It is not using WhatsApp. It is using a slightly improved SMS with a green logo.
The cost of this underuse is real. Every conversation that could have been automated and is not mobilizes an agent. Every qualified lead via WhatsApp that does not receive a reply within 5 minutes loses 80% of its conversion probability. Every campaign sent without fine behavioral segmentation generates opt-outs, and a WhatsApp opt-out is final.
CRMs were not designed to manage these parameters. They ignore them or delegate them to custom configurations that must be maintained manually.
The other issue no one mentions: who operates WhatsApp within a company?
In 70% of cases, it is marketing. Otherwise support. Rarely the CRM admin.
Yet in a CRM, to build a new WhatsApp flow, you need to go through IT. Or an integration partner. Or a 3-day training on the automation studio. It is not designed to be operated by a marketing team that wants to launch a campaign before a sales period.
A dedicated WhatsApp platform is built so marketing can be autonomous. No-code. Visual interface. Deployment in a few hours, not a few weeks.
This is not a UX detail. It is the difference between a brand that can activate WhatsApp continuously and one that uses it twice a year because it is too complex.
CRMs will remain essential. They will remain the backbone of customer data. They will continue to improve their WhatsApp integrations, and those integrations will continue to serve the minimum use case: sending a message, logging a reply.
But to turn WhatsApp into a true acquisition, conversion, and retention channel, you need a platform that was built for it. Not one that added it to its roadmap after Meta announced 3 billion users.
The good news: a dedicated platform does not replace the CRM. It connects to it. It enriches it. It does what it cannot do, and feeds it with the data it needs.
This is not a choice between the two. It is a question of which one is built for the job you are asking it to do.
WhatsApp deserves better than a checkbox in a product roadmap.
Sandra is a conversational platform dedicated to WhatsApp and web chat, designed for marketing teams that want to go beyond broadcast. All data hosted in Switzerland and the EU. --> hello@sandra.ch