WhatsApp Coexistence Mode: Keep Your App and Add the API
For years, connecting a number to the WhatsApp Cloud API meant giving up the WhatsApp Business app on that number. Coexistence changed that. It is a Meta feature that lets the app and the API run on the same number at the same time, so a team can add a shared inbox and automation without losing the familiar app or their chat history. This page explains how it works and why it removes the biggest reason teams hesitated to upgrade.
Last updated July 5, 2026
Short answer
Coexistence is a Meta feature that lets you use the WhatsApp Business app and the Cloud API on the same number at the same time, without losing your chats. Connecting the API used to deactivate the app; Coexistence keeps both live, so your team keeps the familiar app for one-to-one chats while a shared inbox handles team messaging on the same number. This is how marv.Inbox connects you, so you keep your number and history.
What changes on your WhatsApp Business app after you add the Cloud API
| Feature | What happens after you add the Cloud API | Works through the Cloud API? |
|---|---|---|
| Individual (1:1) chats | Message edit and revoke start working, up to 6 months of recent chats sync in, and every message you send or receive mirrors between the app and the shared inbox. | Yes |
| Contacts | No change. Every contact with a WhatsApp number can sync across. | Yes |
| Group chats | No change in the app, but group chats do not sync into the shared inbox. | No |
| Disappearing messages | Turned off for all 1:1 chats. | No |
| View once messages | Disabled for all 1:1 chats. | No |
| Live location | Disabled for all 1:1 chats. | No |
| Broadcast lists | Existing lists become read-only and you can no longer create new ones. Send at scale with approved templates from the inbox instead. | No |
| Voice and video calls | No change in the app. | No |
| Business tools | No change in the app. This covers your catalog, orders, and status. | No |
| Messaging tools | No change in the app. This covers greeting and away messages, quick replies, and labels. | No |
| Business profile | No change in the app. This covers your business name, address, and website. | No |
| Channels | No change in the app. | No |
| Linked devices | Your companion apps unlink once during setup, then you re-link the ones you want. All companion clients work except WhatsApp for Windows and for WearOS. | Most |
Group chats and the disabled message types stay in the WhatsApp Business app and are not carried into the shared inbox. If someone messages you from an unsupported companion device (WhatsApp for Windows or WearOS), the message will not reach the inbox, and messages you send may appear there as placeholder text until they open their primary phone.
Why teams search for this
The problem Coexistence solves
The old all-or-nothing choice between the app and the API kept many teams stuck on a single phone. Coexistence ends that trade-off.
- ▲Before Coexistence, connecting the Cloud API deactivated the WhatsApp Business app on that number.
- ▲Teams feared losing their number, their chat history, and the simple app their staff already knew.
- ▲Coexistence keeps both live on one number, so the app and a shared inbox work side by side.
Workflow
How Coexistence works with marv.Inbox
Connect your existing WhatsApp Business app number to the Cloud API in Coexistence mode through marv.Inbox.
Keep using the app for one-to-one chats while the shared inbox handles team messaging, assignment and reporting on the same number.
Messages stay in sync and your history is not wiped, so the team gains structure without a disruptive migration.
What the better setup should include
Why Coexistence matters
Keep your number and app
No new number, no lost app. The same number serves both the WhatsApp Business app and your shared inbox.
No lost history
Connecting in Coexistence mode does not wipe your chats, so you do not start from zero when you add the API.
Add a team layer safely
marv.Inbox adds ownership, assignment, and a live view of queue load on top, without forcing the team off the app they know.
Best fit
Who Coexistence is for
- Teams that already run on the WhatsApp Business app and want a shared inbox without switching numbers.
- Businesses nervous about losing chat history or disrupting staff during an upgrade.
- Managers who want app simplicity for some staff and full inbox structure for the team, on one number.
Questions teams ask before changing the workflow
What is WhatsApp Coexistence mode?+
Coexistence is a Meta feature that lets you use the WhatsApp Business app and the Cloud API on the same number at the same time, without losing your chats. It replaces the old all-or-nothing choice between the app and the API.
Do I lose my chat history with Coexistence?+
No. Connecting in Coexistence mode keeps your existing chats and number. Your team keeps the WhatsApp Business app while a shared inbox handles team messaging on the same number.
Can I use the WhatsApp Business app and API at the same time?+
Yes, that is exactly what Coexistence enables. The app handles one-to-one chats and the API powers software like a shared inbox, both on one number, with messages kept in sync.
How does marv.Inbox use Coexistence?+
marv.Inbox connects your number in Coexistence mode so you keep your number, app and history, and the team gains a shared inbox with ownership, assignment, and queue reporting on top.
Do I have to delete my WhatsApp account to use the API?+
Not with Coexistence. Your existing WhatsApp Business app account and chats stay on the number while the Cloud API is added alongside them, so nothing is deleted. The only path that requires deleting the account first is a full Cloud API migration, where the number becomes an API-only sender and can no longer be used in the WhatsApp Business app. marv.Inbox connects you through Coexistence by default, so you keep your app.
What is the difference between Coexistence and a full Cloud API migration?+
Coexistence keeps the WhatsApp Business app and the Cloud API on the same number at once, with your recent history intact, and it is the guided way marv.Inbox connects you. A full Cloud API migration turns the number into an API-only sender: you delete or migrate the existing account first, the app stops working on that number, and the chat history does not carry over. Most teams pick Coexistence; full Cloud API fits a brand new API number or a setup that does not need the app at all.
Can I send a free-form message outside the 24-hour window in Coexistence?+
It depends which side you send from. From the API-based shared inbox the normal rule applies: inside the 24-hour customer service window you reply in free text, and once it closes you reopen the chat with a pre-approved template. The WhatsApp Business app on your phone is not bound by that window, so you can still open the app and send a free-form message to a past customer at any time, and in Coexistence that message syncs back into marv.Inbox. Use the app for a quick personal follow-up; planned re-engagement at scale still goes out as approved templates from the inbox.
Why would a business use Coexistence mode?+
Three reasons come up most. First, no downtime: you add the API to your existing number without deleting the app or losing history, so no customer message is missed during the switch. Second, you combine automation with people: the API runs the shared inbox, templates, and scheduled sends while staff still answer one-to-one from the familiar app on their phone. Third, you can add and test software, a shared inbox, a CRM link, or automation, on a live number while keeping the app as a fallback. marv.Inbox connects you this way by default.
Can I disconnect from the Cloud API and go back to the app on its own?+
Yes. In the WhatsApp Business app, open Settings > Account > Business Platform and tap Disconnect Account. The number returns to the app by itself and the Cloud API connection is removed, so the shared inbox stops sending and receiving on that number until you reconnect. Your existing chats in the app stay where they are.
See whether this workflow fits your team
Explore the product, then request a walkthrough if you want help mapping channels, ownership, automation, or rollout.