WhatsApp Coexist: The Complete Guide to Using WhatsApp Business and API on the Same Number

WhatsApp Coexist, also known as WhatsApp Coexistence, WhatsApp CoEx, or coexistence mode, allows a company to use the same number simultaneously on the WhatsApp Business app and the Official WhatsApp API.

In practice, the owner or team can continue responding via mobile phone, while a platform like Hablla uses the Cloud API to centralize service, distribute conversations among users, execute automations, integrate CRM, utilize artificial intelligence agents, and send official templates.

This modality reduces one of the main barriers to the adoption of the Official API: the fear of losing the number, the application, and the history already used by the company.

However, WhatsApp Coexist does not eliminate the Official API rules. Messages sent via the platform remain subject to Meta's policies, costs, limits, and quality system.

This article was updated on August 4, 2026, and considers the current rules and the billing changes announced for October 1, 2026.

Summary: How WhatsApp Coexist Works

With coexistence mode:

• The same number continues to work on the WhatsApp Business app on the mobile phone;
• The number is also connected to the Cloud API;
• New messages can be viewed in the app and on the platform;
• Messages sent through the app may appear on the platform as echo messages;
• The platform can utilize CRM, automations, chatbots, and IA agents;
• Sendings performed via the API follow the standard rules of the WhatsApp Business Platform;
• Sendings performed manually via the app remain outside of Cloud API billing;
• Responding via the app does not open or renew the API service window;
• Some features of the app are limited or stop being synchronized.

Meta documents this modality as the onboarding of users who already use the WhatsApp Business App. In support channels and provider documentation, the feature is commonly called Coexistence.

slug: what-is-whatsapp-coexistence

What is WhatsApp Coexistence?

WhatsApp Coexistence is an official Meta configuration that allows you to connect a number already registered and active on the WhatsApp Business app to the Cloud API.

Prior to this functionality, a company wishing to use the Official API had to remove the number from the application. After migration, the number became available exclusively for use through the API and integrated platforms.

With Coexistence, the two environments operate in parallel:

WhatsApp Business App — used by the owner or employees on a mobile device for manual conversations, calls, groups, and other native functions.

WhatsApp Business Platform (Cloud API) — used by platforms like Hablla for team service, automation, CRM, integrations, IA agents, templates, and operational management.

WhatsApp Coexistence, therefore, is not a different API. It is an activation modality of the Official API itself, keeping the WhatsApp Business App connected to the same number.

WhatsApp Coexist, Coexistence, or CoEx: what is the correct name?

The most widely used name internationally is WhatsApp Business App Coexistence.

In Brazil and elsewhere, people also search for:

• WhatsApp Coexist;
• WhatsApp CoEx;
• WhatsApp coexistence;
• WhatsApp coexistence mode;
• WhatsApp Business and API on the same number;
• Official WhatsApp API on mobile.

"WhatsApp Coexist" is not the full technical denomination, but it is a shorthand used by companies, users, and providers. For this reason, this article uses the keyword WhatsApp Coexist in the title, but also works semantically with WhatsApp Coexistence and WhatsApp coexistence.

What is the difference between WhatsApp Business, Coexistence, and Exclusive API?

Coexistence should be understood as a hybrid architecture. It combines the convenience of the application with part of the scalability of the API, but it does not offer exactly the same governance as a number operated exclusively by the Cloud API.

slug: whatsapp-coexist-api-rules

Are the API rules different in WhatsApp Coexist?

No. Deliveries from the platform follow the same rules as the Official API. This is the most important point of the entire article: WhatsApp Coexist does not create an exception to the Official API policies.

Everything sent via Hablla or another platform connected to the Cloud API will continue to be subject to:

• template categories;
• Meta approval;
• opt-in;
• quality rating;
• message limits;
• template pacing;
• marketing frequency per user;
• per-message billing;
• commerce and messaging policies;
• potential restrictions and blocks.

What changes is that the company retains the ability to send messages manually through the WhatsApp Business App. The app and the API use the same number, but have different operational and financial behaviors.

