Discuss your task

Search

Start typing to search articles, cases, and services.

↑↓ navigate Esc close

WhatsApp CRM turns chats into a measurable sales channel

A WhatsApp CRM is a CRM where every WhatsApp conversation flows in: each inquiry becomes a lead or lands in a deal, gets assigned to salespeople by rules and shows up in reports. The messenger becomes an ordinary sales channel you can control, measure, automate and set KPIs for, just like email and phone. A company of 15 or more people is usually well served by a CRM with a built-in WhatsApp channel on Meta’s official platform. Custom development is needed where conversation data has to go beyond the CRM: into end-to-end analytics from ads to revenue, into your own storage, or into external systems.

Search results for this query are almost entirely vendor pages, and each one explains why its own tool is the right fit. In the Kommo implementations and custom WhatsApp Cloud API integrations that Exceltic.dev runs for companies in Spain, other EU countries and the UAE, we see the other side: where each connection setup starts to break two to three months after launch.

Below are the four connection setups and their weak spots, the difference between the WhatsApp Business app and the API after Meta’s 2026 pricing changes, and the point where a CRM’s built-in channel is no longer enough.

A typical starting picture at a client looks like this: WhatsApp is the main inbound channel, but the CRM can’t see it. 8-12 salespeople chat with clients, each from their own number; there is a pipeline in the CRM, but conversations never make it in. The head of sales doesn’t know how many inquiries came in this week, how many became deals or how fast they were answered, so they can neither set KPIs for the channel nor automate anything in it.

WhatsApp CRM: a CRM system with WhatsApp connected as a sales channel: incoming chats create leads or attach to existing deals, are distributed among salespeople by rules, and the channel gets its own metrics: number of inquiries, response speed, conversion to deals.

What a company loses while WhatsApp runs outside the CRM

As long as conversations happen on salespeople’s phones, the company loses not individual messages but control over the whole channel: it can be neither measured nor automated. In our pre-implementation audits we find the same five gaps again and again.

  1. Inquiries don’t become leads. A new client wrote on WhatsApp, but the CRM has no record of them. The company doesn’t know how many inquiries the channel brings in and can’t compare it with the website, calls or ads.
  2. Invisible response time. The head of sales doesn’t know how long a client waited for the first reply and can’t tell a slow salesperson from an overloaded one.
  3. The chat isn’t linked to the deal. Agreements on price and timing stay in the chat, while the deal card is empty. The sales forecast is built on data that doesn’t reflect reality.
  4. Unknown source. The client came from an ad with a button that opens WhatsApp, but in the CRM they look like an ordinary new contact. Marketing can’t calculate the cost per deal for the campaign.
  5. No KPIs and no automation. Without channel data you can’t set salespeople targets for response speed and conversion, and there’s nowhere to set up chat routing, reminders or templates. Nor can you check what exactly a salesperson promised if a dispute with a client comes up.

All five gaps are closed by one decision: every WhatsApp conversation runs through the CRM. Usually that means one or several shared WhatsApp numbers for the sales team, answered by the whole team from the CRM interface, and the channel gets the same reports, rules and targets as email and phone.

Four ways to connect WhatsApp to a CRM and where each one breaks

There are four fundamentally different ways to integrate WhatsApp with a CRM on the market, and each has its own point of failure. Below is how each setup works and what breaks first in real projects.

A CRM with a built-in WhatsApp channel

The CRM itself connects to the official WhatsApp Business Platform, chats arrive directly in the cards, and automation and reports run on the same data. Kommo, for example, works this way.

The weak spot is that you’re limited to what the vendor built. The number of phone numbers is tied to your plan, routing logic to the CRM’s builder, and according to Kommo’s documentation, a number connected to Kommo can’t be used at the same time in other WhatsApp apps and integrations (the exception is coexistence with the WhatsApp Business app, covered below).

A shared inbox service synced with the CRM

A separate omnichannel platform connects WhatsApp, salespeople reply in its interface, and contacts and events are passed to the CRM through a ready-made connector.

The weak spot is that the company ends up with two sources of truth. Response time is measured in one service, revenue in another, and routing rules are configured twice. In setups like this we regularly untangle duplicate contacts caused by different phone number formats and mismatched owners: one salesperson handles the client in the chat, while the deal lists another.

