WhatsApp Coexistence is Meta's official feature that lets a business run the WhatsApp Business App and the WhatsApp Cloud API on the same phone number at the same time, keeping chat history in sync between the two. That means a business can add automation, chatbots, and CRM integrations through the API while the same team keeps answering messages manually in the app they already know — no porting the number, no losing conversation history, no forcing every message through a bot.
We get a version of the same objection almost every time we pitch WhatsApp automation to a business that's never done it: "we don't want to lose our number, our chat history, or our team's ability to just reply normally." Coexistence is Meta's direct answer to that objection, and most businesses evaluating WhatsApp lead automation for the first time have never heard of it. This guide covers exactly what it does, what it breaks, and — just as important — when it's the wrong tool and a full custom build is the better call.
What Coexistence Actually Changes
Before Coexistence existed, moving a WhatsApp number onto the Cloud API meant an all-or-nothing switch: the number left the consumer Business App entirely, and every message from then on had to go through whatever system you connected to the API. Coexistence removes that trade-off. According to Meta's own developer documentation, a business customer onboarded through Embedded Signup keeps using the WhatsApp Business App for one-to-one conversations exactly as before, while the same number simultaneously accepts and sends messages through the Cloud API — the two stay synchronized, not separated.
In practice, this is what unlocks WhatsApp automation for businesses that were previously stuck: a sales team can keep manually replying to warm leads in the app they're used to, while an automated flow handles lead follow-up, order updates, or FAQ responses through the API on the exact same number, without customers ever seeing two different numbers or losing the thread of a conversation that started before automation existed.
A concrete version of this: a boutique clinic keeps its front-desk staff replying to booking questions and rescheduling requests directly in the Business App, exactly as they've done for years, while an automated flow quietly sends appointment reminders and post-visit follow-ups through the API in the background. Patients never notice a switch — they're still messaging the same number they've always messaged — but the clinic stops losing revenue to no-shows without hiring anyone new.
Business App vs. Coexistence vs. Full Cloud API
The right setup depends entirely on how much of the conversation you want automated versus handled by a person. Here's how the three options actually compare:
| Business App only | Coexistence | Full Cloud API (no app) | |
|---|---|---|---|
| Who replies | Humans only, manually | Humans in the app + automation via API, same number | Automation-first; humans reply through a connected inbox/CRM, not the app |
| Chat history | Lives in the app | Synced both ways for the first 180 days after onboarding | Lives in your connected system only |
| Message throughput | Normal consumer-app limits | Fixed at 20 messages/second combined | Scales with your verified messaging tier |
| Broadcast lists | Fully supported | No new broadcast lists can be created | Replaced by API-based bulk sending |
| Best for | Solo owners with low volume, no automation need yet | Teams that want automation live without disrupting how staff already work | Businesses fully committed to an automation-first, high-volume operation |
Coexistence is deliberately the middle option — a way to test and roll out automation gradually rather than forcing a hard cutover on day one. That makes it the right starting point for most businesses new to WhatsApp automation tools, even if they eventually outgrow it once automation handles most of the volume.
Requirements and What Breaks
Coexistence isn't a toggle you flip yourself — Meta requires the technical onboarding to run through a Solution Partner or Tech Provider (in practice, a BSP platform or an automation agency), and the business's own app has to meet a minimum version. Per Meta's documentation, the requirements and side effects are specific:
- App version 2.24.17 or higher on the WhatsApp Business App before onboarding.
- Meta Business Manager account and Business Verification completed first.
- 20 messages per second, combined — this is a fixed throughput cap across app and API traffic together, not a per-channel limit.
- Disappearing messages, view-once media, and live location sharing turn off for every one-to-one chat on that number once Coexistence is active.
- No new broadcast lists can be created through the app after onboarding.
- Group chats aren't part of the deal — they stay in the app only and never sync to the API side.
- A 24-hour sync window. After onboarding, the business has 24 hours to complete history synchronization, covering messages from the prior 180 days — miss that window and the business has to be offboarded and re-onboarded from scratch.
None of these are dealbreakers for most small businesses, since few SMEs rely heavily on disappearing messages or view-once media on a business number. The broadcast-list restriction is the one worth planning around if bulk announcements are part of your current workflow — that volume needs to move to API-based sending instead.
What It Costs
Coexistence itself doesn't carry a separate Meta fee — you're charged the same way you would be for any Cloud API connection: nothing extra for messages still sent through the free Business App, and standard WhatsApp Cloud API messaging rates for anything sent through the API side. What you'll actually pay for is the BSP or agency doing the onboarding and the automation you build on top — a monthly BSP platform fee if you go that route, or a fixed project cost if you have a custom agent built to sit behind the API connection.
When Coexistence Is the Right Call — and When It Isn't
Coexistence earns its place when a business wants to prove automation works before fully committing to it, or when the team genuinely needs to keep manually replying to some conversations while others get automated. It's the wrong choice when a business is already running high message volume that needs the full 100,000-conversations-per-day tier our WhatsApp Business API setup guide covers, since the 20 messages/second combined cap becomes a real bottleneck at that scale — at that point, a full Cloud API setup without the app is the more sensible path.
It's also worth being clear-eyed that Coexistence solves an onboarding and continuity problem, not an automation problem. Turning it on doesn't create a chatbot, qualify a single lead, or answer a single question on its own — it just opens the door for API-based automation to run on your existing number. What you build behind that door — a scripted auto-responder or a real AI agent that reads order data and updates your CRM — is the decision that actually determines whether the automation is worth having. Run the numbers on your own message volume in our automation ROI calculator before choosing which path to build.
Key Takeaways
- Coexistence lets you keep your existing WhatsApp number, chat history, and human team in the app while adding API-powered automation on top — no forced cutover.
- It requires app version 2.24.17+, Business Verification, and onboarding through a Solution Partner or Tech Provider — most businesses go through a BSP or agency, not directly with Meta.
- Trade-offs are real but narrow: 20 messages/second combined throughput, no new broadcast lists, disappearing messages and view-once media disabled, groups don't sync.
- It's the right starting point for businesses easing into automation, and the wrong fit once volume needs the full messaging-tier scale a pure Cloud API setup supports.