WhatsApp Coexistence: Use the Official API Without Leaving the App

Updated in October 2026, based on Meta documentation reviewed on October 6, 2026.

WhatsApp coexistence connects a WhatsApp Business app number to the WhatsApp Business API without changing numbers. The business sends at scale through the Cloud API, keeps chatting on the phone, and WhatsApp keeps the history in sync on both sides.

This guide covers what Meta’s official documentation says as of October 2026: requirements, countries, setup steps, what syncs, features that change, costs, limits, activation errors, and how to disconnect or change phones.

Key Takeaways

• Coexistence is a Meta feature activated by a partner (Solution Partner or Tech Provider) through Embedded Signup: the number stays in the app and also runs on the WhatsApp Cloud API. ConverZAP, a Meta-verified Tech Provider, has offered it inside its own app since October 2026.
• Up to 6 months of one-to-one chats can be synced if the business allows it, but groups are left out, and media older than 14 days arrives only as a placeholder.
• Messages sent from the app remain free; on the API, the number gets 20 messages per second, and the connection drops if the primary phone stays inactive for about 14 days.

What Is WhatsApp Coexistence

WhatsApp coexistence is the Meta feature that links a WhatsApp Business app account to the Cloud API on the same number, so the business can use both channels at once. It is not a new app; it is a way of connecting.

Official Name and How Meta Describes the Feature

In its developer documentation, Meta calls the feature “Onboard WhatsApp Business app users” and notes that it is sometimes called “Coexistence”. Partners, support channels, and the market have adopted coexistence as the name for this flow.

According to the feature’s official page, after the connection the business sends high-volume messages through the partner’s platform, keeps sending one-to-one messages from the app, and has its history synced between the two channels.

Mirroring Between the App and the Platform

Sent and received messages are mirrored between the Cloud API and the app. What the customer writes appears on the phone and in the platform, and a reply given on one side is recorded on the other, with no parallel conversations.

In practice, the team stays in the WhatsApp Business app for conversations that need a human touch, while AI agents for WhatsApp, integrations, and template sends run through the API, with no second number to announce to customers.

App vs. WhatsApp Coexistence vs Cloud API: What’s the Difference

The difference is where the number lives: only in the app, in the app and on the Cloud API at the same time (coexistence), or only on the Cloud API. Each model trades simplicity for scale in a different way, as the table shows.

The comparison uses the Meta documentation reviewed in October 2026. The full analysis, with decision scenarios by type of operation, is in the guide WhatsApp coexistence vs Cloud API: which to choose.

When Coexistence Makes the Most Sense

Coexistence suits businesses that already have customers chatting in the app and want to add automation without changing numbers. Contacts and recent conversations move to the platform, and the team keeps groups, calls, and the catalog on the phone.

It also helps businesses leave unofficial WhatsApp APIs, a frequent cause of a banned WhatsApp number. The official API reduces that risk but does not eliminate blocks: quality and consent still apply to every send.

When the Cloud API Alone Is Better

The Cloud API without the app makes more sense for high-volume operations, because the default throughput is higher and can scale automatically, according to Meta’s throughput page. It is also the path to the Calling API.

WhatsApp Coexistence Requirements in October 2026

To activate coexistence, the business needs a number active on an up-to-date WhatsApp Business app, and the partner must be a Meta Solution Partner or Tech Provider with Embedded Signup set up. The details follow the October 2026 documentation.

What the Business Needs

Based on the documentation and the official Embedded Signup errors list, the business has to meet five conditions:

• Updated app: WhatsApp Business on version 2.24.17 or later.
• Number registered in the app: without it, the flow returns a number-not-registered error.
• Real use of the app: Meta asks for “more activity” when the number is not eligible, without publishing a minimum number of days or messages.
• A free number: it cannot be registered on the Cloud API or connected to another platform.
• An account without blockers: a number not linked to a Facebook Page, and a WhatsApp Business account (WABA) that does not use the Marketing Messages API.

Countries: Where Coexistence Is Available

Brazil (+55) never appeared on Meta’s list of unsupported countries, not even in the May 2025 version. Brazilian businesses have been able to use coexistence since the feature first appeared in the official documentation.