A browser extension on top of WhatsApp Web

Each salesperson installs an extension that adds deal creation buttons, notes and reminders to WhatsApp Web and passes part of the data to the CRM.

The weak spot is that every salesperson still works from their own number, so there’s no shared stream of inquiries, no routing and no channel metrics. The extension depends on the WhatsApp Web interface and in practice breaks after its updates. On top of that, WhatsApp’s terms of service prohibit accessing the service through automated or unauthorized means, so unofficial connections that emulate the web version carry the risk of the number being banned.

Your own connection through the WhatsApp Cloud API

The number is connected directly to Meta’s Cloud API, your server receives events via webhook and passes them to the CRM. We covered the architecture of this setup for Kommo in detail in our article on connecting the WhatsApp Business API to Kommo without a widget.

The weak spot is that reliability is entirely on your side. If the server receiving events goes down or responds with an error, conversations stop reaching the CRM, so you need a queue, retry processing and monitoring. You also track Meta’s changes yourself: in 2025-2026 alone, the pricing model changed twice.

SetupWhere conversations are storedWhat breaks firstBest for
Built-in CRM channelIn the CRMFlexibility: numbers and logic are limited by the plan and the builderMost sales teams
Shared inbox service and CRMIn two systemsSync, duplicates, two sets of rulesMultichannel support, CRMs without their own WhatsApp
Extension on top of WhatsApp WebOn salespeople’s phonesDependence on the interface and on personal numbersTeams of 1-3 people as a temporary measure
Your own server on the Cloud APIIn the CRM and your own storageServer reliability and maintenanceNon-standard routing, audit, analytics

How the WhatsApp Business API differs from the app for a sales team

The WhatsApp Business app is designed for the owner’s phone or a single employee, while the WhatsApp Business Platform (API) is built for a team that works with clients through a CRM. For a sales team, the difference comes down to five points.

1. The 24-hour window. When a client messages or calls you, a 24-hour customer service window opens, and every new message from the client extends it. While the window is open, a salesperson can write free-form text; after it closes, only an approved template. If the client goes quiet for two days, you can no longer follow up with a regular message.

2. Templates and approval. Messages outside the window are sent as templates in three categories: marketing, utility and authentication. Every template goes through Meta’s review before it’s sent for the first time. We showed what this looks like in the Kommo interface in our guide to creating WhatsApp templates in Kommo.

3. Per-message pricing. Since July 1, 2025, Meta charges per message rather than per 24-hour conversation, and the price depends on the category and on the country of the recipient’s number. As of Q4 2026, the changes from October 1, 2026 apply: replies within the customer service window are paid again above 1,000 free messages per month per number, and utility templates sent inside an open window are no longer free. Current rates and rules are on the WhatsApp Business Platform pricing page.

The exception is inquiries from ads with a button that opens WhatsApp (Click to WhatsApp ads). If you reply to such a client within the customer service window, a free entry point window of up to 7 days opens, during which Meta charges for neither templates nor regular replies. And a separate trap: if no payment method is linked to your Meta account, once the free limit is used up Meta stops delivering service messages, and for the sales team this looks like “the salesperson replied, but the client got nothing.”

4. The number and migration. You used to have to choose for each number: either the app or the API. Now Meta supports coexistence: the number stays in the WhatsApp Business app version 2.24.17 or later and is connected to the API at the same time through a Meta partner, such as a CRM. Messages sent from the app stay free; messages sent via the API are charged at Cloud API rates.

Coexistence comes at a price. In the app, disappearing messages are turned off in one-on-one chats, broadcast lists become read-only, group chats don’t sync, and linked devices have to be re-linked. Meta lets you migrate the last 6 months of history, but the CRM may pull in less: Kommo, for example, imports chats that were active in the last 30 days.

5. Team scale. The app is a number on a specific phone plus a few linked devices. Through the API, the whole team works with one number at the same time in the CRM interface, which already has chat routing, reports and the history of every client.

Why Kommo works as a WhatsApp CRM for sales teams

