On this page
Too long? Read this
- Coexistence lets one WhatsApp Business number work in the app on the owner's phone and on the API in a team inbox at the same time, with up to six months of history imported
- Messages sent from either side appear in both; the team gets automation, templates, broadcasts and the CRM while the owner keeps the phone
- Limits: a lower send rate (4 per second), some interactive message restrictions, and the number must be on the app for a short period first
- Setup is Embedded Signup with a QR scan on the phone; disconnecting later converts the number to API-only
For years the answer was no: the WhatsApp Business app and the Business API were mutually exclusive, and moving to the API meant the owner giving up the phone. Since Meta released coexistence, the answer is yes. One number can run in the app on the owner's phone and on the API in a team inbox at the same time, with history imported and messages mirrored. This guide explains how coexistence works, what it syncs, its limits, how to set it up, and the few cases where API-only is still the better choice.
What coexistence is
Coexistence is a Meta feature that registers a WhatsApp Business app number on the Cloud API without deregistering it from the app. The phone keeps working exactly as before; the API side receives every incoming message by webhook and can send through the same number; and messages sent from either side are echoed to the other so both show the full conversation. Meta introduced it in 2024 for Tech Providers and BSPs and it is generally available in 2026.
What syncs
| Item | Coexistence behaviour |
|---|---|
| Incoming messages | Delivered to the app and to the API inbox |
| Replies from the app | Shown in the inbox as sent by the owner |
| Replies from the inbox, flows, AI, broadcasts | Shown in the app as sent |
| Chat history | Up to six months imported at connection |
| Contacts | Imported with the history |
| Labels, quick replies, catalog in the app | Stay in the app; the API has its own |
| Business profile | Shared |
| Groups and communities | App only |
| Status | App only |
What the team gets that the app cannot do
A shared inbox with assignment and history for every teammate; templates for messaging outside the 24-hour window; broadcasts to any number of consenting contacts with delivery protection, instead of 256-contact lists that reach only people who saved the number; chatbot flows, AI replies and sequences; leads, appointments and payments; Instagram, Messenger and website chats in the same inbox; and reporting. The owner keeps the phone for their own conversations and can watch everything.
The limits
- Send rate. Meta rate-limits coexistence numbers more tightly; VGraple CRM paces them at 4 messages per second, so a 5,000-recipient broadcast takes about 20 minutes rather than 2.
- Interactive messages. Some interactive types and WhatsApp Flows have restrictions on coexistence numbers; buttons, lists, templates and media work.
- Eligibility. The number must have been in use on the WhatsApp Business app for a short period, and the app must be up to date.
- One phone. The app side remains a single device (plus linked devices as WhatsApp allows); the team side is unlimited.
- Groups. Group messages stay in the app; the API does not receive them.
How to set it up
- In VGraple CRM go to Settings, then Channels, click Connect WhatsApp, and choose the option to keep using the WhatsApp Business app.
- Sign in to Meta in the pop-up, select or create the Business Portfolio, and confirm the number.
- On the phone, open the WhatsApp Business app, go to Settings, Linked devices or the prompt that appears, and scan the QR code shown.
- Wait for the history import; large histories take a few minutes.
- The channel shows Connected with a coexistence badge. Send a test from the phone and from the inbox and confirm both appear in both places.
The coexistence setup guide has screenshots and troubleshooting, including what to do when history does not import.
A day with coexistence
Morning: the owner replies to two regulars from the phone on the way in; both replies appear in the inbox, so the desk does not repeat them. Ten o'clock: a broadcast to 800 consenting customers goes out from the inbox at the coexistence pace, taking a few minutes; replies land in the inbox and the owner sees them scroll by on the phone. Afternoon: the AI answers price questions from the knowledge base while the team is busy; the owner watches and steps in on one, which pauses the bot for that conversation. Evening: the owner answers a late enquiry from the phone; the flow picks it up the next morning when the customer taps Book. Nothing was duplicated, nothing was missed, and the owner never gave up the phone.
What changed in 2025 and 2026
Coexistence moved from limited availability to general availability, history import grew to six months, and the set of message types allowed on coexistence numbers widened; the send rate limits remain tighter than API-only numbers. Meta's pricing changes (per-message billing from July 2025, portfolio-level limits from October 2025) apply identically to coexistence and API-only numbers.
When API-only is the better choice
- A high-volume marketing operation that needs the full send rate.
- A number that will be used only by a team, with no owner phone.
- Businesses that want interactive message types restricted on coexistence, such as some WhatsApp Flows.
- Numbers that are already API-only; they cannot be moved to the app without deregistering.
In those cases the number is registered API-only through Embedded Signup and the app is no longer used for it; the owner can still use the Android app or the web inbox.
Numbers and limits
Coexistence numbers follow the same messaging tiers and portfolio-level limits as API-only numbers, and the same per-message pricing; the only extra constraint is the tighter send rate Meta applies.
Common questions from owners
"Will my customers notice?" No; the number, name and profile are unchanged. "Can I still reply from my phone at night?" Yes, and the reply shows in the inbox so the team does not repeat it. "What happens to my labels and quick replies?" They stay in the app; the inbox has tags and quick replies of its own. "Can I go back?" Disconnect from VGraple CRM and the number continues in the app as before.
The coexistence feature page lists every limitation Meta currently applies; the app vs API guide compares the two models in full.
Coexistence is the default recommendation for owner-run businesses in India for exactly that reason.