How to Connect WhatsApp Business to Kommo CRM: Step-by-Step Guide

At Brutal Marketing we connect WhatsApp to Kommo regularly, and the expensive mistakes almost never happen during the technical setup. They happen before it. Someone takes the number that already lives in the WhatsApp app on the founder's phone, registers it with the API, and loses the entire chat history. Or they send a marketing template where a free in-window reply would have done the job, and pay five times more for the privilege.

Below is the exact sequence we use with clients: what to prepare, which buttons to press, how to get around the "number already in use" trap, why Meta rejects templates, and what 1,000 conversations a month actually costs. No omnichannel platitudes — only the things that move the result.

The confusion starts with the names. People say "we connected WhatsApp to our CRM" while meaning three different things with three different sets of consequences.

WhatsApp Business App is the free phone app. One primary device, up to four linked ones, manual replies, a catalogue, quick replies. On its own it gives you no CRM integration at all.

WhatsApp Business Platform (Cloud API) is Meta's official business channel. This is what powers the "WhatsApp Business" integration inside Kommo. Unlimited agents on one number, automation, templates, broadcasts, delivery analytics.

Grey integrations are services that hook up your number by emulating WhatsApp Web. Cheap and fast, right up until the number gets blocked.

In our experience grey solutions survive a few months on average — exactly until your reps start sending outbound at volume. Then the number hits restrictions and the client shows up asking us to rescue the database. Rescue is not always possible: conversations from an unofficial integration cannot be migrated into Cloud API.

The choice used to be binary — app or API. Meta now supports coexistence mode: the same number runs in the WhatsApp Business App on the phone and simultaneously in Kommo via Cloud API. Messages mirror in both directions.

Who needs this: the owner who is used to answering personally from their phone, and the sales team that needs a pipeline. Both see the same conversation.

What breaks in coexistence mode: group chats do not sync, and editing or unsending messages stops working. Walk your team through this before you connect, not after the first "why can't I delete a message anymore?"

Half of all failed setups are not technical problems — they are missing access. Gather everything up front.

1. A personal Facebook account with admin rights in the Meta Business Portfolio. Not "our marketer created it on their own email three years ago and left" — actual working access.
2. A Meta Business Portfolio (formerly Business Manager). You can create one during setup, but having it ready is better.
3. A phone number that can receive an SMS or a call. Not a virtual number from a random service — Meta rejects most of those.
4. A payment method in Meta. The card must clear international payments. Without one, your first messages go out and then billing hits the payment threshold and the channel stops.
5. A paid Kommo plan. You can connect on the free trial, but real operation needs the base plan or above — pricing starts at roughly $15 per user per month depending on the tier.
6. Legal company name, website, business category — for Meta business verification.

One more thing: an unverified Meta Business Portfolio supports a maximum of two numbers. Business verification raises that limit. If you have three departments and three numbers, start verification immediately — it takes anywhere from a few days to two weeks.

It is also worth settling your pipeline structure before you connect, because WhatsApp leads will start landing in the CRM within the first hour and they need a stage to land on. We normally do this ahead of connecting any channel.

This is a one-time setup and takes 15–30 minutes once your access is in order.

Step 1. Open integration settings. In Kommo's left menu, go to Settings → Integrations. Search for WhatsApp.

Step 2. Select the "WhatsApp Business" integration. Be careful here: the marketplace lists several cards with similar names, including third-party solutions. You want Kommo's own integration — the one that talks directly to Cloud API. The older integration named "WhatsApp Business API" is no longer supported; Kommo has moved everyone to the new one.

Step 3. Click Install, then Continue with Facebook. Meta's authorisation window opens.

Step 4. Log into Facebook and pick your Business Portfolio. If you do not have one, create it here. Enter your legal company name and website.

Step 5. Create or select a WhatsApp Business Account (WABA). This is the container your numbers and templates will live in. Name it something meaningful — not "WABA 1", but your company or business unit name.

Step 6. Fill in the business profile. Display name, category, description, address, website, avatar. This is what the customer sees in the chat card. The display name goes through Meta moderation and must match your real brand — "Sales 2024" will not pass.

Step 7. Enter and verify the number. Choose SMS or voice call, then enter the code.

Step 8. Wait for the redirect back to Kommo. The system checks whether the number is already used in other Kommo integrations and offers to merge the data if it finds a match.

Step 9. Set up templates. Kommo will prompt you to submit your first templates to Meta for review. Templates from a previous integration migrate automatically.

Step 10. Add a payment method in Meta Business Manager. Payments → Add payment method. Without it the channel runs until it hits the threshold, then stops.

Step 11. Distribute access across your team. In Kommo: Settings → Users → permissions for the WhatsApp source. Decide who sees all conversations and who sees only their own.

