WhatsApp CRM: what to check before you pay

A WhatsApp CRM organises conversations: it routes them between agents, stores history and reports on it. What it does not do is have them. Before comparing prices, know that the subscription and the cost of the messages are two separate bills, and the second one appears in almost no comparison table.

I searched for "whatsapp crm" and read the first ten results. All ten are listicles along the lines of "the 8 best CRMs", and all ten are published by a company that sells a CRM. I am not saying they lie. I am saying none of them will write the paragraph explaining when you don't need what they sell. I don't sell CRMs, so I can write that paragraph.

What is the best CRM for WhatsApp?

There isn't one. There is one that fits your operation, and finding it means answering three questions before you open any comparison.

How many people handle chats at once. If it's one, almost anything works and you probably don't need a CRM at all. From three or four upwards it starts to matter how conversations get routed, and what happens when someone goes on holiday with twenty open chats assigned to them.

What it needs to talk to. A CRM that can't check your stock, your orders or your invoicing forces the agent to look it up on another screen. That is where response time goes, and response time is what converts.

How messages are billed. This is the question nobody asks and the one that causes the most grief. Some providers pass Meta's rate through untouched, some add a per-message markup, and some bundle an allowance into the subscription and charge for anything beyond it. Those are very different models sitting behind very similar headline prices.

Is there a free CRM that works with WhatsApp?

Several offer a free plan, and it's a fair question, but no free plan covers the messages.

Since 1 July 2025 Meta charges for every template delivered, priced by category and by the recipient's country. Somebody pays that, always, and that somebody is you — either directly to Meta or buried inside the CRM's invoice. A free CRM connected to the API still generates messaging costs from the first send.

What genuinely is free is more than most people realise: service messages inside a conversation the customer opened have not been charged since November 2024, utility templates are free inside the 24-hour window, and anyone arriving from a Click to WhatsApp ad opens a 72-hour window in which everything is free. The difference between a reasonable bill and an unpleasant one is almost never the CRM you picked. It's how many messages you send outside those windows.

The questions I ask before recommending one

When a client shows me three quotes, I don't read the feature tables. I ask these:

Does the per-user price include people who only read? Most teams have someone who needs to see conversations but never replies. If everyone counts as a paid seat, the real price is well above the headline.

What happens to my conversations if I leave? Ask for a test export before signing, not after. Conversation history is one of the hardest things to get back and one of the least discussed at purchase.

Is the number mine? With some providers the number ends up registered to them. Migrating later is possible, but it stops being paperwork and becomes a negotiation.

Can I automate anything real, or only save canned replies? A numbered menu and a stored text are not automation. Ask specifically whether you can plug in your own logic and query your systems before replying.

What a CRM does not do

This is why I wrote this. A CRM is infrastructure for order: it routes, files, tags and measures. All of that is useful and necessary once you have volume.

But none of it answers a customer. If forty conversations are waiting, a CRM will display them beautifully sorted, each tagged and assigned, and all forty will carry on waiting. The bottleneck was never organisation. It was that more people are asking than answering.

Which is why I keep meeting companies that switch CRM every eighteen months, convinced the last one was the problem. It rarely was.

Where an AI agent fits

An agent is not a numbered menu or a tree of saved replies. That is a form wearing a conversation's clothes, and customers spot it in the first message.

What I build are agents that read the question as written, check stock, order status or history before answering, and know when to stop and hand over to a person. That last part is the most neglected and the one that saves the most sales: an agent that keeps pushing when it hasn't understood does more damage than no agent at all.

The effect on the bill works twice. Conversations resolved inside the 24-hour window generate no messaging cost, because those messages are free. And answering in seconds, while the person is still looking at the product, converts at a rate no marketing template sent two days later will reach.

The CRM organises. The agent answers. They don't compete, but only one of them replies.

How I would approach it

If you're choosing right now: buy the simplest CRM that covers your three answers above, and get the per-message cost itemised in writing before you sign. Leave the rest of the feature list for when you know which parts you actually use, which will be fewer than you expect.

And before you upgrade to a pricier plan because service is slipping, count how many of those conversations are the same question asked again. If it's most of them — and it usually is — better filing software will not fix it.

If you'd like me to look at your setup, get in touch. I work from Buenos Aires with clients in Mexico City, Argentina, the rest of Latin America and Spain.