WhatsApp Coexistence explained: use the Business app and API on the same number

WhatsApp Coexistence lets an eligible business use its existing WhatsApp Business app number with Cloud API at the same time. Your staff can continue supported conversations in the app while connected software adds team workflows, integrations and automation around the same number.

The attraction is continuity. Customers keep contacting the number they know, and staff can retain familiar app access. But Coexistence has specific compatibility limits, so the decision should start with how your business currently uses WhatsApp.

Zena's approach is: Every Zena feature on every plan. Pick the capacity you need. That describes shipped software features. Meta's rules for the connection still determine which WhatsApp capabilities your number can use.

What Coexistence is technically

Coexistence is an official onboarding option documented by Meta as onboarding WhatsApp Business app users. An eligible provider configures Embedded Signup so a business can connect its existing app account and phone number to Cloud API.

It is not two independent WhatsApp accounts sharing a number. The onboarding flow connects the existing business presence to API access. Your provider uses the authorised account details and webhook subscriptions to operate the integration.

For supported conversations, messages are mirrored between the Business app and the connected software. A webhook called smb_message_echoes reports new messages the business sends through the app or supported companion devices. The provider must process those events and display them in the relevant conversation.

Incoming customer messages and message-status events use the relevant messaging webhooks. Separate history and smb_app_state_sync events support permitted history and contact synchronisation. The echo webhook alone is not the entire integration.

That distinction matters when evaluating software. Connecting a number is only the beginning; the inbox must correctly display messages, recognise who replied and avoid duplicated actions.

Why this option exists

The problem Coexistence addresses is straightforward: a business can need software-driven workflows before it is ready to stop using the phone app.

An owner might still handle important conversations personally while staff need shared visibility. A service team might want requests recorded in a CRM while keeping app access during visits. Coexistence provides a supported route between those ways of working.

It also lets a business introduce automation gradually. You can decide which enquiries should enter a structured process and which should remain personal conversations, provided the software coordinates the handover.

The operating model still needs an owner. If app users and automated rules both reply independently, the customer can receive conflicting answers. Agree when automation pauses, who takes over, and how other staff recognise that someone is handling the request.

What it enables

The useful combination is familiar app access plus a software layer. Depending on the provider, that layer can offer a team inbox, assignments, customer records and connections to business systems.

A request can arrive through WhatsApp, be assigned to the relevant person, and carry the conversation context into an authorised workflow. Staff who continue using the app can contribute to supported conversations without moving the customer to a new number.

Historical context can also be shared during onboarding if the business permits it. Meta documents synchronisation of supported individual chat messages from the most recent six months, with synchronisation initiated and completed within its documented 24-hour onboarding window. This is a bounded process, not a promise that an entire lifetime archive will appear in every provider's inbox.

Ask the provider what it imports, how completion is confirmed, and how it handles unsupported content. Consent to share history should be a deliberate business decision.

What Coexistence cannot do

Meta's feature comparison is essential reading before connecting an established number.

The group limitation is specific to this connection. It should not be turned into a blanket statement that Meta has no group API capabilities elsewhere.

Linked devices need attention too. Meta says companion apps are unlinked during onboarding and supported devices can then be linked again. Its current documentation excludes Windows and WearOS companion clients from the supported set. Audit the devices your staff use before scheduling onboarding.

The separate Calling API requires a Cloud API number that is not in use with the Business app. Keeping app calling is not the same as enabling API calling.

The fixed throughput limit

Meta documents a fixed throughput of 20 messages per second for numbers used with both the Business app and Cloud API. This compatibility limit differs from the higher throughput available to eligible Cloud API numbers without app coexistence.

It is a processing limit, not an allowance of new people you may contact. Meta's messaging limits, quality controls and marketing restrictions still apply. Inbound and outbound traffic must be considered when planning throughput.

A higher software subscription does not remove Meta's fixed Coexistence limit. If concentrated campaign traffic is central to your business, ask the provider to assess the workload against the connection's limits before choosing it.

Eligibility and onboarding checks

The current Meta guide requires the WhatsApp Business app at version 2.24.17 or higher. It also requires the integrating provider to be a Solution Partner or Tech Provider, implement the supported Embedded Signup flow, and process the required webhooks.

The business must be able to authorise the account connection. Confirm who controls the business assets and phone app, and resolve access problems before beginning. If a previous partner or credit line remains associated with the account, have the provider check whether it affects onboarding.

Embedded Signup also changes over time. Meta's Coexistence guide states that older signup versions were deprecated on 15 October 2026. Ask the provider to confirm its onboarding implementation uses the supported version rather than following an old tutorial.

Eligibility should be checked for the actual account and provider flow. Do not delete the existing Business app account to follow generic full-API instructions: Coexistence is specifically designed to connect that account.

For a UAE implementation, the Coexistence setup guide covers the local onboarding context. The underlying technical model described here applies globally.

How message rules and fees work

Meta distinguishes messages sent from the Business app from those sent through Cloud API. Its Coexistence documentation says app-sent messages continue to be free, while API-sent messages follow the applicable API pricing rules.

The API's 24-hour customer service window also remains relevant. An app reply does not open or extend that API window. A customer message received before API onboarding does not retroactively create an API service window after the number connects.

Use Meta's current pricing documentation for charges and exceptions. App access should not be presented as a way to bypass the rules for software-generated messages.

Zena's subscription and Meta's message fees are separate. Zena adds zero markup to Meta fees on every plan. This does not make all messages sent through the API free.

Coexistence or Cloud API without the app?

Choose based on the operating model you want to maintain.

Coexistence deserves consideration when continued Business app access matters, the supported individual-chat model fits your work, and the throughput limit accommodates your expected traffic. It can help introduce shared visibility while staff retain a familiar interface.

A Cloud API connection without continued app use deserves consideration when the team wants a central software inbox, needs capabilities incompatible with Coexistence, or has workloads that require a different throughput profile. Eligibility and capacity still need to be checked.

For a UAE business, the API versus Coexistence comparison connects these trade-offs to practical team decisions. The UAE Coexistence overview provides the local product route.

Can you change the connection later?

Treat a later move as a planned change to the number's operating model. Inventory the app conversations, history requirements, templates, connected systems and staff access before deciding how the transition should work.

Meta documents disconnecting Coexistence from the Business app under Settings > Account > Business Platform. It also states that the ordinary API deregistration endpoint cannot deregister a number while it is used with both the app and Cloud API.

Disconnecting is not a complete migration recipe. The provider must confirm the subsequent onboarding or registration path, preserved assets and any service interruption for the specific account. Keep the app connection until that plan is understood; do not assume historical messages and workflow configuration automatically transfer.

Test the replacement process with controlled conversations before retiring the old way of working. Staff should know where to reply and where to find unresolved requests.

Start with the work you want to improve

The best reason to connect the app and API is a clear business need: less copying between systems, clearer ownership of enquiries, or a repeatable way to collect request details.

Zena's planner starts with your business and suggests relevant automation possibilities. You can then assess the right connection during onboarding, with the current app workflow and Meta's limitations in view.

See what your business can automate