Step 12. Run a test. Message the work number from your personal one and check: did a deal get created, did an owner get assigned, did the bot fire, did the notification arrive?

Without verification you operate under constraints: up to two numbers per portfolio and lower limits on business-initiated conversations. Verification requires documents proving the company exists — registration records, extracts, proof of address.

The most common rejection reason: the name in the documents does not match the name in the Meta profile character for character. The second most common: a website with no contact details and no mention of the legal entity name. Both take an hour to fix, but the resubmission cycle costs several more days.

New numbers start at a limit of 250 unique customers per day that you can message first. The limit then scales in tiers — 1,000, 10,000, 100,000, unlimited — based on volume and your number's quality rating.

Quality rating drops when users report or block you. Fall to "Low" and your limit freezes or shrinks. Fall critically and the number gets cut off from broadcasting entirely.

Practical takeaway: do not push the full database in the first two weeks. We normally start with a warm segment — everyone who messaged you in the last 90 days. They do not complain, the rating stays green, and the limit climbs on its own.

The most common blocker. Three scenarios, three different sets of actions.

Scenario 1. The number is on a regular personal WhatsApp. The painful one. To free the number for the API, the personal account has to be deleted, and the chat history will not follow you into Cloud API. What we do: export a chat backup (Settings → Chats → Chat backup), record the key contacts in the CRM manually or by import, and only then delete the account.

Scenario 2. The number is on the WhatsApp Business App. Good news: nothing needs deleting. Business accounts connect to Kommo without removal, precisely through coexistence mode. The number keeps working in the app while Kommo receives the same conversations.

Scenario 3. The number is already on another integration or provider. Meta supports automated migration between providers if the conditions are met: the number is registered, you have access to the WABA, and two-factor authentication is disabled for the duration. Meta migrates the number itself and your approved templates. Automations — bots, triggers, routing — reset to zero and need rebuilding.

The one rule of migration: do it in the quietest hour of the week. In the gap between deleting the old account and registering the number on Cloud API, inbound messages are not delivered — they simply vanish. On a Monday at 10am that costs you leads.

Messaging a customer first — that is, outside an open window — is only possible with an approved template. Every template goes through Meta review and gets a category, and that category drives the price directly.

Three categories:

• Utility — transactional: order confirmation, delivery status, appointment reminder, booking change. Cheap.
• Authentication — verification codes and one-time passwords. Cheap, with their own formatting rules.
• Marketing — everything else: promotions, discounts, re-engagement, "we launched a new service line." The most expensive category, and it never gets volume discounts.

The line between utility and marketing is intent. "Your order #1024 has shipped" is utility. "Your order has shipped, and here's a promo code for your next one" is marketing — in the same sentence. Meta re-categorises automatically when content does not match the declared category.

1. A variable at the very start or end of the text. {{1}}, welcome! gets rejected. Variables must be surrounded by text on both sides.
2. Two variables in a row. Meta reads {{1}} {{2}} as an attempt to bypass review.
3. An empty or meaningless sample value. If your example for {{1}} is "text", it will not pass. Use something real: "Elena", "#1024".
4. Category does not match content. Declared utility with a discount inside it means rejection, or automatic re-categorisation to marketing with a new price.
5. Promises and guarantees. "We guarantee 40% sales growth" is a red flag for reviewers.
6. Errors and markup. Stray characters, broken links, HTML tags, truncated text.

Example that gets rejected:
{{1}}, we have 50% off! Today only! Message {{2}}

Same meaning, this one passes:
Hello {{1}}. Until August 15 there's 50% off the "Foundations" online course. To reserve your spot, tap the button below. [Button: Reserve a spot]

The difference is not politeness, it is structure: the variable sits inside the text, the deadline is specific, the action is specific, and there is no cascade of exclamation marks.

Review usually takes anywhere from a few minutes to a day. We always submit templates as a batch 2–3 days before a campaign launches, never on launch day.

Keep 5–8 base templates live for recurring scenarios: re-engagement, appointment reminder, order confirmation, review request, abandoned cart. In our projects, one well-written re-engagement template brings 8–14% of a database that has been silent for 60+ days back into conversation.

Templates are half the job. The other half is what happens after the customer replies: who picks it up, how fast, and following which script. That is where automation comes in, taking the first two or three qualification steps off your reps.

The mechanics are simple, and they are what determines your invoice.

A customer messages you and a 24-hour customer service window opens. Inside that window you can send anything, free-form, no templates required. Every new message from the customer resets the window.

Once the window closes, free-form messages stop being delivered. Sending plain text outside the window returns an error. From that point it is templates only, and templates cost money.

Special case: if the customer arrived via a Click-to-WhatsApp ad or a button on your Facebook page, a free 72-hour window opens. Everything you send inside it, templates included, is not billed. For businesses driving paid traffic into WhatsApp, this is the cheapest communication channel in existence.