If your sales run mostly through WhatsApp, Kommo is a strong default choice, because conversations are built right into the deal card instead of living in a separate module. Below is what’s available without custom work as of Q4 2026.

  • Official connection. Kommo connects directly to the official WhatsApp Business Platform, and messages are paid through your Meta account: Kommo’s documentation requires adding a payment method to the WhatsApp Business account.
  • Multiple numbers. According to Kommo’s pricing, Base includes one number plus one more for each additional user, Advanced includes three numbers, and Pro has no limit. On Meta’s side, according to Kommo’s documentation, an unverified business portfolio can start with a maximum of two numbers, and after verification the limit rises to 20.
  • Incoming leads under control. The “Incoming leads” stage holds messages from new clients for review: the salesperson accepts the lead, rejects spam or links the chat to an existing deal. That way a returning client with a new question doesn’t turn into a duplicate.
  • Conversations in the card. The chat is linked to the client profile, from it you assign an owner and set tasks, and the full conversation history sits next to the deal.
  • Routing and automation. Salesbot distributes chats in rotation (the Round Robin step), changes the owner, moves the deal through stages, branches the flow by lead source and sends a webhook to external systems. On the plan cards, pipeline automation, broadcasts and the bot builder are listed starting from Advanced.
  • Response speed in plain sight. The dashboard has widgets for unanswered conversations, median response time and the lead that has been waiting longest for a reply. These are exactly the numbers you can’t see while chats sit on phones.
  • Voice messages and files. The chat supports text, voice messages, images, video and documents, and broadcasts come with delivery, read and reply reports.

We cover which scenarios to automate first so they actually take manual work off your team in our article on CRM automation.

When Kommo’s built-in channel is enough and when you need custom work

The line isn’t drawn by company size but by whether you need WhatsApp data outside the CRM. In a typical project, the built-in channel is enough if you have up to three numbers, inbound inquiries, round-robin or market-based routing, templates for follow-ups and standard response speed reports. All of this is configured without code.

Custom work is needed in four situations:

  1. End-to-end ad analytics. When a client messages you from a Click to WhatsApp ad, the Cloud API passes a referral object in the event with the ad ID and the click ID (ctwa_clid). To tie the ad to revenue, this data has to reach the deal fields and reports. With the built-in channel, check on your own account which of these values make it into the deal; for sending events back to Meta, Salesbot has a Meta Conversions API action.
  2. Your own copy of conversations. For audits, quality control or analytics, conversations are duplicated to your own storage.
  3. Routing based on external data. A chat has to go to a salesperson based on data from an ERP, billing system or property catalog that isn’t in Kommo.
  4. Verification codes in WhatsApp. Authentication templates aren’t currently available in Kommo, so code-based login or booking confirmation via WhatsApp is built as a separate integration.

Depending on the task, this is either custom work on top of the built-in channel via the Kommo API and a webhook from Salesbot, or your own channel on the Cloud API following the setup from the article mentioned above. If you’re just choosing or rebuilding your CRM, plan your Kommo implementation around WhatsApp from the start: how many numbers, who gets which chats, and which pipeline stages the conversations move.

What to consider in Spain and the UAE when storing conversations

In projects for Spain and the UAE we see the same picture: clients message businesses on WhatsApp by default, often with voice messages and in several languages. That’s why companies often keep separate numbers for markets or languages, and routing by number becomes the first routing rule.

Spain is in the EU, so client conversations in your CRM are personal data processing under GDPR. Among the GDPR principles, three matter most for the WhatsApp channel: a lawful basis for processing, data minimization and storage limitation. The company has to set retention periods after which data is deleted or reviewed.

As long as conversations sit on salespeople’s personal phones, the company controls neither where they’re stored, nor for how long, nor whether a former employee still has access to client data. Moving them into the CRM doesn’t make the channel GDPR-compliant automatically, but it gives you a point where these rules can be applied. The UAE has its own federal personal data protection law, and the financial free zones DIFC and ADGM have their own regimes, so check storage requirements with a local lawyer.

What a rollout looks like in numbers

The figures below are a typical range from Exceltic.dev projects that move sales from personal WhatsApp accounts into Kommo for teams of 12-25 people, not the result of a single client.

MetricBeforeAfter 2 months
Numbers used to handle clients8-15, mostly personal2-3 company numbers
Share of chats linked to a deal30-50%90-95%
Median first response time during business hours1.5-3 hours10-25 minutes
WhatsApp channel metricsNot trackedInquiries, response speed and conversion in standard reports

