WhatsApp Coexistence Limitations: What Stops Working

What stops working when you turn on WhatsApp coexistence?

Coexistence runs one phone number on the WhatsApp Business app and Meta's Cloud API at the same time. The trade is real, and Meta documents most of it — scattered across five sections of a single page, in a table almost nobody reproduces.

Here is the whole list in one place. The last column matters most: it separates what Meta documents from what partners repeat to each other.

Checked on 22 August 2026 against Meta's developer documentation for onboarding WhatsApp Business app users, plus Meta's Cloud API overview for the 80 mps comparison, its Calling documentation, and the Marketing Messages Lite API changelog. If you are still deciding whether the trade is worth making, the full picture is in our guide to keeping your number on your phone.

• What stops working when you turn on WhatsApp coexistence?
• Why do broadcast lists stop working?
• Is coexistence capped at 5 or 20 messages per second?
• Can WhatsApp coexistence disconnect itself?
• Why does my coexistence inbox start empty?
• What happens to labels, catalogue and away messages?
• What happens to WhatsApp Web and my linked devices?
• Can a coexistence number get the verified badge?
• What still works after coexistence is on?
• How do you turn off WhatsApp coexistence?

Why do broadcast lists stop working?

This is the change most likely to catch an owner-operated business out, because broadcast lists are usually what they were using the Business app for. Meta's wording is unambiguous: broadcast lists "will be disabled", the business "will not be able to create new Broadcast lists", and "existing Broadcast lists will become read-only". They are not degraded or rate-limited. They stop.

What replaces them is not a like-for-like swap, and any page implying otherwise is glossing. A broadcast list on the phone was free, instant, capped, and reached only people who had already saved your number. An API broadcast is not limited to people who saved your number, but every message outside an open 24-hour window must be a template Meta approved in advance, and Meta charges for each one.

There is a second difference that matters more than the price. How many people you may reach in a day is set by your messaging limit, not by the size of your list — so the list stops being the thing that decides your reach.

That is usually an upgrade. It is never a smaller job. New numbers also start on a low messaging tier and earn their way up, so the first campaign after switching will not reach everyone at once — the mechanics are in our post on what actually caps how many people you can reach.

Is coexistence capped at 5 or 20 messages per second?

Twenty. This is the single most contradicted number in the whole topic, and it is worth being precise about because the two figures are four times apart.

Meta's current wording: "To remain compatible with the WhatsApp Business app, business phone numbers that are in use with both the WhatsApp Business app and Cloud API have a fixed throughput of 20 mps." Checked 22 August 2026.

Plenty of vendor pages still print 5 mps. Read them closely and you can see why: they reproduce Meta's sentence almost word for word — "in order to remain compatible with the WhatsApp Business app…" — around a figure Meta has since raised. That is a copied sentence with a stale number in it, not a second source.

The figure only means something next to the alternative. Meta's Cloud API overview states that business phone numbers "can send up to 80 messages per second by default, with capacity upgrades available". Coexistence runs at a quarter of that, with the upgrade path closed while it is on.

Throughput is also not your messaging limit, and the two get conflated constantly. Throughput is speed. Your messaging limit is how many unique customers you may start a conversation with in a moving 24 hours. Coexistence fixes the first and leaves the second alone — and at 20 mps a 10,000-recipient campaign takes about eight minutes, so for most senders the tier binds long before the cap does.

Can WhatsApp coexistence disconnect itself?

Yes — and this is the limitation that almost no page publishes, even though Meta documents it plainly.

The connection is not permanent. Meta's account_update webhook carries a PARTNER_REMOVED event with a disconnection reason, and six of its values are worth reading as a list of ways coexistence ends without anyone deciding to end it:

Quoted from Meta's developer documentation, checked 22 August 2026.

The practical reading is short. The phone stays load-bearing. If the handset holding the number goes unused for a fortnight — a shop closed for a holiday, a phone left in a drawer once the owner started answering from the browser — coexistence drops and the shared inbox stops receiving.

360dialog's documentation recommends opening the app "at least once every 13 days" — a one-day safety margin on Meta's "approximately 14". Meta states no such rule, so treat it as a partner's precaution rather than a documented limit. The cost of following it is nothing.

Two of the others catch people out differently. Getting a new phone and re-registering, or putting ordinary WhatsApp back on that number, each end the connection — and neither feels like a platform decision when you make it.

Why does my coexistence inbox start empty?

Because history synchronisation is something the platform has to opt into, and many do not.

Meta's documentation says "all chat messages in the most recent 6 months can be synchronized", delivered as a burst of history webhooks covering "all messages sent or received within 180 days of the time when the business was onboarded onto Cloud API". Group chats are excluded outright. Media is worse: those payloads carry no media asset IDs, and the follow-up webhooks that do carry them cover "only … media messages sent within 14 days of onboarding".