slug: how-the-24-hour-window-works-in-whatsapp-coexist

How does the 24-hour window work in WhatsApp Coexist?

The 24-hour service window, officially called the Customer Service Window, opens when the consumer sends a message to the company.

From the last message received from the customer, the company has 24 hours to send free-form messages via the API, such as text, audio, image, video, document, location, interactive messages, human agent responses, and IAm responses.

Meta defines the window based on the message sent by the user. The current pricing model differentiates between template messages and free-form messages sent during this window.

Does a message sent via the app renew the API window?

No.

When an agent sends a message through the WhatsApp Business App, this message can be replicated on the platform as an echo message, or message echo.

The echo message:

• does not open a new API window;
• does not renew the existing window;
• is not a new message received from the customer;
• should not be treated as an inbound;
• does not allow the platform to continue sending free-form messages after the window expires.

Practical example

The customer sends a message on Monday at 10 AM. The API window will remain open until Tuesday at 10 AM. The agent responds via the app on Tuesday at 9:50 AM. This manual response does not extend the window until Wednesday. If the customer does not respond again, starting at 10 AM, the platform will need to use an approved template to send another message.

Which timestamp should the platform consider?

To correctly control the window, the platform must consider the date and time of the last message received from the consumer.

One should not simply use the last message of the conversation, as it could have been sent by the platform, by an automation, by an IAm, by the WhatsApp Business App, or by a linked device.

At Hablla, the operation must clearly differentiate between received messages, API messages, and app echo messages.

slug: are-whatsapp-business-app-messages-charged

Are messages sent via the WhatsApp Business App charged?

Messages sent directly through the WhatsApp Business App remain free from a Cloud API perspective. They:

• do not generate API message charges;
• do not consume the limit of API-initiated messages;
• may appear on the platform as echo messages;
• do not open or renew the API window;
• remain subject to the general policies of the WhatsApp Business App.

Only messages sent via the platform using the Cloud API fall under the charging rules of the WhatsApp Business Platform.

This does not mean the app can be used to circumvent policies. Performing repetitive, unsolicited, or bulk manual sends still carries the risk of reports, blocks, restrictions, quality reduction, and account suspension. If you want to understand what usually gets a number taken down, see the guide why WhatsApp Business is banned.

Coexistence does not turn the app into a mass broadcasting tool.

How do templates work in WhatsApp Coexistence?

Templates for a number in Coexistence go through the exact same creation, classification, and approval process used by any other Cloud API number. The categories remain:

Marketing — promotional campaigns, offers, product launches, cart recovery, customer reactivation, demand generation, commercial relationship building, and content that encourages a new purchase.

Utility — messages directly related to a purchase, an order, a reservation, a request, a contracted service, an operational update, or an action previously initiated by the consumer.

Authentication — access codes, authentication, account recovery, identity verification, and one-time passwords.

The fact that the number is also connected to the app does not make approval simpler and does not allow a promotional message to be classified as Utility. Meta may reclassify templates when the content is not aligned with the selected category.

Does Coexistence make template approval easier?

No. The analysis considers the content and context of the template, regardless of whether the number is exclusively on the Cloud API, connected via Coexistence, linked to Hablla, or another provider. There is also no special template category for Coexistence.

slug: how-whatsapp-coexist-billing-works

How does billing work in WhatsApp Coexist?

Rules in effect until September 30, 2026

Marketing Templates continue to be charged even when an open service window exists.

Changes starting October 1, 2026

Meta announced a relevant change in Official API billing. Starting October 1, 2026:

• free-form service messages sent via API within the window will be charged per message;
• Utility templates sent within the window will also be charged;
• messages sent via the app will remain outside the Cloud API billing;
• messages received from consumers will remain free;
• Marketing and Authentication templates will continue to be charged.

The 24-hour window will continue to exist, but it will primarily control the permission to send free-form messages, rather than the free status of those messages.

