WhatsApp Coexistence: Use the Business App and API Together

What does coexistence cost?

Messages sent from the Business app remain free, and messages sent through the API follow Meta's per-message pricing by category and market. Meta also states that a customer service window opens only when a WhatsApp user messages the business after onboarding, and app messages do not open or affect API windows or pricing.

Rates and rules change, so we do not print them here. Use Meta's pricing documentation, our WhatsApp pricing by country and the pricing calculator.

Coexistence or full migration: which should you choose?

Choose coexistence if you want to keep the app as your main working tool while adding automation. Choose a full migration if you have many agents, large volumes or need features the app cannot offer.

Our articles on API vs Business app, choosing a business phone number and migrating a number between providers cover the full-migration side. The number rules for a new setup are in how to set up the API.

Who is coexistence for, and who should skip it?

Coexistence fits a business that already has an active Business app number and customers who know it, and wants to add automation without a hard switch. Typical cases are clinics, salons, small shops and consultancies with a few staff answering on phones.

It is a poor fit when you need any of the following:

• High-volume campaigns. The fixed 20 messages per second ceiling applies to the number.
• Many agents with roles. The app allows a limited set of linked devices, while a shared inbox gives assignment, tagging and reporting. See shared inbox for WhatsApp, Instagram and email.
• Group chats or calls on the same number. They are not supported on the API side.
• A provider that cannot receive app-sent message events. Without them, the inbox shows only half of each conversation.

What should you check before onboarding?

Run through this list with your provider before you start. It takes ten minutes and avoids a failed attempt.

1. Is the number on the WhatsApp Business app, not the standard app?
2. Is the app updated to at least the version Meta currently requires?
3. Is the phone active and used regularly, so inactivity does not disconnect it?
4. Does the provider support coexistence and the app-sent message events?
5. Do you accept that broadcast lists become read-only and group chats are not synchronised?
6. Have you decided whether to share chat history, and who will see it in the provider inbox?
7. Is the Facebook account of the admin who will approve the signup available?
8. Are opt-ins recorded for the contacts you will message by template?

If any answer is no, fix it first or consider a new number for the API. The API readiness checklist covers the documents Meta may request for business verification.

How do you leave coexistence?

You disconnect the account from the phone. Meta documents Settings, Account, Business Platform, Disconnect Account as the route, and says the Deregister API cannot be used for numbers in use with both the app and the API.

A disconnect can also happen without you choosing it. Meta lists inactivity reasons: the primary phone inactive for about 14 days, or a companion device inactive for about 30 days. Open the app regularly if you rely on coexistence.

Worked example: a Kuwait City dental clinic

"Salmiya Smiles" (synthetic) has two receptionists on one WhatsApp Business app number. They want automatic appointment reminders and a booking assistant, but the receptionists like answering on the phone.

• The clinic asks its provider whether the number can onboard through coexistence and confirms the app is on a supported version.
• It agrees to share six months of history so staff can see earlier chats in the provider inbox.
• Reminders go out as approved utility templates through the API; replies reach the receptionists in the app and in the inbox.
• They rebuild their quick replies as saved templates and stop using broadcast lists, which are now read-only.
• Six months later, with four receptionists and a second branch, they plan a full migration to a shared inbox.

What are the common mistakes?

• Assuming every number is eligible. Eligibility depends on the app version and on your provider's setup. Ask first.
• Missing the 24-hour sync window. Start the history sync straight after onboarding.
• Letting the phone go idle. Prolonged inactivity can disconnect the number.
• Forgetting consent. Sending templates through the API needs opt-in. See opt-in and consent.
• Expecting bulk speed. The 20 messages per second ceiling is fixed.

How OmniChannels.ai helps

BroadNet is an official Meta Business Solution Provider, and we onboard WhatsApp numbers through Meta's Embedded Signup. Whether your number can connect with coexistence depends on its eligibility, so ask our team whether it can onboard this way. If not, we help you migrate the number fully to the API or register a new one, including business verification and display name requests, and give you the Omni Inbox for agents. Approval decisions stay with Meta. Book a demo to check your number.