Two constraints make it one-shot. The partner has 24 hours from onboarding to pull the history "otherwise they must be offboarded and they must complete the flow again", and contact synchronisation runs only once.

WabaCRM does not subscribe to the history field at all, so a coexistence inbox here starts empty and past chats stay on the handset. That is deliberate, and worth stating rather than hiding.

A 180-day backfill for a busy number is megabytes in one burst, and webhook subscriptions are set per app rather than per customer. If those payloads exceed a web server or database ceiling, Meta retries, then disables the subscription for that account — which stops ordinary inbound messages too. Losing today's customer messages to import last year's is a bad trade.

What happens to labels, catalogue and away messages?

They keep working — on the phone. They do not cross over. Meta's feature comparison lists "Business tools (for example, catalog, orders, status)" and "Messaging tools (for example, marketing messages, greeting message, away message, quick replies, labels)" with the same two entries against each: No change in the app, and Not supported on Cloud API.

Both halves matter. Nothing you configured is deleted: your catalogue stays live, your labels stay on their chats, your away message keeps firing for anyone who messages the app directly.

But none of it is visible on the API side, so none of it reaches the shared inbox your team answers from, and none of it can be reported on, automated against or used to segment a campaign. Most teams rebuild the equivalents on the platform and let the phone's copies go stale.

What happens to WhatsApp Web and my linked devices?

Everything is unlinked once, and two clients never come back. Meta documents that a business can link up to four companion clients, that "All companion clients are supported, except for WhatsApp for Windows and WhatsApp for WearOS", and that on onboarding "all companion apps will be unlinked from the account, and the business can then re-link any supported companion apps".

There is a quieter consequence underneath. If a message arrives at an unsupported companion client, "the message will not trigger messages webhooks", so it never reaches the API and never appears in the shared inbox. Anyone on your team who lives in the Windows desktop app should know that before you switch.

Can a coexistence number get the verified badge?

Meta does not document this, and the partner pages contradict each other. That is the honest answer, and it is more useful than a confident one.

Meta's coexistence page does not mention business verification, the Official Business Account, the verified badge or display name anywhere. Two partner help centres fill that silence, agreeing on one point and contradicting each other on the next.

Where they agree: the badge does not come with you. 360dialog's documentation states that the Official Business Account blue badge "is not supported for coexistence accounts", and that "the blue badge verification does not transfer between the WhatsApp Business app and WhatsApp Business Platform".

Where they disagree is Meta Verified — Meta's separate paid subscription, and not the same thing as the Official Business Account badge. 360dialog treats it as the way forward: display name "is not automatically reviewed" for coexistence numbers, and "the business must first apply for Meta Verified" to start that review.

Wati's help centre says the opposite — that "your paid Business Verification status in the WhatsApp mobile app may be removed", and that "you can have either the CoEx integration or paid Business Verification active, but not both at the same time". Both checked 22 August 2026.

One is recommending the thing the other says will end your integration, neither cites Meta, and neither carries a hard date. So treat it as unresolved: if a badge matters, get your provider to confirm in writing before you connect, and read our explainer on what the verified badge actually gets you first.

One related warning is worth following even though only 360dialog states it: profile picture updates are "not supported after onboarding". Set your picture and business details correctly in the app before you start the flow.

What still works after coexistence is on?

Worth stating plainly, because the list above reads heavier than the change feels day to day.

Your number is unchanged. Existing chats stay on the phone and stay readable there, and your contacts stay in the handset. You keep answering from the app as before, and what you send from it is mirrored into the shared inbox. Customers notice nothing — no migration notice, no number change, no interruption.

The number must already be on the WhatsApp Business app, not the consumer app, at version 2.24.17 or higher. A number active on consumer WhatsApp cannot use coexistence at all. If you are unsure which side of that line you are on, our comparison of the Business app and the API sorts out which product you are running.

One requirement is about your provider rather than about you. Meta states that the partner "must already be a Solution Partner or Tech Provider". Beyond that documented bar, our own experience is that the journey also needs Advanced Access to Meta's WhatsApp permissions — a provider still on Standard Access has a working ordinary signup and a coexistence flow that fails only after the customer has typed their number.

Meta does not document that asymmetry, so ask directly whether a provider has run a coexistence connection through to completion. WabaCRM has held Advanced Access since 13 August 2026 and connects numbers this way in production.

How do you turn off WhatsApp coexistence?

From the phone, not from the API — and not casually.

Meta states you "cannot use the Deregister API to deregister a business phone number from Cloud API if it is already in use with both Cloud API and the WhatsApp Business app". Instead the business opens the WhatsApp Business app and navigates to Settings → Account → Business Platform → Disconnect Account.

Because contact and history synchronisation each run once per onboarding, disconnecting and reconnecting is not a free reset. Anything that was going to be imported was imported the first time.