WhatsApp Coexistence limitations: what breaks and when to skip it

WhatsApp Coexistence has a short list of limitations, and every one of them is concrete. While your number is linked to the Cloud API, broadcast lists lock in the app; disappearing messages, view once and live location stop working; groups stay on the phone but outside the API; the number is capped at 20 messages per second; and someone has to keep opening the app. None of this is hidden. What varies from business to business is which one actually hurts.

Below is each limitation, who should treat it as a dealbreaker, and how to check before you connect. At the end there is a straight answer on when coexistence is the wrong call.

The short list: what locks while the API is connected

Coexistence keeps one number in the WhatsApp Business app and in the Cloud API at the same time. For both sides to live together, Meta switches off a few app features that have no API counterpart. Today the list looks like this:

Read the right-hand column slowly. For most businesses that sell or support over WhatsApp, none of these rows is a dealbreaker. For a few, a single row flips the decision.

Each limitation in plain terms

Broadcast lists

This is the one longtime app users bring up first. A broadcast list is how a lot of small businesses run promotions: build a list on the phone, send one message to everyone, done.

With the API connected, that feature locks in the app. Sending to many contacts moves to the API, which means a Meta-approved template and per-message billing. That is not just a tool swap, it is a rule swap. If the weekly broadcast is how you sell, figure out the cost and the template approval before you connect. The numbers side is covered in WhatsApp Coexistence pricing.

One warning. The workaround of "fine, we will send them one by one from the phone" is exactly the pattern Meta penalizes. Manual mass sending from the app drags down the number's quality and can get it restricted. Read WhatsApp number quality before you try it.

Disappearing messages, view once and live location

Three chat features go dark while the API is linked. Most retail and service businesses will never notice.

Some will. Say you run a plumbing and HVAC company in Phoenix and your techs share live location so customers know when they will arrive. That flow is gone on the connected number. Or a practice that sends lab results as view once because of an internal policy needs another way to do it.

Groups

Groups keep working on the phone. The difference is that they sit outside the API: nothing that happens in a group is read by connected systems, and nothing is sent to a group through the API.

If your service lives in groups, say one group per client at an agency or one per project at a contractor, coexistence will not see those conversations. Only one-to-one chats count for measurement and automation.

The 20 messages per second ceiling

Each number is capped at 20 messages per second. For support, appointment confirmations and order updates, that is plenty. If your plan is to hit a large list in the same minute, it is a real bottleneck and belongs in the plan.

The 14-day rule

Coexistence assumes the app stays alive. If nobody opens WhatsApp Business on the phone for about 14 days, Meta may drop the API connection.

This catches one profile in particular: the business that connects the number, moves everything to software, and leaves the phone in a drawer. If the goal is to retire the app, coexistence is the wrong model. See coexistence or migration.

The rules that are not on the list but still bite

Beyond what Meta locks, three rules of the model catch people off guard.

One number, one API. The number has to be in the WhatsApp Business app today, the green business app, and not linked to any other API. If another platform already holds it through the official API, it must be released first. A number on personal WhatsApp does not qualify.

History syncs once. At connection, Meta syncs up to six months of history, a process that takes anywhere from minutes to hours. Anything older stays out, and the sync does not run again. Details in the 24-hour sync.

API rules apply to whatever leaves through the API. Outside the 24-hour window, a business-initiated message sent through the API needs an approved template. Only a customer message opens or resets that window. What your team sends from the phone is free and does not touch it. More in the 24-hour window with coexistence.

How to test before you connect

You do not need to connect anything to find out whether a limitation is a dealbreaker. A 30-minute conversation with whoever answers the phone settles it. Run through this:

• Does anyone on the team use broadcast lists every week? For what?
• Does any workflow rely on live location, view once or disappearing messages?
• Are any clients served inside groups, and does that need to be measured?
• Is there a plan to message a large list in the same minute?
• Will someone keep opening the app on that phone every week?
• Is the number in WhatsApp Business, not tied to another API?
• Does the team know that mass sending from the phone hurts number quality?

If every answer is calm, the limitations will not get in your way. If one lights up, deal with that one before anything else. The right question is "what do we do instead", not "we will figure it out later".

A practical test for the 14-day rule: name the person who owns that phone today and put "open the app" in their routine. If nobody wants to own it, you already have your answer.

When to skip coexistence

Coexistence is built for one situation: a team that already works in the app, wants to keep working there, and needs software to read and send on the same number. Outside that, there are better options.

Skip it if broadcast lists are your sales channel and you do not want per-message billing or template approvals. Stay on the app until that math works.

Skip it if the app will sit idle. If the plan is to run everything through software, a full migration to the API is simpler and has no 14-day rule.

Skip it if your service happens in groups and that is what you want to measure. The API will not see it.

Skip it if volume is low and there is nothing to automate or measure. A few dozen messages a month, with no ads driving people to WhatsApp, does not justify the setup.

Skip it if the real goal is to dodge template costs by hand. Sending promos one by one from the phone is not a workaround; Meta penalizes that pattern with or without coexistence.

What to do next

Walk through the checklist with whoever answers the phone. If nothing lights up, the limitations are not your problem, and the next step is the WhatsApp Coexistence requirements. If something does, solve that first. To see how the module works in Vazante, go to the WhatsApp Coexistence page. For the full picture of the model, start with what WhatsApp Coexistence is.