Meta informed that it will publish the rates that will come into effect in October by September 1, 2026. To simulate the impact on your number, use the WhatsApp new billing calculator.

This means that companies with large service operations must monitor not only the number of conversations but also the number of messages sent in each service interaction. A conversation resolved in two messages may have a very different cost than a conversation with fifteen fragmented responses.

slug: whatsapp-coexist-tiers-quality-policies

Does WhatsApp Coexist have different tiers?

There is no exclusive tier for numbers in Coexistence. The number enters the standard messaging limits model of the WhatsApp Business Platform. The Embedded Signup documentation states that companies activated through this flow start with the platform's normal limits, which can evolve based on eligibility and usage.

Messaging limits control how many unique customers a business can proactively contact within a 24-hour rolling window. They should not be confused with throughput.

• Messaging limit — controls how many unique consumers can receive business-initiated messages.
• Throughput — controls how many messages can be technically processed per second.

In Coexistence, throughput is limited to 20 messages per second in current implementations. This limit is specific to the hybrid architecture and may be lower than the throughput of a number exclusively connected to the Cloud API.

Therefore, a number can have a high messaging limit and still be limited to 20 messages per second in Coexistence. For large-scale Marketing operations, this limit must be considered in campaign planning and sending queues.

Quality, blocks, and policies in WhatsApp Coexist

A number in Coexistence does not have a separate reputation for the app and the API. Sends performed via API can affect number quality, template quality, the ability to start new conversations, pacing, campaign delivery, template availability, WABA restrictions, and the possibility of being blocked.

Among the main risk indicators are:

• high number of blocks;
• reports;
• low read rates;
• content differing from the opt-in;
• excessive messaging;
• high frequency;
• outdated lists;
• lack of context;
• incorrectly classified templates;
• difficulty in opting out of communications.

Coexistence should be used to facilitate the transition to a professional operation, not to sustain non-consensual broadcasting practices. If your number has already been restricted, the guide to recovering a banned WhatsApp shows the way.

slug: is-conversation-history-synchronized-in-whatsapp-coexistence

Is conversation history synchronized?

The availability of synchronization depends on the provider's implementation and the version of the flow released by Meta.

Some current flows allow the user to authorize the sharing of up to 180 days of history. Other providers still only synchronize messages received and sent after activation. Therefore, the company should not assume that the entire history will be imported automatically.

There are three possibilities:

1. The history remains only in the application.
2. The platform receives only new messages.
3. The platform imports part of the history, if the flow and the provider offer this option.

Before activation, confirm how many months will be imported, if contacts will also be synchronized, if media will be imported, if old messages can trigger automations, if history will be available to all agents, and if the process needs to be authorized on the mobile device.

Which app features change after activating Coexistence?

After the connection, some functions of the WhatsApp Business App may be deactivated or stop being synchronized with the API.

Individual conversations — continue to work in the app and on the platform. New messages can be mirrored between environments.

Groups — remain available in the app, but are not synchronized with the Cloud API. The platform will not receive messages from groups, participants, group events, files sent in the group, or replies made within the group.

Voice and video calls — remain available in the WhatsApp Business App, but are not necessarily displayed or controlled by the platform.

Status and channels — remain linked to the app and are not synchronized as API conversations.

Broadcast lists — after activation, these may be deactivated. Existing lists may only be available for consultation. Campaigns shift to being conducted via the API, using approved templates, opt-in, and Meta's billing rules.

Ephemeral messages — may be deactivated in individual conversations.

View once — view-once messages may no longer be available.

Real-time location — live location sharing may be deactivated in individual conversations.

These limitations are applied by Meta's architecture and not by an isolated decision of the platform or the provider.

slug: what-happens-to-linked-devices-coexistence

What happens to linked devices?

During Coexistence activation, companion devices may be disconnected. The primary device remains connected, but the company may need to re-link WhatsApp Web, browsers, tablets, additional phones, and other companion devices.

Some devices may not correctly generate echo message webhooks. There are documented reports of limitations, especially in WhatsApp for Windows and WearOS.