The setup itself takes 2-4 weeks: an audit of numbers and scenarios, business portfolio verification in Meta, pipelines, the Incoming leads stage, Salesbot with routing, and templates. The longest part isn’t technical but moving clients from personal numbers to company ones: in a typical project that takes another 4-6 weeks.

After launch, three things break most often. Meta rejects a template, and the follow-up after the window closes doesn’t go out. No payment method has been added in Meta, and service messages stop being delivered after the free limit. Some salespeople keep replying from their personal phones, so from day one the head of sales watches the number of new leads per salesperson: a sharp drop for one person usually means they’re handling clients outside the CRM.

Who this setup is for

This setup is for companies of 15 or more people where WhatsApp is the main inbound channel and at least five salespeople work in sales. Most often that’s real estate, education, travel and professional services in Spain, other EU countries and the UAE, where clients expect a reply in a messenger rather than an email. If you have one or two salespeople and one number, the WhatsApp Business app is enough for now, and you should plan the switch for when you hire the third.

Frequently asked questions

Can I keep the WhatsApp Business app and connect the same number to a CRM?

Yes. Meta supports coexistence: the number keeps working in the WhatsApp Business app and is connected to the API at the same time through a Meta partner, such as a CRM. You need app version 2.24.17 or later, and new accounts aren’t admitted right away: according to Kommo’s documentation, Meta looks at how long the number has been in use and at the quality of its conversations. Messages sent from the app stay free; messages sent via the API are charged at Meta’s rates. Keep the limitations in mind: broadcast lists in the app become read-only, group chats don’t sync, and linked devices have to be re-linked. When you connect, Kommo imports chats that were active in the last 30 days.

How much does the WhatsApp Business API cost for a sales team?

Meta charges for every message, and the price depends on the template category and on the country of the recipient’s number. As of Q4 2026, each number gets 1,000 free service messages per month; beyond that, replies within the customer service window are paid, and utility templates inside an open window have been charged since October 1, 2026. Inquiries from Click to WhatsApp ads open a free entry point window of up to 7 days. On top of that comes the CRM subscription: in Kommo, the WhatsApp channel is included in the plan, and messages are paid through your Meta account.

How is a WhatsApp CRM better than a separate shared inbox service?

The main difference is a single source of truth. In a WhatsApp CRM, the chat, the deal, the owner and the response time live in one system, so you can tie response speed to conversion and revenue. A separate shared inbox service suits a support team working across several channels, or a CRM that can’t connect WhatsApp on its own. For sales, it adds syncing between two systems: duplicate contacts, mismatched owners, routing rules in two places and a second subscription. If you haven’t chosen a CRM yet and your sales run through WhatsApp, it’s simpler to start with a CRM that has a built-in channel.

Can I connect my salespeople’s personal numbers to a CRM?

Technically, some of these numbers can be connected, but for sales it’s a weak solution. According to Kommo’s documentation, a number from regular WhatsApp has to be deleted and reconnected as a new one, so the history on the phone won’t move over. A number from the WhatsApp Business app can be connected in coexistence mode, but it still remains the employee’s number. Extensions and unofficial gateways work around the official API, and WhatsApp’s terms of service prohibit unauthorized and automated access to the service, hence the risk of a ban. The reliable setup is company numbers that your salespeople move clients to over several weeks.

Summary

  • A WhatsApp CRM turns the messenger into an ordinary sales channel: every conversation is in the CRM, inquiries count as leads, and the channel has metrics, automation and KPIs.
  • For most sales teams, a CRM with a built-in channel on Meta’s official platform is enough, while shared inbox services and extensions add points of failure.
  • Since October 1, 2026, Meta again charges for service messages above 1,000 per month per number, so a payment method in Meta is a mandatory launch item.
  • Kommo covers incoming leads, routing and response speed control without code, while custom work is needed for ad analytics and working with external data.

If WhatsApp is one of your main sales channels but it doesn’t show up in your CRM and reports, describe your task to the Exceltic.dev team: how many numbers, salespeople and markets you have. We’ll propose a connection setup and estimate the scope of work.

More articles

All
Get in touch your way
WhatsApp Telegram

Before you go: bonus months of Kommo

The implementation estimate is free: describe your sales process in a few words and we propose a solution, a plan and a quote with timelines.

We are an official Kommo partner in Europe: pay for the subscription through us and get bonus months.