WhatsApp coexistence is Meta's way of connecting a number that already runs on the WhatsApp Business app to the Cloud API without taking it off the phone. Once a provider onboards the number, the app keeps working, messages on either side are mirrored to the other, and the business can add a bot, a team inbox or template campaigns to the number its customers already saved. Meta's documentation calls it onboarding Business app users; providers say coexistence or Coex.

The app and the API can run on the same number at once, on Meta's terms. The connection goes through a Solution Partner's or Tech Provider's Embedded Signup, the app must be version 2.24.17 or later, and the number is held to 20 messages per second. Messages typed in the app stay free. Messages sent through the API follow Cloud API pricing, which since 1 October 2026 includes service replies beyond 1,000 a month per number. Broadcast lists, disappearing messages and a few other app features switch off.

What reaches the platform is the provider's call: Meta lets it pull contacts and up to six months of chats, and providers import anything from six months to nothing.

How onboarding works

The sequence, per Meta's coexistence page (updated 26 June 2026) and the providers' help pages:

  1. In the provider's panel, start the WhatsApp connection and log in with Facebook as an admin of your business portfolio; Meta's Embedded Signup window opens.
  2. Choose to connect an existing WhatsApp Business app and type the number with country code and DDD (+55 11…).
  3. The app receives a message from Facebook's business account. Tap Connect, then Connect to the Business Platform, and scan the QR code or enter the code shown in the browser.
  4. Decide in the app whether to share chat history. The provider can run the contact sync and the history sync once each; redoing either means disconnecting and starting over.
  5. Keep the app open until the provider confirms. Meta gives the provider 24 hours to synchronize, or the number has to be connected again.

At the end, the app shows the connection under Settings > Account > Business Platform, and every linked device is logged out.

Eligibility. Meta does not publish its criteria. Providers say new app accounts are not eligible right away: Huggy asks for chats with at least four contacts in the last five days, Gupshup for an account about three months old. No provider page read on 25 September 2026 lists Brazil as unsupported.

What syncs, and what your provider shows

What Meta makes available:

  • Contacts that have a WhatsApp number, plus later additions and edits.
  • One-to-one messages from the 180 days before onboarding; media only from the last 14 days.
  • New messages in both directions. A reply typed on the phone reaches the provider as a "message echo" webhook; an API message appears in the app.
  • Group chats: never synced.

What providers say they import (help pages, 25 September 2026):

ProviderHistory after connecting
WATIUp to 6 months of one-to-one chats and 2 weeks of media; contacts imported
BotmakerContacts and messages up to 6 months back
KommoChats active in the last 30 days; contact import can take 24 hours
InfobipMessage history through webhooks; contacts not yet synchronized
respond.ioNo contact or history sync yet; history stays in the app
Zenvia (Customer Cloud)Earlier chats and contacts not imported; chats started from the app do not appear

If your sales history lives in WhatsApp chats, get this answer in writing before you sign.

Two gaps apply to every provider. Messages from customers on WhatsApp for Windows or WearOS reach only the app. And a customer's first message, often right after a click-to-WhatsApp ad, can arrive as error 131060; Meta says this clears in seconds and the message is in the app.

What changes in the app

From Meta's feature comparison:

App featureIn the app after onboardingThrough the API
One-to-one chatsKeep working; edit and delete supportedSupported and mirrored
Group chatsNo changeNot available
Broadcast listsNo new lists; existing ones read-onlyNot supported
Disappearing, view-once and live location messagesTurned off in one-to-one chatsNot supported
Voice and video callsNo changeNot supported
Catalog, orders, status, channels, greeting and away messages, quick replies, labelsNo changeNot supported
Linked devicesAll logged out; up to four can be linked again, except WhatsApp for Windows and WearOSNot applicable

Broadcast lists are what a Brazilian shop misses first: the weekly promotions list turns read-only, and its replacement is a marketing template sent through the provider to opted-in customers, paid per delivery (bulk messaging on the official API). The catalog stays in the app but cannot be sent through the API (catalog guide). WATI tells customers to switch off the app's greeting and away messages before using its automations, and Botmaker pauses its bot when someone answers from the phone.

Some limits come from providers, not Meta's page. 360dialog's docs say coexistence numbers cannot get an Official Business Account (Meta Verified is the alternative), cannot move to another WABA and cannot use the Calling API. Digisac says no verification badge can be requested while a number is in CoEx. An existing Meta Verified badge is kept, per 360dialog and respond.io (verified badge guide).

Keeping the connection alive

  • Open the app on the main phone. Meta drops the API side when the primary phone has been idle for about 14 days (a linked device, about 30); 360dialog says to open the app at least every 13 days.
  • Don't uninstall the app, change the number or register it on the regular WhatsApp app. Each one removes the API side.
  • Changing phones. The API side drops automatically; during registration on the new phone, a pre-checked option restores it within minutes (Meta, reconnecting clients). WhatsApp Web must be linked again, and API sends fail meanwhile.
  • Leaving. In the app, Settings > Account > Business Platform > Disconnect. The provider cannot deregister the number through the API.
  • Changing providers. Remove the old partner in Meta Business Suite and in the app first, as Manychat's guide describes.

