What WhatsApp Coexistence is: the same number in the app and the API

For years, using WhatsApp for business meant picking a side. Either the WhatsApp Business app, with your team replying by hand, or the Cloud API, with automation and integrations — and the number living only there, with no app.

Coexistence ends the choice. The same number now exists in both places at once: the team keeps replying in the app they already know, and the API can read conversations and send messages on that same number.

What changes and what stays

The last line is the one that matters. The classic objection to the Cloud API was never technical — it was that the team would lose the tool they already know. Coexistence removes exactly that objection.

What the API can now do

With the number connected, three things become possible without taking anything away from anyone:

Read what happens. Messages arriving and leaving through the app become visible to the systems you authorize. That is what lets you measure, log to the CRM and know where each conversation came from.

Send automatically. Confirmations, reminders, status updates — triggered by a system, from the same number the customer already knows.

Connect it to everything else. What arrives on WhatsApp can become a deal in the CRM, with its origin attached. It is the path that solves knowing which ad produced which conversation.

The 24-hour sync

The part of the process that catches most people off guard: after connecting, there is a sync window in which the app's recent history is transferred to the platform.

During that period the system is building its initial state. It is not instant, and abandoning the process halfway leaves the number connected on Meta's side with nothing on yours — the worst of both worlds.

The practical rule: connect and let it finish. Start the process at a moment when nobody will touch the configuration for the next few hours.

Who should use it

It makes sense if:

• your team already answers through WhatsApp Business and it works
• the number is already on ads, the website and printed material
• you want to automate one part — confirmations, reports, alerts — without changing how people are served
• you need to know which campaign produced which conversation

It does not make sense if:

• you do not use WhatsApp for support yet; start with the app
• you already run API-only and want no app at all; migration is simpler
• your volume is tens of messages a month; the complexity will not pay for itself

What coexistence is not

Three common confusions worth clearing up before deciding:

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

It is not a bot replacing the team. Human support stays in the app. Automation covers what repeats, not what is a conversation.

It is not freedom to send anything. Platform rules still apply: a business-initiated message outside the service window needs an approved template, and sending what people did not ask for drags your number's quality down.

Where to start

1. Confirm the number is on WhatsApp Business, the business app — not regular WhatsApp.
2. Set aside the moment. The connection has a sync step that needs to complete.
3. Decide what to automate first. Start with one thing, repetitive and low risk: appointment confirmations, receipt acknowledgements, internal reports.
4. Leave human support where it is. The temptation to automate the whole conversation in month one is the most common mistake.

To understand what coexistence requires before you begin, see coexistence requirements. For the comparison against taking the number out of the app for good, see coexistence or migration.