The list changed over time: through October 2025, it excluded the European Union, the United Kingdom, Australia, Japan, and other markets; in November 2025, only Nigeria and South Africa remained; by June 2026, the list was gone from the documentation.

Even without a public list, error 3441042 still exists for numbers from regions that are not served. Articles that describe Europe as blocked rely on old versions of the rules, from before November 2025.

What the Partner Needs

The partner must be a Solution Partner or Tech Provider, run the Cloud API, use Embedded Signup with session logging, and have a webhook that processes the events. From version 3 onward, the flow uses the whatsapp_business_app_onboarding parameter.

To serve other businesses, the partner’s app needs Advanced Access approved in App Review. Without that approval, the permissions do not appear in the flow, and the partner cannot connect customers, with or without coexistence. ConverZAP’s App Review was approved on October 10, 2026, with Advanced Access to the whatsapp_business_messaging and whatsapp_business_management permissions.

How to Activate WhatsApp Coexistence Step by Step

Coexistence activation happens in the partner’s Embedded Signup and ends on the phone: the business enters the number, confirms the connection in the app, and decides whether to share its history. No coding is required.

The Five Steps of the Official Flow

In the flow described on Meta’s main page, confirmation uses a verification code. Pages for earlier Embedded Signup versions describe a QR code scanned in the app, so the screen varies with the version the partner uses:

1. Choose the option: in the partner’s signup, connect the existing WhatsApp Business app account.
2. Enter the number: type the app’s number and note the verification code shown.
3. Open the app: in the message from the official “Facebook Business” account, tap “Connect” and then “Connect to the Business Platform”.
4. Decide on history: tap “Confirm” and choose whether to share conversations.
5. Finish: paste the code into the partner’s signup or scan the QR code, depending on the flow version.

WhatsApp Coexistence at ConverZAP

ConverZAP, a Meta-verified Tech Provider, has offered WhatsApp coexistence since October 2026: the number stays in the WhatsApp Business app on the phone and also works on the official API, with AI agents, a team inbox, and campaigns with approved templates on the same number.

Activation happens inside the ConverZAP app, through Meta’s Embedded Signup, in a few steps:

1. Create the account: the 7-day free trial already includes connecting your own number, and signup does not ask for a card.
2. Choose the connection: in Integrations or WhatsApp Health, click “Number already using the WhatsApp Business app”.
3. Log in to Meta: in Meta’s window, log in with Facebook, choose the business portfolio, and enter the app’s number.
4. Confirm on the phone: in the WhatsApp Business app, confirm the connection with the QR code or the code shown, and decide whether to share your history.
5. Reconnect the computer: link WhatsApp Web again, since it is logged out during activation, and turn on the AI agent.

Recent one-to-one history (up to 6 months) can be imported in the first 24 hours. After that, messages you send from the phone show up in the ConverZAP inbox as “Sent from phone”, and the AI agent pauses so it doesn’t reply over you. Meta’s rules in this guide still apply: app version 2.24.17 or later, 20 messages per second, and regular use of the primary phone.

The step-by-step guide and a shortcut to get help on WhatsApp are on the connection card itself, and the same flow is in the coexistence setup guide.

What Happens After Activation

During activation, all linked devices, such as WhatsApp Web, are logged out. Supported ones can be linked again right away, and the team should be told in advance so the logout does not come as a surprise.

From then on, the partner has 24 hours to sync contacts and history. If the deadline passes, the business has to be disconnected and redo the flow. Meta recommends keeping the app open during the sync, which can take a few minutes.

What Syncs and What Doesn’t

With coexistence, contacts, one-to-one chats from the last 6 months (if the business allows it), and all new messages sync; groups and older media are left out. The table summarizes each item, according to Meta.

180 Days of History and 14 Days of Media

History arrives in three phases: day 0 to 1, day 1 to 90, and day 90 to 180. The platform shows recent conversations first and fills in the rest gradually, so a partial screen at the start is normal.

Media needs attention. Photos, audio, and documents sent up to 14 days before activation arrive with the file; older ones appear only as a media placeholder, without the file. Anyone who needs those attachments should save them first.

History Opt-In, Echoes, and the Service Window

