WhatsApp Coexistence: How to use WhatsApp Business app and the API on one number
WhatsApp Coexistence lets you keep using the WhatsApp Business app while connecting the same number to the Cloud API for automation, AI, and a shared inbox.
TLDR
- WhatsApp Coexistence lets one phone number work in the WhatsApp Business app and through the Cloud API at the same time.
- Your team can keep replying from the phone while Visito handles AI responses, automation, and conversations in a shared inbox.
- You can choose to share contacts and up to six months of eligible one-to-one chat history during setup. Groups, calls, and several app-only features do not appear in the API inbox.
- Messages sent manually from the app remain free. Messages sent through Visito or another connected platform follow Meta's Cloud API pricing and messaging rules.
Moving an established WhatsApp number to the API used to create an awkward choice. You could keep the familiar Business app on the phone, or move the number to a platform built for automation and teamwork. You could not use both on the same number.
That was a serious problem for a hotel, clinic, shop, or local service business whose customers already knew one number. Changing it meant updating listings and signs. Moving it entirely to the API meant the owner or front-desk team could no longer open the app and write a quick personal reply.
WhatsApp Coexistence removes that choice. The existing number stays active in the WhatsApp Business app while the Cloud API connects it to software such as Visito.
It is a practical bridge for a business that wants automation without forcing the entire team to abandon the app on day one. It still has limits, and those limits matter before you connect a busy number.
What is WhatsApp Coexistence?
WhatsApp Coexistence is Meta's onboarding path for using an existing WhatsApp Business app number with the WhatsApp Business Platform, commonly called the Cloud API. The app and the connected platform can send and receive supported messages on the same customer-facing number.
A reply typed on the phone can be copied to the connected platform through a message echo. A reply sent by a person or AI agent through the API can appear in the Business app. That gives both sides a record of the supported one-to-one conversation.
Coexistence works with the WhatsApp Business app, not a personal WhatsApp account. It also depends on the provider implementing Meta's onboarding, synchronization, and webhook requirements correctly. Meta's Coexistence documentation describes the underlying requirements.
What do I need before connecting my number?
Start with the number that is already active in the WhatsApp Business app. Do not delete the account or register the number through a new-number flow first. Coexistence depends on the existing app account remaining active during setup.
Meta currently requires WhatsApp Business app version 2.24.17 or later. In practice, update the app before you begin rather than checking only the minimum version. You also need the phone in hand for the in-app confirmation and QR steps.
Before opening the connection flow, confirm the following:
- The number is active in the WhatsApp Business app, not personal WhatsApp.
- You can sign in with the Meta identity that controls the correct Business Portfolio.
- Your provider supports Coexistence through Meta's Embedded Signup flow.
- The phone has internet access and can receive the official in-app prompt.
- Your team has time to reconnect supported companion devices if Meta unlinks them during onboarding.
What happens to chats, contacts, and new messages?
Your existing chats remain in the WhatsApp Business app. During onboarding, Meta may let you share contacts and up to six months of eligible one-to-one message history with the connected platform. That history transfer is optional, and the provider must support it.
After activation, supported one-to-one messages can flow in both directions. When a customer writes to the number, the message can reach the Business app and Visito. If a staff member replies from the app, Meta can send an echo of that reply to Visito. Messages sent from Visito can also appear in the app.
This shared view is useful, although it does not create assignments or ownership rules inside the phone app. If a receptionist replies from the phone while an AI agent is preparing an answer, both sides need clear handoff rules to prevent duplicate responses.
The safest test is simple: message the business from another phone, confirm the incoming message appears in both places, reply once through Visito, then reply once from the Business app. Check that the customer receives only the intended response and that both replies appear in the conversation history.
Which features work with Coexistence?
Coexistence keeps the Business app available, but it does not turn every app feature into an API feature. The distinction is easiest to see in the table below.
Meta changes these capabilities over time. Check the official documentation and your provider's current implementation before relying on an app-only feature in an automated workflow.
| Feature | WhatsApp Business app | Connected platform | What to know |
|---|---|---|---|
| One-to-one messages | Available | Available | Supported messages can sync in both directions. |
| Contacts and old chats | Remain in the app | Optional import | Up to six months of eligible history may be shared during setup. |
| Group chats | Remain in the app | Not supported | Groups do not appear in the API inbox. |
| Voice and video calls | Remain in the app | Not supported | Calls are handled on the app side. |
| Broadcast lists | Existing lists become read-only | Not supported | New app broadcast lists cannot be created after onboarding. |
| Disappearing messages, view-once media, and live location | Disabled for one-to-one chats | Not supported | Plan around these restrictions before connecting. |
| Message editing and revoking | Supported | Supported by Meta | The provider still needs to implement the related events. |
| Linked devices | Supported devices can be relinked | Not applicable | Existing companion devices may be unlinked during setup. |
How do I set up WhatsApp Coexistence with Visito?
Visito supports the official Coexistence connection flow. The screens can change as Meta updates Embedded Signup, but the decisions remain the same: use the correct Meta identity, choose the existing Business app path, and finish the confirmation on the phone.
The setup usually follows these steps:
- In Visito, open Connections, choose Channels, and select Connect WhatsApp.
- Sign in to Meta with the identity that controls the intended Business Portfolio.
- Select or create the correct business assets when Meta asks.
- Choose Connect your existing WhatsApp Business App rather than the new-number option.
- Enter the phone number currently active in the Business app.
- Open the official prompt inside the WhatsApp Business app and complete the QR linking step.
- Choose whether to share eligible contacts and message history when Meta offers the option.
- Return to Visito, finish activation, assign the correct business, and verify that the channel can respond.
How do I verify the connection before going live?
Do not treat a successful Meta authorization screen as proof that the full message flow works. Test the number from the customer's side before allowing an AI agent or campaign to use it.
Run this short acceptance test:
- Send a new message from a different phone and confirm it appears in the Business app and Visito.
- Reply manually from Visito and confirm the customer receives it and the reply appears in the app.
- Reply from the Business app and confirm the message is visible in Visito.
- Trigger one approved AI response and check that the customer receives only one answer.
- Reconnect any companion devices your team needs and repeat the incoming-message test.
What should I check if Coexistence remains pending?
A pending connection usually means the phone-side confirmation, QR step, or final activation callback did not finish. Creating another channel while the first one is pending can make the problem harder to diagnose.
Work through these checks in order:
- Keep the phone online and open the WhatsApp Business app to look for an unfinished prompt.
- Confirm that the QR code was scanned from the intended Business app number.
- Check that you selected the correct Meta Business Portfolio and Visito workspace.
- Use Retry Activation from the existing Visito channel row after completing any missing app step.
- If messages arrive in only one place, contact support instead of deleting the Business app account or registering a duplicate channel.
How much does WhatsApp Coexistence cost?
Meta does not add a separate fee just for enabling Coexistence. Manual one-to-one messages sent directly from the WhatsApp Business app remain free. Messages sent through Visito use the Cloud API and follow Meta's current pricing rules. Your Visito plan is separate from Meta's delivery charges.
The Cloud API customer service window lasts 24 hours from the customer's latest message. During that window, the API can send free-form service replies. Once it closes, the business needs an approved template to write through the API.
A message sent from the Business app does not open, extend, or reset the API's 24-hour customer service window. A staff member may continue chatting from the phone while a later follow-up from Visito requires a template.
Meta is changing service-message pricing on October 1, 2026. Our WhatsApp Business API pricing guide explains the current allowances, message categories, and market-based rates. Use the official pricing page for the latest published rates.
The operational rule is straightforward: decide which replies should come from the free app, which should come through Visito, and who owns the conversation when both are active. That matters more than the Coexistence switch itself.
Should I use Coexistence or move fully to the API?
Choose Coexistence when the phone app still has a real job. A hotel owner may want to answer a VIP guest personally. A clinic receptionist may need to start a quick conversation from the phone. Visito can handle routine questions and after-hours coverage while those habits continue.
A full API setup is cleaner when every conversation should be assigned, measured, and handled inside one shared system. It reduces the chance that someone replies from the phone without the rest of the team understanding who owns the conversation.
The right choice depends on how your team works today:
| Question | Choose Coexistence | Choose a full API setup |
|---|---|---|
| Does the team still need the phone app? | Yes, regularly | No, the shared inbox can replace it |
| Do staff start manual conversations from the phone? | Yes | Rarely or never |
| Must every conversation have one clear owner? | Helpful, but not essential | Essential |
| Are groups and app-side calls part of daily work? | Yes | No |
| Is centralized reporting more important than app access? | No | Yes |
Is WhatsApp Coexistence a good fit for my business?
Coexistence is a strong fit for a small or midsize business that already has an established WhatsApp number, wants automation, and still needs occasional access to the phone app.
It is less useful when the app has become a source of confusion. If staff regularly answer the same customer from different places, or management needs reliable assignment and reporting, moving the operation into one inbox may be the better decision.
The feature is also less valuable when you are starting with a brand-new number. In that case, there is no existing app workflow or history to preserve, so a standard API connection may be simpler.
Visito can connect an eligible existing number, answer customers with an AI agent, and hand conversations to your team across web, iOS, and Android. Read our WhatsApp AI agent guide, review the detailed Visito Coexistence setup, see how Visito works on WhatsApp, or use the Visito API for custom workflows. When you are ready to test it with your business, start with Visito for free.