Therefore, after activation, perform tests from each device used by the team. A message that appears on the mobile phone will not necessarily appear on the platform when sent by an unsupported device.

Is it necessary to keep opening WhatsApp Business?

Yes. In current implementations, the primary application must be opened periodically to keep the connection active. Some providers indicate the need to open WhatsApp Business at least once every 14 days. If this does not happen, the connection may be removed or experience synchronization issues.

As an operational best practice: keep the app installed and updated, do not change the number's device without planning, open the app regularly, monitor the API connection, and avoid deleting the app after activation.

Should an echo message trigger automation?

Technically, an echo message represents a message sent by the company itself through the app. It should not be treated the same way as a message received from a consumer.

If an automation is triggered indiscriminately by echo messages, several issues can occur: duplicate responses, loops between the app and automation, incorrect reopening of tickets, undue movement of opportunities, unnecessary triggering of IAm agents, incorrect SLA changes, and wrong calculation of the 24-hour window.

The platform needs to differentiate between at least three events:

1. Message received from the customer.
2. Message sent by the platform.
3. Message sent by the WhatsApp Business App.

In the Marketing Conversacional Integrado architecture, this separation allows for the integration of service, CRM, Customer Success, automation, and Business Performance without losing the origin and context of each interaction.

slug: when-to-use-whatsapp-coexist-vs-cloud-api

When is it worth using WhatsApp Coexist?

Coexistence is recommended when:

• the company already uses WhatsApp Business intensely;
• the number is well-known by customers;
• there is resistance to abandoning the mobile device;
• the owner still wishes to respond personally;
• the company wants to adopt CRM and automations gradually;
• it is necessary to maintain groups and calls within the app;
• the operation is still transitioning to an omnichannel model;
• the company does not have a large volume of campaigns;
• maintaining number continuity is more important than centralizing all governance.

It tends to be especially useful for small and medium-sized businesses, clinics, stores, service providers, real estate agencies, offices, local businesses, companies led directly by the owner, and commercial operations that started on a mobile device.

When is the exclusive Cloud API more indicated?

An exclusive Cloud API number tends to be more suitable when the company has a large volume of messages, many agents, 24-hour operation, multiple departments, strict security requirements, auditing needs, centralized governance, large-scale Marketing campaigns, critical integrations with CRM or ERP, processes that cannot depend on a physical device, the need for higher throughput, and policies that prohibit service outside the platform.

In an enterprise operation, allowing parallel responses through the app can reduce traceability. An agent might respond via mobile without selecting an opportunity, classifying the reason, logging a ticket, updating the CRM, following a playbook, respecting queue distribution, or informing the next step.

Therefore, Coexistence should be an architectural choice, not just a preference for keeping the app.

Is WhatsApp Coexist an unofficial API?

No. WhatsApp Coexist utilizes Meta's own Cloud API and the official Embedded Signup flow.

It should not be confused with solutions that connect WhatsApp through unofficial QR Codes, WhatsApp Web emulation, reverse libraries, browser automation, modified apps, or non-certified sessions.

In official Coexistence, the connection is authorized by Meta within the onboarding flow. Before hiring a platform, verify:

• if the connection uses Meta login;
• if a WABA exists;
• if the number appears in the WhatsApp Manager;
• if templates are approved by Meta;
• if there is official billing from the WhatsApp Business Platform;
• if the platform is an official solution or integrated with an authorized provider.

slug: how-to-activate-whatsapp-coexist-on-your-platform

How to activate WhatsApp Coexist on your platform

Screen names may change according to Embedded Signup updates, but the workflow typically follows these steps:

