WhatsApp and CRM: Three Ways to Connect

The requirement sounds simple: "WhatsApp conversations should land in the CRM." In practice that hides three different solutions with different prices, different reliability and very different consequences when something goes wrong.

Option 1. The official WhatsApp Business Platform

Meta grants access through partner providers (BSPs), and the CRM connects to that access. This is how the native amoCRM, Kommo and Bitrix24 integrations work.

What you get: conversations on the customer record, history owned by the company, template messages for reminders, the option to plug in an AI assistant, and business verification if you want it.

What it costs: Meta bills per conversation and the provider adds its own fee. Also, a number bound to the API can no longer be used in the regular WhatsApp app on a phone. That move is one-way.

Who it suits: anyone for whom messaging is part of selling rather than the occasional question.

Option 2. A widget from the CRM marketplace

The amoCRM, Kommo and Bitrix24 marketplaces carry dozens of widgets promising WhatsApp "in two clicks". Technically most of them wrap one of the other two options.

What to check before buying: what the widget actually runs on. If the description says "official API" and names a provider, it is option 1 with somebody else's interface on top, and that is fine. If no provider is named and setup comes down to scanning a QR code with a phone, it is option 3 whatever it calls itself.

The overlooked risk: a widget is one more intermediary between you and Meta. If its developer shuts down, the history stays but the channel goes dark.

Option 3. An unofficial gateway over QR code

It works by connecting to your ordinary WhatsApp the same way WhatsApp Web does, then forwarding messages into the CRM. Cheap, fast, no business verification.

Why we do not install these: Meta treats such connections as a breach of terms and closes the numbers. Not "might close one day" but closes them regularly, in waves. A number carrying your whole customer base is rarely recovered, and the conversation history goes with it.

The saving here is measured in tens of euros a month. The risk is your main sales channel.

What breaks most often

• The number is already taken. If the regular WhatsApp Business app is registered on it, it has to be released first. The move is irreversible: you cannot go back to the app on the same number.
• Templates get rejected. Meta turns down templates with direct advertising or promises. Wording has to be rewritten, which takes anywhere from a few hours to a couple of days.
• Two channels on one number. Telephony and WhatsApp can share a number, but they must be configured together, otherwise a call and a message create two separate deals for one customer.
• Group chats. The API has none. If part of your work happens in groups, that part cannot be automated.

Choosing in five minutes

If WhatsApp brings in money, it is option 1 and the question is closed. If it is a rare side channel you would not miss, the plain app is fine and no integration is needed. Option 3 saves little and risks a lot.

Our part: channel connection from €200 per channel if a CRM is already in place, and from €990 for a CRM implementation with channels included.

Who answers when the channel goes down

A question that surfaces during the very first outage, and that has to be discussed before connecting.

Four parties sit between you and the customer: Meta, the access provider (BSP), the widget developer if there is one, and the integrator. When messages stop arriving, each can honestly say "everything works on our side".

What to settle in advance:

• Who you contact first. There has to be one entry point, not three chats with different contractors.
• How fast they respond. "During business hours" and "within an hour" are different promises, and the difference is very noticeable mid-outage.
• Whether there is a fallback channel. While WhatsApp is down, enquiries still have to land somewhere: phone, web form, Telegram. That is configured in advance, not during the incident.
• Where Meta's notifications go. Emails about policy breaches and rule changes arrive at the address given at registration. If that is a former employee's personal inbox, you will hear about the problem from customers.

The last point looks like a detail right up until the first time.

Meta's rules change; check the current WhatsApp Business Platform documentation before connecting.