Sharing history is optional. If the business declines in the app, the platform receives a notice with error 2593109 and starts without the old conversations. The decision is made in the app, during activation, and does not depend on the partner.

After activation, every message sent from the app reaches the platform as an echo. The API’s 24-hour customer service window, however, only opens when the customer writes after the connection; older messages can only be answered through the API with a template.

App Features That Change With WhatsApp Coexistence

With coexistence, the app keeps working, but some features are turned off in one-to-one chats and others stay on the phone only, without API support. The table below follows Meta’s October 2026 documentation.

The details on groups, broadcast lists, and calls, with the official alternatives, are in the guide to groups and broadcast lists with coexistence. For desktop use, the guide to WhatsApp Web with coexistence shows what keeps working.

Disabled Features and Broadcast Lists

Disappearing messages, view once, and live location are turned off in all one-to-one chats. In exchange, those chats now support editing and deleting messages, which calls for clear rules for the team.

Broadcast lists become read-only. Campaigns move to approved message templates sent through the API, with WhatsApp opt-in and unsubscribe, as the WhatsApp Business Messaging Policy requires. In Brazil, consent also follows the country’s data protection law (LGPD), and similar rules apply under GDPR in the EU. The guide to WhatsApp bulk messaging details this format.

Tools That Stay in the App Only

Groups, calls, catalog, orders, Status, business profile, and Channels stay the same on the phone, but the API does not see any of them. The Groups API is also unavailable for coexistence numbers, according to Meta.

Greeting messages, away messages, quick replies, and labels stay in the app and do not apply to the API. Businesses that rely on the app’s automatic messages need to rebuild those flows in the platform, or a WhatsApp chatbot will not follow them.

WhatsApp Web and Linked Devices

The business can link up to four companion devices. All are supported except WhatsApp for Windows and WhatsApp for Wear OS. WhatsApp Web works, but it needs to be linked again after activation.

Messages sent from an unsupported device do not reach the platform, and the business’s messages viewed on those devices appear as placeholder text. That is why the team should reply from the phone, WhatsApp Web, or the platform.

WhatsApp Coexistence Costs

With coexistence, messages sent from the WhatsApp Business app remain free, and only messages sent through the Cloud API follow Meta’s pricing. The bill separates the two channels, even when the conversation is the same.

Worked examples using Meta’s official rate card are in the guide to WhatsApp coexistence pricing.

App Messages: Free and Outside the Window

According to the coexistence documentation, sending from the app is not subject to the 24-hour window and does not open, extend, or affect API windows or charges. Meta’s official PDF guide confirms that groups, calls, and Status remain free.

API Messages: What Changed on October 1, 2026

Since July 1, 2025, Meta’s pricing page charges per delivered message, not per conversation, based on the category and the recipient’s country. The cost calculator for Brazil helps estimate volume before activating.

From October 1, 2026, Meta charges service messages and utility messages sent inside the 24-hour window, with 1,000 free service messages delivered per phone number per month, according to the official pricing announcement. In Brazil, for example, the rate card lists R$ 0.035 per service, utility, or authentication message and R$ 0.3217 per marketing message. The guide to WhatsApp API pricing details the change.

Messaging Limits and Throughput With Coexistence

A coexistence number has a fixed throughput of 20 messages per second, according to the Meta documentation reviewed in October 2026, and follows the same Cloud API messaging limits for messages sent through the API.

20 Messages per Second and What It Means

The throughput page states that the Cloud API without the app starts at 80 messages per second and can scale on its own to 1,000 for eligible numbers. The count includes sent and received messages; with coexistence, the rate is fixed.

Messaging Limits and Quality

Messaging limits count unique users in 24 hours: they start at 250, rise to 2,000, and then, automatically, to 10,000, 100,000, and unlimited. Businesses onboarded through Embedded Signup start at the default limit.

One-to-one messages sent from the app do not count toward these limits or toward API integrity. Messages sent through the API go through normal enforcement, and the WhatsApp quality rating should be monitored with every campaign.

Common Coexistence Activation Errors

Coexistence activation errors have official codes in the Embedded Signup documentation, and almost all of them are fixed on the business side: update the app, free up the number, or choose the right account. The main ones are below.

Official Codes and the Fix for Each One

