WhatsApp Coexistence: Running the Business App and Cloud API on the Same Number (2026)
Coexistence lets a business keep chatting from the WhatsApp Business app while a platform sends and automates messages through the Cloud API — on the very same phone number. It sounds simple. In practice, a narrow onboarding window, a hard throughput cap, and a long list of features that quietly stop working make it one of the easiest WhatsApp setups to get wrong.
What Coexistence actually is
Traditionally, moving a number onto the WhatsApp Cloud API meant giving up the WhatsApp Business app on that number — and losing the chat history with it. Coexistence removes that trade-off. A business can be onboarded onto the Cloud API through Embedded Signup while continuing to reply one-to-one from the Business app, and WhatsApp keeps the message history between the two in sync.
That makes it the natural path for SaaS tools, agencies, and chatbot platforms whose clients are not ready to abandon the familiar Business app but still want automation, templates, and higher volume through the API. If you are still deciding between the two, our WhatsApp Cloud API setup guide explains the standard (non-coexistence) path first.
What it unlocks — and what it quietly disables
Kept in sync
One-to-one chats are mirrored between the Business app and Cloud API, and up to six months of past chats plus WhatsApp contacts can be synchronized after onboarding.
Business app stays usable
Staff can still reply manually from the Business app; those messages are echoed to the platform so the conversation thread stays complete.
Disabled on the number
Group chats, disappearing messages, view-once, live location, and broadcast lists stop working on that number once it is onboarded to the Cloud API.
Business tools drop off
Catalog, orders, status, greeting and away messages, quick replies, labels, voice and video calls, and Channels are not supported on the API side.
Where Coexistence onboarding goes wrong
- The 24-hour sync window. After the business finishes onboarding, there is a hard 24-hour window to synchronize contacts and message history. Miss it and the customer has to be offboarded and taken through the whole flow again.
- A 20 messages-per-second ceiling. Numbers running in Coexistence are capped at a fixed throughput of 20 messages per second to stay compatible with the Business app — a real constraint for high-volume senders.
- Partner status required. Coexistence onboarding only works if you are already a Solution Partner or Tech Provider with a working Embedded Signup and webhook stack. It is not a self-serve toggle.
- Webhook coverage. The integration depends on additional webhook subscriptions — message history, contact state sync, and Business-app message echoes. Miss one and history, contacts, or manual replies silently fail to appear.
- App version and history sharing. The client must be on a recent Business app version, and history only transfers if they explicitly agree to share it — otherwise you get an empty-history signal, not an error you can retry.
- Offboarding is not an API call. You cannot deregister a Coexistence number through the API. Disconnecting has to be done by the client inside the Business app, which surprises teams expecting a clean programmatic teardown.
How a Coexistence setup comes together
Confirm eligibility
Partner status, Cloud API familiarity, a webhook endpoint that reliably digests events, and a client on a supported Business app version.
Prepare the onboarding flow
Embedded Signup is configured for Business-app onboarding and subscribed to the extra webhook fields before a single customer is invited.
Onboard and verify the number
The client connects their existing Business app number and the platform confirms the number is now registered for both the app and the Cloud API.
Synchronize immediately
Contacts and history are pulled within the 24-hour window, then new Business-app messages are mirrored on an ongoing basis.
Each of these steps hides configuration details that decide whether the sync completes or the number has to be re-onboarded. That is the part we handle end to end — this overview is deliberately high level.
What a correct setup gets you
Done properly, the client keeps their number, their conversations, and their familiar Business app, while your platform gains API messaging, templates, and automation on top — with new manual replies flowing back into the same thread. Done incorrectly, the most common results are a lost history sync, missing contacts, silent gaps where manual replies should appear, or a number stuck in a half-onboarded state that has to be torn down and rebuilt.
Coexistence, pricing, and the 24-hour window
Messages your client sends from the Business app stay free. Messages sent through the Cloud API follow standard Cloud API pricing, and the 24-hour customer-service window applies only to those API messages — a Business-app reply does not open or extend it. Teams that assume “same number, same rules” often miscost their rollout. If Business Verification or the underlying API approval is still outstanding, our WhatsApp API approval support and Embedded Signup onboarding guide cover what has to be in place first.
Frequently asked questions
Can a business use the WhatsApp Business app and the API at the same time?
Yes — that is exactly what Coexistence enables. The number runs on both, with one-to-one chats kept in sync between them.
Will the client lose their chat history?
No, provided the sync is done inside the 24-hour window after onboarding and the client agrees to share history. Up to six months of one-to-one chats can transfer; group chats do not.
Is there a volume limit?
Yes. Coexistence numbers are held to a fixed 20 messages-per-second throughput so they stay compatible with the Business app.
How does a client leave Coexistence?
Disconnection is done by the client from inside the Business app settings, not through an API call — the standard deregister endpoint is blocked for Coexistence numbers.
Facts here are based on Meta’s official WhatsApp Business Platform documentation (Coexistence / Business-app onboarding), reviewed July 2026. This is technical implementation guidance, not legal advice, and is not affiliated with or endorsed by Meta Platforms, Inc. Meta and WhatsApp make all onboarding, verification, and enforcement decisions independently; no specific outcome, sync result, or timeline can be guaranteed. Need a Coexistence setup handled correctly the first time? Reach out through the contact options in the footer.