WhatsApp Coexistence, Explained

For years the most common reason a small business refused to connect its number to the WhatsApp API had nothing to do with technology. It was that the number was on their shopfront, their van, their wedding brochure - and connecting it meant deleting the WhatsApp Business app account on it. The owner would lose the inbox they actually used, along with every conversation in it.

That was a genuinely bad trade, and most people correctly refused it. Coexistence, which Meta shipped in May 2025, is the fix.

What it actually does

Coexistence lets a single number be live on the WhatsApp Business app and the Cloud API simultaneously. Your colleague replies by hand from their phone; your software sends templates and handles automation through the API; both see the same conversations.

Chat history is preserved rather than discarded, which is the part that makes it adoptable. Nobody has to explain to a customer why the business has forgotten a conversation from last week.

In practice this collapses a decision that used to be genuinely painful. The old question was “do we automate, or do we keep the human inbox?” That question no longer has to be answered.

The conditions

Coexistence is a real feature with real edges, and it is better to learn them now than during onboarding.

The 13-day rule deserves more attention than it usually gets. It is a small requirement that fails in a very annoying way: everything works for weeks, someone leaves or changes phones, nobody opens the app, and the number quietly goes inactive. If you are deploying Coexistence across many customers, that is a support ticket generator. Put a reminder somewhere a human will see it.

Two surfaces, two billing behaviours

A subtlety worth internalising: what a message costs depends on which surface sent it.

Messages your team types by hand in the WhatsApp Business app are free, exactly as they have always been. Messages sent through the API are billed at standard Cloud API per-message rates. The same conversation thread can therefore contain both free and billed messages.

This matters more from 1 October 2026, when in-window replies through the API stop being free. From that date, the cheapest way to answer a customer inside the 24-hour window is literally for a human to reply from the app. Whether that is a sensible way to run a business is a separate question, but the economics are worth knowing - see the pricing guide.

A wiring detail that will save you a bad afternoon

If you are integrating Coexistence yourself rather than through a provider, one hard-won note about webhook subscriptions.

Coexistence introduces additional webhook fields - things like history sync and app state - and it is tempting to enable everything by posting a fresh subscription for the business account. Do not. Subscribe field by field, toggling only the specific ones you need.

A wholesale re-subscribe can reset the fields already active on that account, and because webhooks fail silently, the symptom is not an error. It is inbound messages simply not arriving anymore, discovered whenever someone notices the replies stopped. We cover the general shape of this failure mode in how WhatsApp webhooks actually work.

When Coexistence is the wrong answer

It is not automatically the better option, and it is worth being clear about when to skip it.

Skip it if the number will be driven almost entirely by software. The 13-day requirement is pure operational overhead if nobody meaningfully uses the app, and standard Cloud API onboarding is simpler with fewer moving parts.

Skip it if you need several numbers under one identity, since the one-number-per-app-account limit will constrain you.

Reach for it when the number has a human relationship attached - a business whose customers already message that number, a team that answers by phone, an owner who wants to keep replying personally while automation handles the volume. That is exactly the case it was built for, and it is a common one.

Why this changes the onboarding conversation

The strongest argument for connecting your own number was always brand continuity: messages should come from the number your customers already know, not an unfamiliar one. The strongest argument against was that you had to give up the app to do it.

Coexistence removes the second argument without weakening the first, which makes bringing your own number the default choice for far more businesses than before. We wrote up that decision in full, including when a shared sending number is still the better option, in the guide to using your own number.