According to the official errors page, reviewed in October 2026, these are the most common codes:

• 3441045: number not eligible; the official fix is to use the WhatsApp Business app more.
• 3441042: feature unavailable for the number’s region; use another number.
• 4563015: outdated app; update to version 2.24.17 or later.
• 2655095 and 2655048: number not registered with WhatsApp Business; register it in the app or use another one.
• 3441030: number already registered, for example on the API; deregister it or use another one.
• 3441049 and 2655094: number already connected to a platform; disconnect in the app and wait 15 minutes.
• 2655093: account already shared with another partner; disconnect the current partner in the app.
• 3441041: number outside the selected portfolio; choose the right portfolio.
• 2655082: number linked to a Facebook Page; unlink it in Meta Business Suite.
• 3441047: account uses the Marketing Messages API; choose another account.

How to Diagnose Before Repeating the Flow

Before trying again, write down the code shown, check the app version, and confirm whether the number has been on another platform. Repeating the flow without fixing the cause usually leads to the same error.

Causes, prevention, and steps for each code are in the guide to WhatsApp coexistence errors. For technical terms such as WABA, webhook, and portfolio, the official API glossary helps.

How to Disconnect or Change Phones

To disconnect coexistence, the business uses the app itself, in Settings > Account > Business Platform > Disconnect account; the Deregister API does not work for these numbers. Changing phones also drops the connection, which can come back on its own.

Disconnect the Account in the App

When the business disconnects, the platform receives the PARTNER_REMOVED event and stops receiving messages, and customer service depends on the app alone. The official account_update reference lists the reasons for each disconnection.

Phone Changes and Automatic Reconnection

When the business changes phones or reinstalls the app, the Cloud API connection drops automatically. On the new registration, the app shows a pre-checked option to reconnect the products; if the business leaves it checked, reconnection happens within a few minutes.

During that gap, API messages are suspended, the app is briefly unavailable, and history from the period is not synced. WhatsApp Web has to be linked again, and the reconnection fails if another partner connects the account first.

Inactivity: The 14-Day Rule

If the primary phone stays inactive for about 14 days, the system removes the connection to the partner and records the PRIMARY_INACTIVITY reason. The same reference lists COMPANION_INACTIVITY, tied to a linked device that has been inactive for about 30 days.

Meta does not set an interval for opening the app, but a weekly routine on the primary phone prevents the drop. Since the official reason refers to device inactivity, messages sent from the platform should not be treated as a substitute.

Who Should Use WhatsApp Coexistence and How to Start on the Official API

Coexistence is most valuable for businesses that already serve customers in the app and want to add automation without changing numbers; teams that work only in a platform, with multiple agents, tend to do better on the Cloud API alone. The decision starts with the current routine.

Businesses that use an unofficial connection today will find the steps in how to move from an unofficial API to coexistence, keeping the same number.

Profiles That Gain the Most and Watch-Outs

An editorial reading of Meta’s rules separates four profiles:

• Businesses already serving customers in the app: they gain AI, templates, and integrations without changing numbers.
• Businesses that rely on groups or calls: they can activate it, knowing those features stay on the phone only.
• High-volume senders: they need to account for the fixed rate of 20 messages per second.
• Businesses that rarely open the primary phone: they need a routine against the 14-day rule.

AI Agents on the Official API

ConverZAP is a platform of AI agents for WhatsApp that works with Meta’s official API. The agents answer, qualify, and take actions in CRMs and databases, and the team inbox brings multiple agents together.

Campaigns use approved templates, opt-in, and unsubscribe, and the CRM integration records every conversation. Since October 2026, ConverZAP also connects numbers through coexistence, as the section WhatsApp Coexistence at ConverZAP shows.

WhatsApp Coexistence FAQ

Conclusion

Coexistence ended the forced choice between the phone and scale: the number stays, recent conversations come along, and the API takes on templates, AI, and integrations. In return, the business accepts features limited to the app, 20 messages per second, and a primary phone that stays in use.

To activate coexistence and bring the same number to the official WhatsApp API, with AI agents, a team inbox, and campaigns with approved templates, see how coexistence works at ConverZAP or try it free with your own number.

Reviewed by Conrado Vita, Founder of ConverZAP.