WhatsApp Coexistence: Keep Your Number's History While Adding Real Automation

For a long time, connecting a WhatsApp number to the Cloud API meant giving up the WhatsApp Business app on that number entirely. The number became API-only, and any message history or human-managed conversations were simply gone the moment migration completed. For a small business with years of real relationships and history on that number, that wasn't a minor inconvenience, it was a real enough cost that a lot of businesses avoided the API entirely.

What Coexistence actually solves

Coexistence lets a business keep using the WhatsApp Business app on their phone, for a real person to read and reply by hand exactly as they always have, while also connecting that same number to the Cloud API through a tech provider, so automation can run alongside it. Both the app and the API see the same conversation thread, and message history carries over instead of resetting to zero. A customer who's been messaging that number for two years doesn't experience any disruption.

Real requirements that gate whether it's even available

The Business app needs to be on a sufficiently recent version; Meta has published specific minimum version numbers, so an old, un-updated install can block the whole setup before it starts. On the provider side, whoever handles onboarding needs to already be an established Meta Solution Partner or Tech Provider with a webhook callback proven to reliably accept and correctly process incoming events.

Eligibility isn't automatic just because the technical boxes are checked. Meta evaluates the account's tenure and existing messaging quality before allowing onboarding. This is built for a specific case: helping small and medium businesses that haven't previously been on the API make that jump without losing what they already have.

A one-directional door, with a real throughput ceiling

Coexistence only works for numbers currently registered in the WhatsApp Business app. If a number is already fully migrated to the API, Coexistence won't work for it, there's no app-based conversation left to preserve. And a number using both the app and the API at once has a fixed combined throughput ceiling, a cap on messages per second across both the human-managed and automated sides. For a small business sending occasional automated messages alongside normal human conversation, this rarely matters. For genuinely high volume on a still-actively-used number, check that ceiling against your expected traffic before building a workflow that assumes unlimited headroom.

What onboarding actually feels like

From the business owner's side, it typically starts as a prompt inside the WhatsApp Business app itself, offering to link the account through whichever tech provider is guiding the setup, without needing to touch the developer platform directly. The complexity sits entirely on the tech provider's side, which is the whole point.

Why this matters if you already have a number your customers know

This matters most for exactly the kind of business LeadOro builds for: one with a real, active number customers already know and have saved, where losing that continuity purely to gain automation would cost more in trust than the automation itself would ever be worth. LeadOro handles the Coexistence onboarding directly, so you keep the number and the history while gaining automation on top of it, rather than choosing between the two.