This is where honesty matters, because most guides online have not caught up yet.

Today, agent replies inside the window are free. From October 1, 2026 Meta starts charging for service messages at a rate equal to the utility rate of the relevant market. No volume discounts apply to this category. Separately, dedicated pricing for the Meta Business Agent takes effect on August 1, 2026.

In practice: a conversation with 15 messages from your rep, which costs nothing today, becomes a paid line item from October. Exact figures for several markets were not published at the time of writing — Meta committed to releasing them by September 1, 2026.

In our experience, three quarters of lost WhatsApp leads are not a pricing problem — they are a response-time problem.

1. First reply within 5 minutes. In Kommo this is handled by notifications plus automatic owner assignment on inbound messages.
2. A trigger at hour 20 of the window. If the conversation is still open and the customer has gone quiet, a bot sends a short clarifying message; the customer's reply resets the window.
3. A task for the rep at hour 23. Not an automated message — a human touch, on deals that justify it.
4. After the window closes, one re-engagement template. Not spam. One template, relevant to the deal stage. Not three in a row.
5. Check where the conversation started. If it came from an ad, you have 72 hours, not 24. Kommo shows the source in the card.

In teams where we have implemented this routine, the share of conversations reaching the target action typically rises over the first six to eight weeks — simply because the gap between "customer wrote" and "rep noticed" disappears.

Two facts break every older calculation.

Fact one. On July 1, 2025 Meta dropped 24-hour conversation-based billing and moved to per-delivered-template-message pricing. Every "cost per conversation" calculator is now obsolete. You pay only for delivery — undelivered messages are not billed.

Fact two. Price depends on the recipient's country, not on where your business is registered. A number writing to a customer in Germany pays the German rate.

Kommo does not add a markup on messages — you pay Meta directly from a linked card on a threshold model. So your budget is two components: the Kommo subscription per user, plus the Meta invoice for messages.

Take a typical month for a service business: 1,000 conversations, 600 of them customer-initiated and 400 initiated by you.

The rates above are planning estimates for a mid-cost European region. Meta revises its rate card quarterly, so check the current WhatsApp calculator in Kommo or Meta's live rate card before signing off a budget. Several markets move to standalone, higher-rate pricing on October 1, 2026 — build in headroom.

Scenario A. Service business (dental, auto repair, salon). 80% inbound traffic; outbound is appointment reminders, i.e. utility. The Meta invoice is negligible. Your real cost is the CRM subscription.

Scenario B. E-commerce with broadcasts. 2,000 marketing templates a month across the database. At $0.05 that is $100 for the broadcast alone, before any conversations. Here every percentage point of segment relevance converts directly into money.

Scenario C. Paid-traffic business. All communication starts from Click-to-WhatsApp, so 72 hours are free. The Meta invoice is near zero and the real cost is your ad budget. The most economical configuration we have seen.

We do not sell channels people do not need, so let us be direct.

WhatsApp penetration varies enormously by market. In some countries it is how business is simply done; in others — Ukraine included — it sits behind Telegram and Viber for domestic audiences. If your customers are local and your competitors reach them on another messenger, WhatsApp will be your third channel, not your first.

Where WhatsApp delivers most: export and cross-border sales, tourism and relocation services, diaspora-facing businesses, and B2B with Latin America, India, the Middle East and Southern Europe.

Payments. Meta charges a card that clears international payments. For some companies this is a separate conversation with finance, and it is better closed before connecting than when the channel stops at the payment threshold.

Rules change faster than guides get written. The pricing model has changed twice in the last eighteen months, and a third change is already scheduled for October. Building a process that depends on a single channel is risky. Building it in a CRM, where a channel is just a source you can swap or supplement, is sensible.

Run through this before you turn on traffic.

• Number verified, profile complete, avatar and display name approved
• Meta Business Portfolio verified (or verification in progress)
• Payment method linked, payment threshold understood
• At least 5 base templates approved
• Template categories checked against actual content
• Automatic owner assignment on inbound configured
• Hour-20 window trigger working
• Team access permissions distributed
• Test conversation created a deal at the correct pipeline stage
• Team briefed on coexistence-mode limitations
• Q4 budget recalculated for the October 1 changes

We at Brutal Marketing will select the best CRM program for you to use in your business. We will be happy to tell you about the program's capabilities and show you which settings will exactly help you achieve the desired financial results.

We handle the whole chain: WABA registration, Meta business verification, number migration without losing conversations, template approval, and automation configured around your pipeline. You get a channel that works from day one and a team that knows what to do with it.

Get Kommo CRM implemented with WhatsApp — on a free consultation we'll review your case, calculate your messaging budget, and tell you honestly whether this channel is right for you at all.