WhatsApp CoEx: what the acronym means and what it changes

CoEx is shorthand for WhatsApp Coexistence: a setup where the same phone number runs in the WhatsApp Business app on your phone and in the WhatsApp Cloud API at the same time. Your team keeps answering from the app, and a system you authorize can read and send messages on that same number. If you saw "WhatsApp CoEx" in a BSP's docs, a vendor's pricing page or a forum thread, that is what they mean. It is not a new app or a separate WhatsApp product. It is a way to connect the number you already have without pulling it off the phone.

Why everyone calls it CoEx

People who build on WhatsApp shorten everything. The Cloud API becomes "the API." Embedded Signup becomes "the signup." And coexistence becomes CoEx. The acronym stuck because it shows up exactly where buying decisions happen: in vendor offers, onboarding calls and the question every integrator asks first, "are we bringing this number in through CoEx or a full migration?"

The catch is that the acronym arrives without context. Plenty of business owners see "CoEx included" on a proposal and assume it is a chatbot, a plan tier or some new inbox. It is none of those. These labels all point to the same thing:

If a vendor uses a different term and you are not sure, ask one question: "Will my team keep replying from the WhatsApp Business app, on the same number?" If the answer is yes, it is coexistence. If the answer is no, you are looking at a migration.

What CoEx actually is, in four parts

The whole feature fits in four sentences. Each one hides a detail that tends to surprise people later.

Same number. No new number, no port. The number already printed on your truck, your Google Business Profile and your ads stays the channel.

Two sides at once. The number lives in the Business app and in the Cloud API. Conversations show up on both sides: what your team sends from the phone is visible to the system, and what the system sends shows up in the app.

Connected through Embedded Signup. The connection runs inside Meta's own flow. The owner of the number authorizes it there and scans a QR code in the app. The vendor never gets a password and never needs to hold the phone.

One initial sync. When you connect, Meta syncs up to six months of history. It takes anywhere from minutes to hours and happens only once. Everything after that comes in live.

The full walkthrough is in how to enable WhatsApp Coexistence. For the broader overview, start at what WhatsApp Coexistence is.

What CoEx is not

The acronym causes more confusion than the feature itself. Four things CoEx is not:

It is not a second number. It is the same number, in two places.

It is not a migration. Migrating takes the number out of the app so it lives only in the API. With CoEx, the app stays. The trade-offs are laid out in coexistence or migration.

It is not a chatbot. CoEx is the connection. What you do with it, a bot, a report, an appointment reminder, depends on the tool on the other end. A lot of buyers expect automated support to come bundled with "CoEx" and are disappointed when it does not.

It is not a license to blast. Meta's rules still apply. A business-initiated message sent through the API outside the 24-hour window needs an approved template. And swapping API broadcasts for mass manual sends from the phone is exactly the pattern Meta penalizes: quality ratings drop and blocks still count.

What gets locked while CoEx is on

This is the part most sales decks leave in the fine print. With the API connected, some app features stop being available:

• broadcast lists in the app
• disappearing messages, view once and live location
• groups stay on the phone but are outside the API
• the number gets a cap of 20 messages per second

One more thing to watch. Someone has to open the app now and then. If nobody opens WhatsApp Business for roughly 14 days, Meta can drop the connection. That happens more than you would think on numbers that exist mainly to catch ad leads and that the team only checks occasionally.

If your business runs on broadcast lists for promos or restock alerts, think twice before switching CoEx on. What keeps working on the phone is covered in does the app keep working with coexistence.

What CoEx costs, in broad strokes

There are two separate bills, and mixing them up is the most common budgeting mistake.

Meta's bill. Meta charges per message sent through the API, based on a public rate card that varies by country and by template category: marketing, utility or authentication. Service replies inside the 24-hour window are currently not charged. Rates change, so always check Meta's current rate card before you run numbers.

Your provider's bill. This is what the tool that connects your number charges. Every vendor prices differently: per number, per conversation, or per message with a markup on top.

Here is the part many people miss: messages sent from the phone app are free. They are not billed by the API, and they do not open, extend or affect the 24-hour window. Only what goes out through the API is billed.

Say your front desk handles 300 chats a month from the phone, and the system sends an appointment reminder through the API to everyone who books. Only those reminders hit Meta's bill. The 300 replies from the phone cost nothing extra.

Who should turn CoEx on

Run through this list. It takes five minutes:

• your team already answers on the WhatsApp Business app and it works
• the number is already on your ads, website or signage
• you want to automate one piece, like reminders or reports, without changing how people are served
• you want to know which ad started each conversation
• you can live without broadcast lists in the app

Checked four or five? CoEx is probably your path. Checked one or two? The app alone might be enough, or a pure API setup with no app might fit better. Before deciding, read the coexistence requirements and the most common coexistence mistakes.

Series map: where each piece lives

CoEx has several moving parts, and each one has its own article. Use this as an index:

What to do next

If the acronym brought you here, you now know what is on the table: your number in the app and the API at the same time, a few app features locked, and two separate bills to plan for. Next, check that your number meets the requirements and see how the module works on the WhatsApp Coexistence page. Per-number pricing is on the pricing page.