1. Confirm the number is on WhatsApp Business. Numbers used only on personal WhatsApp must be converted to the business app before onboarding.
2. Update the app. Current documentation indicates version 2.24.17 as the minimum requirement.
3. Verify Meta portfolio access. The person performing the connection must have sufficient permissions in the Meta Business Portfolio, preferably with full control.
4. Start onboarding on the platform, choosing the option equivalent to "connect WhatsApp Business," "use the app and the API," "connect existing number," or "WhatsApp Coexistence."
5. Log in to Meta and authorize Embedded Signup permissions. Check the selected portfolio, WABA, number, business name, connected partner, and payment method.
6. Confirm the connection on the mobile phone. WhatsApp Business may request a confirmation on the primary device; keep the app open during the process.
7. Choose whether to share history, confirming the period and import conditions.
8. Wait for synchronization. The time will depend on the volume of contacts, messages, and media.
9. Reconnect companion devices — WhatsApp Web, tablets, and additional mobile phones.
10. Perform full tests: received message, reply via app, reply via platform, echo message, opening and expiration of the 24-hour window, template sending, media sending, automation, distribution to agents, CRM update, and linked devices.

Checklist before activating WhatsApp Coexist

• The number is on WhatsApp Business, not personal WhatsApp.
• The app is updated.
• The person in charge has full control in Meta.
• The correct business portfolio has been identified.
• The company understands API billing.
• Agents have been guided on echo messages.
• There is a policy for app usage.
• The necessary templates have already been planned.
• Contact opt-in is documented.
• Important history is backed up.
• Linked devices have been mapped.
• The company knows which app features will be disabled.
• The impact of the 20 messages per second limit has been evaluated.
• There is a contingency plan for loss of synchronization.
• Automations differentiate between received messages and echo messages.

slug: best-practices-for-using-coexistence-securely

Best practices for using Coexistence securely

Define who can respond via the app

Do not allow all employees to respond indiscriminately through both the mobile app and the platform. Define responsible parties, schedules, types of service, exceptions, rules for strategic clients, and criteria for returning to the platform queue.

Use the platform as the primary data source

Even with the app active, CRM, tickets, opportunities, and metrics must remain centralized. The app should be a complementary interface, not a parallel management system.

Do not use the app to bypass templates

When the API window is closed, sending manually via the app solely to avoid costs or template approval can fragment the operation and increase the risk of improper practices.

Control opt-in

Coexistence does not replace consumer authorization. Record the origin of consent, date, purpose, channel, campaign, text presented, and the possibility of cancellation.

Monitor conversation context

An operation of Marketing Conversacional Integrado needs to consider not only the message but also the 8Cs: client, context, content, communication, cost, convenience, confidence, and consistency. These eight elements prevent Coexistence from being used merely as technical infrastructure without a relationship strategy. To measure where your operation stands today, use the Diagnóstico MCI da Operação de WhatsApp.

Reduce fragmented messages

With the billing of service messages starting in October 2026, responses like "Hello.", "How are you?", "Checking now.", "Just a moment.", and "Your order has been shipped." could generate five separate charges via the API.

Prefer a more complete response:

"Hello, I have checked your order and it has already been shipped. The delivery estimate is Thursday, and the tracking code is ABC123."

In addition to reducing costs, this approach improves clarity, context, and experience.

slug: is-whatsapp-coexist-worth-it

Conclusion: Is WhatsApp Coexist worth it?

WhatsApp Coexist represents an important evolution of the official API because it allows companies to gradually professionalize their operations without immediately abandoning the application, the number, and established habits.

It is especially relevant for companies that need to combine personal service via mobile, multiple agents, CRM, automations, IAm agents, official templates, commercial governance, and data integration.

On the other hand, coexistence does not mean an absence of rules. Messages sent through the platform remain subject to Meta's policies, billing, templates, service windows, and quality systems.

The decision between Coexistence and an exclusive Cloud API should consider the company's maturity stage, volume, governance, and the experience it wishes to build for the customer.

Coexistence can be part of a broader Marketing Conversacional Integrado architecture, connecting Service, Marketing, Sales, Customer Success, Customer Experience, and Business Performance into a single conversational journey.

The goal is not just to keep WhatsApp on the mobile phone. The goal is to transform every conversation into context, relationship, operational efficiency, and revenue generation.