RevoplyAI Team
Aug 6, 2026
WhatsApp Coexistence: One Number, App and API
For years, connecting your business number to the official WhatsApp Business API meant giving something up. The number had to be migrated, the WhatsApp Business app on your phone stopped working for it, and your team lost the simple thing they actually liked — tapping a chat and typing a reply. Plenty of small businesses looked at that trade and decided the API wasn't worth it. Coexistence removes the trade. Meta now lets you connect a number that is already live in the WhatsApp Business app to the API, and keep using the app exactly as before. No migration, no downtime, no lost history. This guide covers what coexistence actually is, what you need before you start, what syncs and what doesn't, and the limitations nobody mentions until after you've connected.
What is WhatsApp coexistence?
Coexistence — Meta's own documentation files it under onboarding WhatsApp Business app users, and you'll also see it sold as "Quick Start" — lets a single phone number run on the WhatsApp Business app and the WhatsApp Cloud API at the same time. Both sides stay in sync in both directions. A reply your colleague types on their phone and a reply an AI assistant sends through the API land in the same thread, and your customer sees one number and one continuous conversation. Technically, messages sent from the app fire a webhook back to the platform so the API side knows what was said; that's what keeps the two views from drifting apart.
The practical consequence is worth stating plainly: the app is not demoted. It is not a read-only mirror or a fallback. Your team keeps answering from their phones, and everything they send shows up in the platform inbox alongside the automated replies. If you're still deciding which tier your business needs at all, our guide on WhatsApp Business app vs API covers the underlying difference.
Who is coexistence actually for?
It fits a specific and very common situation: a business already running on the WhatsApp Business app, with real history and real customers on that number, that wants automation without disruption. The classic examples are a shop where the owner still answers personally in the evenings, a clinic whose receptionist handles bookings by hand, or a small team that shares one phone. All of them want an AI assistant for the repetitive questions and the 2 a.m. messages — but none of them can afford a week of migration, and none want to tell customers to save a new number.
It fits less well if you are starting from scratch with a brand-new number, in which case there is nothing to preserve and a normal API onboarding is simpler. It also fits badly if you need very high throughput or the blue Official Business Account badge, both of which are constrained on coexistence — see the limitations below.
What you need before you start
| Requirement | Detail |
|---|---|
| WhatsApp Business app v2.24.17 or newer | The hard version floor. Update from your app store before you begin — older builds simply won't offer the option |
| A number already active in the app | Coexistence goes app first, API second. A number that was never registered in the WhatsApp Business app has nothing to coexist with |
| Not already connected to the Cloud API elsewhere | One number, one API connection. If another provider still holds it, release it there first |
| A Meta business portfolio with admin access | You sign in during setup, so you need an account that can actually approve the connection — not a colleague's |
| A supported country | Availability has expanded steadily, but Meta has excluded certain countries at various points. If the option doesn't appear, this is a likely cause |
How to connect your number, step by step
The flow runs inside Meta's own embedded signup window, so it looks the same whichever platform you connect through. Budget ten minutes, and have the phone with the WhatsApp Business app in your hand — you will need to scan a QR code with it.
- Update the app first. Confirm you are on v2.24.17 or newer before anything else, or the connection option will not be offered.
- Start the connection from your platform — in RevoplyAI, that is the Channels page — and sign in with your Meta admin account.
- Choose "connect an existing WhatsApp Business app account" rather than registering a new number. This is the branch that makes it coexistence; pick the wrong one and you are doing a migration.
- Enter the number with its country code, and confirm your business name and time zone.
- Scan the QR code with the WhatsApp Business app on the phone that owns the number, then approve the request that arrives as a WhatsApp message.
- Decide about chat history — carefully. You are asked once whether to sync your existing conversations. Say yes. See the warning below.
- Wait for provisioning, typically a couple of minutes, then send a test message from your phone and confirm it appears in the platform inbox.
The one irreversible moment: chat history is synced only during onboarding. If you skip that prompt and change your mind next week, the only way back is to disconnect the number and run the whole onboarding again. It costs nothing to accept it, so accept it.
What syncs, and what doesn't
| Data | What to expect |
|---|---|
| Contacts | Imported automatically during setup, in the background |
| One-to-one chat history | Up to roughly six months. Recent conversations appear almost immediately; older ones fill in gradually |
| Media (photos, files) | A much shorter window than text — commonly reported as about two weeks |
| Group chats | Not synced, and not available through the API. They stay in the app, untouched, and you keep using them there |
| New messages, in both directions | Continuously, from the moment you connect. This is the part that makes it coexistence rather than a one-time import |
Exact figures vary a little between providers' documentation, so treat the durations as the right order of magnitude rather than a contract. The shape is reliable: contacts and months of text, days of media, no groups.
What changes inside the app after you connect
This is the section most write-ups skip, and it is the one that causes support tickets. Coexistence is generous but not free of consequences — a handful of app features are switched off, because the API has no way to represent them.
- Keep the app installed, and open it regularly. Uninstalling breaks the connection. Providers also report an inactivity limit — open the app at least once every couple of weeks to be safe.
- Disappearing messages and view-once media stop working on that number. Both depend on the message vanishing, which an API-side copy defeats.
- Live location sharing is disabled, since a continuously updating position has nothing to sync to.
- Broadcast lists effectively retire. Bulk sending moves to the platform side, where it is subject to template rules — and, done carelessly, to ban risk. Our guide on sending bulk WhatsApp messages without getting banned is worth reading before your first campaign.
- Companion devices are limited. WhatsApp for Windows and WearOS aren't supported alongside coexistence, and linked devices are typically unlinked during setup.
- The blue Official Business Account badge isn't available for coexistence numbers. If that badge is a hard requirement, coexistence is the wrong path.
- Throughput is capped below what a fully migrated API number can push. Reported limits differ between providers, so check yours before planning a large campaign — for everyday support volume it is a non-issue.
None of this touches the thing that matters most day to day: your team still answers from the phone, and the number keeps its identity, its history, and its customers.
Does coexistence risk getting my number banned?
No — and the reason is worth being precise about, because the fear is well founded in general. WhatsApp bans come overwhelmingly from unofficial automation: modified clients, web-scraping bots, and tools that drive the consumer app through the back door. Coexistence is the opposite of that. It is a first-party Meta feature, connecting through the official Cloud API, with the connection approved from your own phone. You are doing the sanctioned thing, in the sanctioned way.
What can still get a number restricted is behaviour — messaging people who never opted in, blasting templates that get reported, ignoring a falling quality rating. That risk exists identically whether you migrate or coexist, and it is about how you message, not which door you came through. If the number is new to high-volume messaging, our WhatsApp number warm-up guide explains how to build up sending safely.
Coexistence or full migration: which should you choose?
| Coexistence | Full migration | |
|---|---|---|
| Phone app on that number | Keeps working, unchanged | Stops working for that number |
| Existing chats and contacts | Synced during onboarding | Left behind in the app |
| Downtime | Essentially none | A gap during the switch |
| Throughput ceiling | Capped | Full API rates |
| Blue OBA badge | Not available | Available if you qualify |
| Best for | Small teams adding automation to a number they already run by hand | High-volume senders who work entirely from a desktop inbox |
For most small and medium businesses the honest recommendation is coexistence first. It is reversible — you can disconnect from the app's settings — so it costs you very little to try, and migration remains available later if you outgrow it.
Connecting a coexistence number to RevoplyAI
RevoplyAI is a verified Meta Tech Provider, so the coexistence flow above runs directly from your dashboard's Channels page. Once the number is connected, your AI assistant answers from the same knowledge base that powers your other channels, and every message — the assistant's replies and the ones your team taps out on their phones — appears in one shared inbox. When a conversation needs a person, the assistant hands it over instead of guessing, and your colleague can take it either from the dashboard or straight from the WhatsApp Business app, whichever is closer to hand. Nothing about your customers' experience changes: same number, same chat thread, faster answers.
Frequently Asked Questions
Can I really use the WhatsApp Business app and the API on the same number?
Yes. That is exactly what coexistence is for. Both run on one number at the same time, with messages syncing in both directions, so your team can answer from their phones while an AI assistant handles the rest through the API.
Will I lose my chat history?
Not if you accept the sync prompt during setup. Contacts and up to about six months of one-to-one conversations come across; group chats stay in the app. The catch is timing — history can only be synced during onboarding, so skipping the prompt means disconnecting and starting over to get it.
What happens if I uninstall the WhatsApp Business app?
The connection breaks. Coexistence depends on the app staying installed on the phone that owns the number, and providers also report an inactivity window, so open it at least once every couple of weeks. If you genuinely don't want the app anymore, a full migration is the right choice instead.
Can I undo it?
Yes. You can disconnect from the WhatsApp Business app's own settings, under the account's Business Platform section. That reversibility is a large part of why coexistence is a low-risk first step.