WhatsApp CRM: what it needs, how it works with the official API and what it costs

What a WhatsApp CRM is

CRM stands for customer relationship management: the record of who buys, the sales pipeline, the tasks and the history of every deal. A WhatsApp CRM is a CRM where the WhatsApp conversation lives inside the system, tied to the customer profile and the deal, not on a separate phone.

In Brazil and much of Latin America, a large share of sales starts, moves and closes on WhatsApp, so this is no longer a detail. The traditional CRM, built around email and phone calls, keeps the records while the negotiation happens somewhere else. The salesperson replies from their phone, updates the pipeline when they remember, and the manager only sees what was typed in.

The most expensive symptom shows up the day someone leaves the company. The conversation history leaves with the device, the customer who was about to close writes to a number nobody checks anymore, and the next salesperson starts from scratch. A WhatsApp CRM exists so the conversation belongs to the company, not to whoever had the phone.

What it needs to have

The conversation inside the system, not a link that opens WhatsApp in another tab. Whoever is answering needs to see the customer’s message next to their profile, with what they already bought, the team’s notes and the open deals, without switching screens and without copying and pasting.

One customer profile across all channels. The same customer who wrote on Instagram, got an email and sent a WhatsApp message needs to show up once, with the full timeline. That includes matching the same number written in different ways: in Brazil, the same mobile number with and without the ninth digit; elsewhere, country codes and formatting. Otherwise the profile splits in two.

A sales pipeline that talks to the inbox. Any conversation should become a deal in the right stage with one click, and the deal card should show the customer’s last message and link back to the conversation. Stages with a time limit, which flag a deal that has stalled, are worth more than a report at the end of the month.

And assignment across the team: a new conversation arrives with an owner, through round-robin assignment or a rule; the agent can transfer it to someone else with an internal note the customer doesn’t see; and the manager sees each person’s workload and what has been waiting too long for a reply.

Two ways to connect WhatsApp to a CRM

The first is a browser extension that sits on top of WhatsApp Web. It installs in minutes, is usually cheap or free, and draws a pipeline, labels and reminders over the WhatsApp screen. It’s what many of the results for “WhatsApp CRM” offer, which is why so many companies start there.

The problem is what it does underneath. The extension modifies WhatsApp Web, and many extensions automate sending, while the WhatsApp Terms of Service prohibit modifying the service and sending bulk or automated messages. The Help Center warns that unofficial apps and versions can lead to a temporary or permanent account ban; it doesn’t name extensions, but the rule in the terms is the same. And the session depends on an open browser, with customer data passing through third-party code.

The second is the official API, Meta’s Cloud API. The number is connected to the platform through Meta’s signup flow, and messages come into the system and go out through it by webhook, with no phone in the middle. There’s no session to drop, the history stays on the platform’s server, and any number of people can answer the same number. If you don’t want to give up the app, coexistence lets you use the same number on the phone and on the API at the same time.

Shared inbox: the whole team on one number

A shared inbox means several people answering the same WhatsApp number without stepping on each other. The WhatsApp Business app lets you add up to four linked devices to the main phone, and the paid Meta Verified subscription extends that to up to ten devices, with a name for each device and conversation assignment. For a small team, that may be enough.

On the API, the limit is no longer about devices. Agents work inside the system, and the number of people depends only on the platform. What changes the operation is what comes with it: a single queue, automatic assignment based on each agent’s workload, conversations marked as someone’s, visible reply deadlines and a supervisor view to reassign whatever was left without an owner.

One question settles half of any vendor comparison: does the price change when the team grows? In many tools, each agent is a license. That pushes the business to put fewer people on conversations than it should, which is the opposite of what a shared inbox promises.

From first contact to closing

The typical path starts with an ad that opens WhatsApp, the button on the website or an Instagram message. The first reply can be automatic, sharing business hours and asking for what’s missing to qualify the contact, and the conversation lands in the sales queue with an owner already assigned. The salesperson replies, creates the deal in the pipeline and sets the next task.

Follow-up runs into the rule that most often catches people who come from the phone: the customer service window. For up to 24 hours after the customer’s last message, the salesperson can write anything. After that, only with a template approved by Meta. The CRM needs to show when the window closes and offer the right templates to restart the conversation, instead of letting the salesperson find out from a message that didn’t go through.

The template category matters. Reminding a customer about a proposal they asked for is different from sending a new offer, and Meta classifies, charges and limits each type differently. At closing, the deal leaves the pipeline as won or lost, with the reason, and that reason, combined with the time spent in each stage, tells you where sales are getting stuck.

Automation inside the CRM

Automation in a WhatsApp CRM has three uses that pay off quickly. The first is the after-hours reply: whoever writes at night gets an instant note saying when someone will reply and asking what they can share in advance, and the conversation is waiting in the queue in the morning. The second is an AI first line, which answers repeat questions with the company’s catalog and knowledge base and hands off to the salesperson when the topic turns into a negotiation.

The third is follow-up. When a deal moves to a new stage, that stage’s message can go out on its own, like confirming the proposal was sent or reminding the customer about a meeting. And reminders for the salesperson, such as getting back in three days to a customer who asked for time, keep sales from dying of forgetfulness, which is the most common cause of lost deals and the least recorded one.

The caveat is the same as for any WhatsApp automation: a message to someone who hasn’t written in the last 24 hours goes out as a template, with a category and a cost, and needs consent. Automation that fires an offer at every stage change turns the pipeline into a block generator, and blocks drag down the quality of the whole number.

Data, privacy law and the day a salesperson leaves

Sales conversations are your customers’ personal data, and under data protection law (GDPR in Europe, LGPD in Brazil) the business is responsible for them. That asks three things of the CRM: knowing where the data is stored, controlling who on the team sees what, and recording each customer’s consent to receive messages, with date and channel, along with opt-out requests.

With the conversation inside the system, a salesperson leaving becomes a handover of their accounts, not a loss. Their conversations and deals move to someone else with the full history, their access is removed the same day, and the customer keeps talking to the same company number without noticing the change.

How much a WhatsApp CRM costs

There are two bills added together. The first is the platform’s, and the models vary: a monthly fee per agent, or per-seat pricing, which is the standard for traditional CRMs; billing per active contact, which goes up as your contact base grows; and a monthly fee based on message volume, which tracks usage rather than team size. The same business can pay very different amounts depending on the model.

The second is Meta’s, which applies on any platform that uses the official API. Replies inside the window are service messages, with 1,000 free per number per month and charges after that; templates outside the window are charged by category and by the recipient’s country. A good platform shows that cost before you send, not just on the invoice.

The fair comparison is the monthly bill for your real team: how many people will answer, how many conversations per month, how many template follow-ups and how much of that is marketing. Ask for a quote in those terms. A per-user price that looks low can become the biggest line on the bill when the team doubles.