To take a number off the app for good, see numbers for WhatsApp Business.

What coexistence costs since 1 October 2026

Meta charges only for what goes out through the API:

  • Messages typed in the app (phone, WhatsApp Web, other linked devices): free. Per Meta, they do not open or extend the 24-hour window and do not affect Cloud API pricing.
  • Replies sent through the API inside the 24-hour window, by a bot or an agent in the provider's inbox: 1,000 free per number per month, then R$0.0350 each (Meta, pricing).
  • Templates, which only the API side can send: R$0.3217 per marketing template, R$0.0350 per utility template, and R$0.0350 for a utility template sent inside an open window.

The API's 24-hour window opens only when the customer writes after onboarding; a message from just before can be answered through the API only with a template.

That makes the cheapest setup plain: the platform handles the bot, order updates and campaigns, and people chat from the app. Agents replying in the provider's inbox use up the free tier; replies typed on the phone never touch it. The catches: the phone has no shared queue for a team, and providers bill app messages their own way. respond.io counts echo messages toward Monthly Active Contacts; SendPulse says manual app messages are not billed. The webhooks guide covers how echoes reach a CRM.

Providers in the catalog that document coexistence

Every platform in the catalog was checked for a public coexistence page on 25 September 2026. These describe it. Price and setup fee are for each platform's cheapest official-API plan, which may not include coexistence:

PlatformWhat its own page saysPriceSetup fee
360dialogApp must be opened every 13 daysfrom €49/monthNo setup fee
Blip GoNumber needs a history of customer chatsfrom R$389/monthNo setup fee
BotConversaOfficial-API plans only, not the QR connectionfrom R$299/monthSetup fee not published
BotmakerContacts and 6 months of chats migratedfrom R$600/monthSetup fee unclear: sources disagree
DigisacVia 360dialog, activated by Digisac analystsfrom R$197/month + official WhatsApp API on requestNo setup fee
GupshupSelf-serve; lists known issues on Meta's sideNo monthly fee, pay per messageNo setup fee
Huggy"Conecte seu app WhatsApp Business existente"from R$729/monthNo required setup fee (optional service R$1,250)
Infobip20 messages per secondfrom $530/month+ one-time setup fee on request
KommoAny plan or trialfrom $20/monthNo setup fee
ManychatLabeled betafrom $39/monthSetup fee not published
respond.ioNo history sync yetfrom $99/monthSetup fee not published
SendPulseManual app messages not billedfrom R$95/monthNo setup fee
WATIEnabled on requestfrom R$369/monthNo setup fee
ZenviaEarlier history not importedfrom R$100/month+ R$649 one-time setup

Not found on public pages: Blip Platform, RD Station Conversas, Sinch, Treble, Twilio, Umbler Talk and VTEX CX Platform (Weni). Octadesk's activation article has you delete the WhatsApp account on a number already in use, and a Poli Digital blog post updated 14 August 2026 says coexistence is in testing for release in 2026. Not found does not mean not offered; ask the vendor.

When coexistence is a poor fit

  • You need the blue check. Per 360dialog, an Official Business Account is not available on coexistence numbers.
  • You send at volume. 20 messages per second is the ceiling; an API-only number starts at 80 and can be upgraded to 1,000 (Meta, throughput).
  • Sales run through groups or broadcast lists in the app.
  • The team works in WhatsApp for Windows.
  • Nobody opens the app on the main phone for two weeks at a time.

Then an API-only number fits better: how the WhatsApp Cloud API works and how to choose a BSP.

About this guide

Written by the editorial team of WABA Index, an independent catalog of WhatsApp Business platforms for companies selling to customers in Brazil. No platform pays for its position or a mention, and this page has no affiliate links.

Methodology

On 25 September 2026 the editors read Meta's developer documentation on coexistence (updated 26 June 2026), reconnection, throughput and pricing (updated 10 September 2026), Meta's PDF on API solutions for Business app users, 360dialog's note on service-message charging, and the coexistence or connection pages of every platform in the catalog. Meta rates, the free tier, prices and setup fees come from the catalog data. Nothing was tested hands-on, and no number was connected to any provider.

Last updated

31 October 2026. Facts and sources were checked on 25 September 2026; prices, Meta rates and scores in the tables are read from the catalog data when the page loads.

FAQ

Is WhatsApp coexistence free?

Meta charges nothing to connect, and app messages stay free. API messages follow Meta's rates, plus the provider's plan and any setup fee.

Does WhatsApp Web still work with coexistence?

Yes, after you link it again. WhatsApp for Windows and WearOS are not supported.

Can I still send broadcasts from the app?

No new broadcast lists, and existing ones become read-only. Campaigns go out as marketing templates through the provider.

How do I stop using coexistence?

In the app, open Settings > Account > Business Platform and tap Disconnect. The app keeps the same number and chats.