WhatsApp coexistence lets a business keep its number on the WhatsApp Business app and connect the same number to the Cloud API. The team goes on replying from the phone, while software sends templates, automations and AI replies through the API. Meta's name for it is onboarding WhatsApp Business app users, and it only works through a partner's Embedded Signup.
This guide covers what coexistence changes in the app, what it does not carry over to the API, how the history sync works, how the two sides are billed, and when a dedicated number is the better choice.
What coexistence is, in one paragraph
Under ordinary registration a number lives in one place. To put an app number on the API you delete the app account first, and the chat history of that account goes with it. Coexistence removes that step: the owner scans a QR code inside Embedded Signup, the number is onboarded to the Cloud API and the app keeps working. Messages sent from the phone are echoed to the partner's software, and messages sent by the software show up in the app, so both sides see one conversation.
What you need before you start
A recent app. Meta's documentation asks for WhatsApp Business app version 2.24.17 or higher. The consumer WhatsApp app is not part of this flow: the number must be on the Business app.
A partner allowed to run it. Only a Solution Partner or a Tech Provider can offer the flow, through Embedded Signup. A business cannot enable coexistence alone from its Meta settings, so the first question for a vendor is whether it supports this specific onboarding. The wider criteria are in the guide to choosing a WhatsApp BSP.
Check your country with the partner. Vendor articles disagree on which country codes are supported and when exclusions were lifted, and the Meta page we read lists no excluded regions. Ask the partner to confirm for your number before planning around it.
Everything else the API needs. Business portfolio, payment method, display name and business verification work as in any activation. Those steps are in how to activate WhatsApp Business API and are not repeated here.
What changes in the app the day you connect
Linked devices are unlinked. At onboarding every companion device is disconnected. You can link them again afterwards, up to four, except WhatsApp for Windows and WhatsApp for WearOS, which Meta lists as unsupported.
Broadcast lists stop. Existing lists become read-only and new ones cannot be created. Bulk sends move to approved templates on the API.
Three chat features switch off. Disappearing messages, view once and live location are turned off for one-to-one chats, because the Cloud API does not support them.
Groups stay on the phone. Group chats keep working in the app but are not synchronised to the API, so the shared inbox or the bot never sees them.
Calls are an app matter. Voice and video calls are not supported on the Cloud API side of a coexistence number.
Editing and deleting a message still work, and the partner receives the change through webhooks.
History and contacts: one chance, 24 hours
During onboarding the owner chooses whether to share chat history. If they agree, Meta can synchronise the one-to-one messages of the most recent six months and all contacts that have a WhatsApp number.
The window is short. The partner has 24 hours from onboarding to start the synchronisation. After that the business must be offboarded and go through the flow again. The step can be run once per onboarding.
The owner can refuse. Sharing history is a choice. Before accepting, check that passing six months of customer conversations to a new processor is covered by your privacy notice and by a data processing agreement with the vendor. This is not legal advice.
How it is billed
App messages stay free. Meta states that messages the business sends from the WhatsApp Business app continue to be free.
API messages follow Cloud API pricing. Templates are charged per delivered message by category, and free-form replies sent through the API are service messages, with the allowance and rates described in the WhatsApp Business API cost guide.
The trap is the window. A message typed on the phone does not create, extend or affect the Cloud API customer service window. If a customer wrote before the number was onboarded, or more than 24 hours ago, the software can only answer with a template, even if a colleague replied from the app a minute earlier. Teams that mix manual and automated replies need to know which side is answering.
The limits that decide whether it fits
Throughput is fixed at 20 messages per second. A number used with both the app and the API cannot go above it. For a shop sending a few thousand order updates a day it is irrelevant. For a large campaign with a tight delivery time it is a ceiling.
The phone has to stay alive. Among the reasons Meta lists for a disconnection is a primary device inactive for about 14 days, and a companion device inactive for about 30. A number parked in a drawer is not a coexistence number for long.
The owner can pull the plug. In the app, Settings, Account, Business Platform has a Disconnect Account button. The partner is notified, and its Deregister call cannot be used on a number that is active on both sides. Decide who in the company holds that phone.
When coexistence is the wrong choice
If nobody replies by hand any more, the app adds nothing: you inherit the 20 messages per second cap and the dependence on a physical phone for no benefit, and a dedicated API number is cleaner. The same goes for a team that works mainly in WhatsApp groups or relies on calls, because neither reaches the API.
It is also the wrong tool for changing vendor. Moving an API number from one provider to another is a different procedure, described in migrating a WhatsApp number between BSPs.
Coexistence fits one situation well: the number on the shop window is the asset, people still answer from the phone, and you want automation on top without asking customers to save a new contact.
TikJoy runs on the official WhatsApp Business API and connects the number to an AI concierge, orders and cashback. See how the WhatsApp AI Concierge works.