WhatsApp coexistence connects a WhatsApp Business app number to the WhatsApp Business API without changing numbers. The business sends at volume through the API, chats one-on-one on the phone, and keeps the message history synced on both sides.
Without coexistence, a company had to choose between the WhatsApp Business app and the API, and migrating meant leaving the phone and old conversations behind. According to Meta’s documentation, with the feature turned on, both channels work together.
Key Takeaways
- Coexistence links the WhatsApp Business app to the Cloud API through a provider, with no number change and up to 180 days of synced history.
- Messages sent from the app remain free, but groups, calls, and the catalog stay app-only, and broadcast lists become read-only.
- The primary phone cannot go about 14 days without use, and the provider has 24 hours to complete the sync during activation.
What Is WhatsApp Coexistence
In practice, coexistence is a connection method, not a new app. The number stays in the WhatsApp Business app and is also served by a platform connected to the API.
Defining Coexistence Between the App and the API
According to Meta, coexistence connects a WhatsApp Business app account to the Cloud API. Volume sends go out through the API, while the team keeps handling one-on-one chats in the app on the phone. There is no second number or second account to share with customers, which keeps the company’s communication simple.
Messages are mirrored on both sides. What the customer sends shows up on the phone and on the platform, and what the business replies in one channel is logged in the other. There is a single history.
App vs. API vs. Coexistence
Meta explains the difference between the standard app and the business app on its WhatsApp vs. WhatsApp Business page. Coexistence is designed for companies that already use the WhatsApp Business app.
The table below summarizes each model. The middle column represents the Cloud API used without the app, and the last column shows both channels sharing the same business number.
| Criteria | WhatsApp Business app | Cloud API alone | Coexistence |
|---|---|---|---|
| Number | Number used on the phone | Number connected to the API | Same number as the app |
| Service on the phone | Yes | No | Yes, through the app |
| Volume sends with templates | No | Yes | Yes, through the API |
| AI and system integration | No | Yes | Yes, through the API |
| App groups and calls | Yes | Not applicable | Remain app-only |
| Cost of app messages | Free | Not applicable | Free |
| Cost of API messages | Not applicable | Meta’s official rate card | Meta’s official rate card |
Why Use WhatsApp Coexistence
Businesses that already serve customers through the app often delay moving to the API for fear of losing conversations, contacts, and the number itself. WhatsApp coexistence addresses that concern and reduces friction, with no overnight switch.
Keep Your Number, Contacts, and History
With coexistence, the business does not change numbers or start from scratch. Recent conversations and the contact list move to the platform, and customers keep messaging the same WhatsApp number as always.
Moving to the official API also removes the need for unofficial tools, a frequent cause of a banned number. That does not make blocks impossible, since quality and consent rules still apply to every send.
Add AI, Templates, and CRM to Human Service
The API connection opens the door to AI agents, scheduled sends, and CRM integration that logs every conversation in the customer record. Meanwhile, the team stays in the app for conversations that need a human touch.
Another gain is Meta-approved message templates. They are the only message type allowed outside the 24-hour window and fall into three categories: marketing, utility, and authentication. The guide to WhatsApp message templates covers them in detail.
Coexistence Requirements and Activation
Activation depends on a Meta provider, a recent app version, and a sync window with a fixed deadline.
Meta Provider and Embedded Signup
Under Meta’s rules, coexistence can only be activated through a Solution Partner or a Tech Provider. Meta’s solution providers page explains how these providers work.
The provider must offer the Cloud API and Embedded Signup, Meta’s built-in onboarding flow. It must also subscribe to three webhooks, which are automatic notifications Meta sends to the platform:
- history: delivers the app’s chat history during the initial sync.
- smb_app_state_sync: keeps the app’s contacts up to date on the platform.
- smb_message_echoes: mirrors on the platform the messages the business sends from the app.
When comparing WhatsApp AI tools, it is worth confirming this point: without all three webhooks, the sync is incomplete.
App Version and Supported Devices
The app must be on version 2.24.17 or later. Meta’s coexistence rules allow up to four linked devices, all supported except WhatsApp for Windows and WearOS, the smartwatch operating system.
The page does not detail unsupported countries or a minimum age for the number. Those points should be checked with the provider, along with the plan for multiple agents on the same number.
Step by Step and the 24-Hour Deadline
The official flow starts on the provider’s website and ends on the primary phone, with no coding required from the business:
- Choose the option: on the provider’s website, the business indicates it wants to connect the WhatsApp Business app account it already uses.
- Enter the number: the business types the number and receives a code.
- Open the app: on the phone, it opens the message from the official Facebook Business account and taps the option to connect to a business platform.
- Authorize: it agrees to share chat history and pastes the code it received.
- Sync: the provider starts syncing contacts and messages.
After authorization, the provider has 24 hours to sync the data. If the deadline passes, the flow must be restarted. During activation, all linked devices are logged out, and supported ones can reconnect right after.
Customer service best practices help during this window: pick a low-traffic time, brief the team, and confirm that messages reach the platform. From then on, service automation can run through the API.
How History Sync Works
The most common question about WhatsApp coexistence is whether old conversations will be lost. The answer lies in how Meta structures the data transfer between the app and the platform.
Messages from the Last 180 Days in Three Phases
According to the official coexistence documentation, messages from the last 180 days are imported in three phases: day 0 to 1, days 1 to 90, and days 90 to 180.
As a result, the platform shows the most recent conversations first and fills in the rest gradually. The history does not disappear; it arrives in stages, and the team should know this so they do not assume something failed.
With the history in one place, WhatsApp customer service gains context. Whoever takes over the conversation, a person or an AI agent, can see what was already agreed with that customer.
Media, Contacts, and Mirrored Messages
Photos, audio, and documents older than 14 days arrive later, in separate webhooks. An old conversation may first appear with text only and receive its attachments later, with no content lost.
All contacts with WhatsApp are synced, and later changes are too. After the initial load, every new message sent from the app or the platform appears in the other channel.
What Changes in the App and WhatsApp Web
The phone keeps working after activation, but some features behave differently. Knowing these changes in advance avoids surprises for the team and for customers.
Disabled Features and Broadcast Lists
The official documentation says three features stop working in one-on-one chats. Teams that use any of them in customer service need to adjust their routine before connecting the number:
- Disappearing messages: turned off in one-on-one chats.
- View once: photos and videos of this type are also turned off.
- Live location: real-time location sharing is no longer available.
Broadcast lists become read-only, and new ones cannot be created. Mass sends move to templates through the API, which requires contact consent under the WhatsApp Business Messaging Policy.
On the plus side, editing and deleting messages becomes possible. To run campaigns within these rules, service automation should include opt-in and unsubscribe from day one.
Groups, Calls, and Catalog Stay in the App
Groups are not synced and do not work in the Cloud API, so they stay app-only. Voice and video calls, catalog, orders, status, and labels also work as before on the phone, but not through the API.
This affects automation, because a WhatsApp chatbot only sees what passes through the API. Catalog orders or group conversations, for example, are out of the bot’s reach.
WhatsApp Web and Unsupported Devices
Messages sent from unsupported devices, such as WhatsApp for Windows and WearOS, do not trigger a webhook, and the customer sees a notice. The team should avoid these devices for customer service after activation.
The documentation does not mention WhatsApp Web, but it is not among the excluded devices, so it will likely keep working; the provider should confirm. As a linked device, it must be reconnected after activation and drops after about 30 days of inactivity (COMPANION_INACTIVITY).
WhatsApp Coexistence Costs
Whether app messages will be charged is a frequent question among companies evaluating coexistence. The answer requires separating what Meta charges for the official API from what stays free.
App Messages Remain Free
Messages sent from the WhatsApp Business app remain free with coexistence. Only messages sent through the Cloud API follow the API rate card, according to Meta’s documentation, even in long conversations on the phone.
These app messages do not open or extend the API customer service windows. A reply from the phone, therefore, does not renew the platform’s window to reply without a template.
That is why it makes sense to map the sales funnel and define the channel for each stage. A clinic, for example, can confirm appointments with a utility template through the API and leave package negotiations to the front desk in the app.
Per-Message Pricing on the API
According to Meta’s pricing page, since July 1, 2025, Meta charges per delivered message. The rate depends on the category (marketing, utility, or authentication) and on the recipient’s country. Non-template messages and utility templates inside the window were free through September 30, 2026. From October 1, 2026, Meta charges for both, with 1,000 free service messages delivered per phone number per month. In Brazil, for example, that rate is R$ 0.035 per delivered message. The WhatsApp API pricing guide explains the change. Messages sent from the app with coexistence remain free.
Meta reviews these rules periodically, so check the official rate card before budgeting actions such as sales follow-up. This guide does not list other prices, which depend on the category and can change.
In Brazil, since March 11, 2026, the AI provider rule charges general-purpose assistants for non-template messages to +55 numbers. Companies that use AI in their own customer service are not covered by this rule.
Limits, Quality, and the 14-Day Rule
WhatsApp coexistence does not exempt the number from the official API rules. Beyond limits and the quality rating, the primary phone gains a new obligation: it cannot sit idle.
Messaging Tiers and Throughput
Under Meta’s rules for coexistence numbers, throughput is 20 messages per second, a pace to factor into large campaigns and AI chatbot flows.
Messaging limits count unique recipients in 24 hours and rise in tiers: 250, 2,000, 10,000, 100,000, and unlimited. With the October 2025 change, the limit applies per portfolio, and a quality drop no longer downgrades the tier.
Quality Rating and Template Pausing
Meta gives templates a high, medium, or low quality rating based on signals from the last seven days, such as blocks and reports, which grow when messages go out without consent. When these signals pile up, template pausing kicks in: first for 3 hours, then for 6 hours, and if the problem persists, the template is disabled.
Monitoring customer service metrics, such as reply rate and unsubscribe requests, shows early when a campaign starts to annoy people. Adjusting audience and frequency protects template quality and the number’s reputation.
Primary Phone Inactivity
If the primary phone goes about 14 days without use, the API connection drops, and the coexistence documentation records the reason as PRIMARY_INACTIVITY. The disconnection interrupts the integration and can leave customers without replies from the platform.
Prevention is a routine where someone on the team opens the app on the primary phone regularly, with a recurring calendar reminder. AI replies go out through the API and do not count as phone usage.
Who Should Use Coexistence
Not every operation gains the same from coexistence. The assessment below is editorial, based on Meta’s rules, and helps decide whether to turn the feature on now.
Profiles That Gain the Most and Watch-Outs
The decision depends on how the company already serves customers, which app features it uses day to day, and what it plans to automate. Three profiles sum up the picture:
- Teams already serving through the app: gain AI, templates, and CRM without changing numbers or losing history.
- Teams that rely on groups or calls: can activate it, knowing these features stay on the phone only.
- Teams that rarely open the primary phone: need a routine against the 14-day rule before activating.
ConverZap AI Agents with Coexistence
ConverZap is a WhatsApp AI agent platform that works with the official API in coexistence mode, activated through Meta’s official Embedded Signup. The team stays in the app, while the agents answer, qualify leads, and take actions in other systems.
Bulk messaging follows a compliant format, with approved templates and an unsubscribe button. The platform also handles re-engagement, promotions, transactional messages, and reminders, with integrations to databases, CRMs, and dashboards.
Because the synced history contains personal data, processing must comply with Brazil’s data protection law (LGPD, in Portuguese); similar rules apply under GDPR in the EU. Agents follow rules set by the business and need protection against manipulation, a risk known as prompt hacking.
WhatsApp Coexistence FAQ
Mirroring shows on both sides what has already been sent, but it does not stop two people from replying at the same time. Set an internal rule on who owns each conversation, for example leaving first contact to the AI agent and negotiations to whoever works in the app.
The feature was built for WhatsApp Business app accounts, according to Meta’s documentation. Anyone serving customers on the standard WhatsApp app should first evaluate moving to the business app.
When the connection drops because the primary phone was inactive, the connection to the platform must be redone. The documentation reviewed does not detail this procedure, so the steps should be confirmed with the provider.
In the app, the path is Settings > Account > Business Platform > Disconnect account. After that, the platform stops receiving messages, and customer service depends on the app alone.
Conclusion
Coexistence ends the old choice between the phone and scale: the number stays, recent history comes along, and the API takes on templates, AI, and integrations. In return, the business accepts features that remain app-only, per-message pricing on the API, and the discipline of keeping the primary phone in use.
To connect your current number to the official API without giving up the app, talk to the ConverZap team about AI agents with coexistence.
