waplyGuide
Connect WhatsApp Cloud API to Kommo: new number, Coexistence, or migration
You can connect WhatsApp to Kommo on Meta’s official Cloud API in three ways: a new number, Coexistence (same number on the WhatsApp Business app and Cloud API for messaging), or migration from another provider or prior Kommo WhatsApp path. Waply’s short docs cover the product clicks; this guide is the full decision path. Coexistence keeps the phone app for 1:1 messaging but Meta does not enable WhatsApp Calling API on coexistence-onboarded numbers. Waply uses official Cloud API only — messaging, human calls on eligible platform-only numbers, and independent AI.
Kommo support and blog pages already rank for “connect WhatsApp to Kommo” and coexistence. Waply’s own docs for connect-number and numbers-coexistence-migration are intentionally thin step lists. Use this guide to choose the path, understand Meta/Kommo limits (especially calls), and know when Waply’s official-API product is the right install — then follow the linked docs for the UI flow.
Free 3-day trial with everything in Voice AI.
Which path fits your number?
Before you open Meta Embedded Signup, identify how the number is used today. Picking the wrong path is the main reason teams disconnect too early or lose messaging during cutover.
Three official Cloud API paths for Kommo teams (Sept 2026)
| Path | When to use it | Phone app | WhatsApp Calling API |
|---|---|---|---|
| New number | Number is free for WhatsApp Business Platform, or you are starting clean | Not on WhatsApp Business app for that number | Possible on eligible platform-only numbers |
| Coexistence | Number already lives in WhatsApp Business app; you want CRM/API messaging without giving up the app | Stays active; 1:1 chats can sync | Not supported on Cloud API (Meta) |
| Migration | Number is on another BSP, prior WhatsApp API, or another Kommo WhatsApp integration | Usually not — platform-only after a full migrate | Possible after a successful platform-only migrate (eligibility still applies) |
Unofficial QR / “grey” session connectors are a different category. For Lite/QR history and vendor options, see the WhatsApp Lite in Kommo guide. This page stays on official Cloud API paths.
Connect a new Cloud API number
Use this path when the number is eligible for WhatsApp Business Platform onboarding and is not already tied to another Cloud API host you still need. High-level flow with Waply installed in Kommo:
- Install Waply in Kommo and open Numbers → Connect WhatsApp number.
- Complete Meta sign-in and select the Business Portfolio, WhatsApp Business Account, and phone number.
- Return to Waply and wait until the number shows as connected before turning on messaging automations or calls.
- Send a permitted test message (and a human call if the number is platform-only and Calling is enabled).
- You need access to the Meta Business Portfolio that will own the WhatsApp assets.
- Pending Meta verification or missing asset permissions must be fixed before the number can become ready.
- Meta conversation pricing and template rules apply on the Cloud API side; Waply subscription is separate.
Click-by-click screens live in Waply docs. This guide is the SEO/AEO answer for which path to pick; docs stay the product checklist.
Coexistence: keep the WhatsApp Business app
Coexistence (Meta’s “onboard WhatsApp Business app users” flow) lets the same number run on the WhatsApp Business app and Cloud API at once for synced 1:1 messaging. Kommo documents this for its WhatsApp Business integration; Waply supports coexistence numbers for messaging on official Cloud API.
What usually works
- 1:1 chats mirrored between the Business app and Cloud API / CRM inbox (per Meta + Kommo).
- Contacts sync as documented by Meta/Kommo for the coexistence flow.
- Cloud API templates and automation on the API side, while manual app chats can stay on the phone.
Critical limits (including calls)
- Voice and video calls: not supported on Cloud API for coexistence-onboarded numbers (Meta capability table). You may still place calls inside the WhatsApp Business app; they do not become Calling API sessions in the CRM.
- Group chats, broadcast lists, disappearing / view-once / live location messages, and several Business-app tools (catalog, status, Channels, etc.) are not synchronized to Cloud API — see Meta’s table and Kommo’s coexistence support article.
- Eligibility: Kommo notes supported country codes, WhatsApp Business app version requirements, and that brand-new Business app accounts are not immediately eligible — confirm in-product; do not invent a tenure day count.
- History import windows differ by product wording (Kommo support cites recent chats, on the order of the last ~30 days for its import path). Treat that as product documentation, not a Meta SLA.
If you need WhatsApp Calling API, recordings in the lead, or Voice AI on calls, plan a platform-only (non-coexistence) number. See the WhatsApp calls in Kommo guide.
Migrate from another provider or prior Kommo path
Migration moves a number that already sits on WhatsApp Business Platform (another BSP, an older API path, or another Kommo WhatsApp integration) onto the WhatsApp Business Account you will use with Waply/Kommo.
- Do not disconnect or delete the number from the old host “to fix a pending state” until Meta’s transfer path is clear — Waply and Kommo docs both warn about this.
- Kommo documents automatic vs manual migration. Automatic migration typically needs a verified Meta Business, an approved WABA, a valid payment method on the existing WABA, and two-step verification disabled on the phone number — confirm current Kommo/Meta checklists in support docs.
- Display name, quality-related limits, and eligible templates may transfer under Meta’s rules; automations often need reconfiguration after cutover.
- Numbers that only live in the WhatsApp Business app (no Cloud API yet) usually follow coexistence or a fresh platform register — not the “migrate from another BSP” article alone.
- Lite → WhatsApp Business inside Kommo has its own source-merging path; see the Lite guide rather than duplicating it here.
Soft-word: partner blogs sometimes compress migration into a single “one-click” story. Use Kommo’s migration articles and Meta’s phone-number guidance as the checklist, and test send/receive before turning off the old provider.
How Waply fits
Waply is an independent product installed in Kommo. It connects WhatsApp only through Meta’s official Cloud API — not unofficial QR/session connectors — and adds human WhatsApp calls (eligible numbers), call intelligence, and text/voice AI on third-party models.
Waply plans (USD, waply.online/pricing)
| Plan | Monthly | WhatsApp-relevant inclusions |
|---|---|---|
| Basic | USD 18 | Official-API messaging; human WhatsApp calls and recordings (90-day retention) |
| AI 24/7 | USD 39 | Everything in Basic + text AI agents, call intelligence allowances, 365-day retention |
| Voice AI | USD 89 | Everything in AI 24/7 + Voice AI agents on WhatsApp calls (managed/BYOK minutes) |
- 3-day free trial includes everything in Voice AI.
- Coexistence numbers: messaging can work; WhatsApp calls do not (Meta restriction).
- Waply AI does not consume Kommo native AI credits.
- Meta message and call charges are separate; BYOK usage is billed by your provider.
Frequently asked questions
How do I connect WhatsApp Cloud API to Kommo?
Install an official Cloud API integration (Kommo WhatsApp Business and/or Waply), complete Meta Embedded Signup, select the Business Portfolio / WABA / number, wait until the number shows connected, then test messaging. Exact screens are in Waply’s connect-number docs.
What is WhatsApp Coexistence in Kommo?
Coexistence lets the same number stay on the WhatsApp Business app and join Cloud API for synced 1:1 messaging. Kommo’s blog and support docs describe setup requirements (app version, Business Portfolio, supported countries). It is not the old WhatsApp Lite QR product.
Can I keep the Business app and still use WhatsApp calls in the CRM?
Messaging can sync under coexistence. Meta does not support voice/video Calling API on Cloud API for coexistence-onboarded numbers. For Calling API, recordings in the lead, or Voice AI on calls, use an eligible platform-only number.
How do I migrate a number from another provider?
Follow Meta’s number migration into the WABA you will use with Kommo/Waply. Kommo documents automatic vs manual paths and prerequisites (verified business, approved WABA, payment method, two-step verification off). Do not delete the number from the old host until the transfer path is clear.
Should I disconnect my old BSP before connecting?
Usually no — not until migration requirements are confirmed. Disconnecting early is a common cause of downtime. Identify whether you need coexistence, automatic migration, or manual release first.
Does Waply use unofficial QR WhatsApp?
No. Waply connects WhatsApp through Meta’s official Cloud API only.
What are Waply’s plans and is there a trial?
Basic is USD 18/month, AI 24/7 is USD 39/month, Voice AI is USD 89/month. The free 3-day trial includes everything in Voice AI. Meta and BYOK charges are separate when applicable.
Where are the click-by-click product steps?
In Waply docs: connect a number, and numbers / coexistence / migration. This guide explains which path to choose and the Meta/Kommo limits; docs stay the UI checklist.
Connect on an official path, then prove messaging
Choose new number, coexistence, or migration before you touch the old host. Install Waply when you want official Cloud API messaging in Kommo plus calls and independent AI on eligible numbers — with a 3-day Voice AI trial.
Free 3-day trial with everything in Voice AI.