WhatsApp Coexistence for the WhatsApp Business App and Cloud API
WhatsApp Coexistence lets teams keep the WhatsApp Business App active while using Cloud API on the same number. Dualhook configures Webhook Override, monitors the 13-day heartbeat requirement, and routes message-path webhooks directly from Meta to your endpoint instead of using Dualhook as a message-storage layer.
WhatsApp Coexistence lets businesses use the WhatsApp Business App and Cloud API on the same phone number without giving up either channel.
What is WhatsApp Coexistence?
Most teams discover WhatsApp Coexistence when they want to keep their existing WhatsApp Business App workflow but also need API automation, backend webhooks, or template messaging. Without coexistence, that usually turns into a tradeoff between the app and the API.
Dualhook is built around that exact coexistence use case. It lets product teams, support teams, and operations teams keep the app while their systems receive Cloud API webhooks directly from Meta.
Why do teams use WhatsApp Coexistence?
- Keep the current business number and mobile workflow.
- Add automation, webhook processing, and API-based sending.
- Avoid moving message traffic through a BSP or shared inbox.
- Maintain a cleaner privacy boundary between Meta and your backend.
Eligibility and practical limits
- Coexistence is intended for numbers already active in the app.
- Some Meta verification and badge paths differ for coexistence numbers.
- The app still needs periodic activity to keep the coexistence link active.
- Regional availability and onboarding details can change with Meta policy.
How does Dualhook set up WhatsApp Coexistence?
Dualhook uses Meta's onboarding flow to connect the WhatsApp Business Account, discover the relevant IDs, and configure the webhook routing needed for coexistence. The key step is applying WhatsApp Webhook Override so message events go straight from Meta to your webhook instead of through Dualhook.
That setup keeps Dualhook out of the inbound message path while still giving you connection health, token visibility, template tooling, and monitoring in the dashboard.
How to use the WhatsApp Business App and Cloud API on the same number
Yes — you can run the WhatsApp Business App and the WhatsApp Cloud API on the same phone number. Dualhook handles Meta Embedded Signup, turns on WhatsApp Coexistence, and sets up Webhook Override so Meta delivers webhooks straight to your server through direct Meta routing.
- 1
Prepare your webhook before Meta Embedded Signup
Add your HTTPS webhook URL and verify token before Meta Embedded Signup begins. Your endpoint must return Meta's raw hub.challenge during the verification GET request. Dualhook uses these credentials to apply the WABA-level Webhook Override immediately after approval and before triggering any approved one-time chat-history or contact sync.
- Prerequisite
- An HTTPS endpoint that handles Meta's verification GET and webhook POSTs
- Time
- ≈1 minute
- You get
- Webhook credentials ready before Meta onboarding
Step 1 · Webhook credentials prepared before Embedded SignupTraditional BSPthe old wayMetaAppBSPproxyYour ServerwaitingSetting up…Dualhookthis is usMetaApp
Dualhookconfig onlyYour ServerwaitingSetting up… - 2
Approve WhatsApp Coexistence in Meta and WhatsApp
In Meta's popup, select your Business Portfolio, WhatsApp Business Account, and the number already registered in the WhatsApp Business App. Then approve the Business Platform connection on your phone and choose whether to share existing chat history. That history choice is a one-time onboarding decision; the Business App remains active after you connect.
- Prerequisite
- Access to the Meta Business Portfolio and the phone running WhatsApp Business
- Time
- ≈2–3 minutes
- You get
- Your existing number connected to Cloud API while the app stays active
Step 2 · WhatsApp Coexistence approved in Meta and the appTraditional BSPthe old wayMetaApp+Cloud APIBSPproxyYour ServerwaitingSetting up…Dualhookthis is usMetaApp+Cloud APIDualhookconfig onlyYour ServerwaitingSetting up… - 3
Receive message events directly from Meta
With the WABA-level Webhook Override active, Meta sends inbound messages, delivery and read statuses, message echoes, and any approved history or contact sync directly to your endpoint. Dualhook stays outside that message path. It handles operational signals such as template, quality, and account updates so the dashboard remains useful without storing conversation content.
- Prerequisite
- A verified webhook endpoint that returns successful POST responses
- Time
- Active when onboarding completes
- You get
- Direct Meta → your server delivery for customer-path events
Step 3 · Message events routed directly from MetaTraditional BSPthe old wayMetaApp+Cloud APIBSPproxyYour ServerwaitingRouted via BSP proxyDualhookthis is usMetaApp+Cloud APIDualhookconfig onlydirectYour ServerwaitingDirect webhook configured - 4
Keep the connection production-ready
Use Dualhook to test endpoint availability, manage templates and media, and monitor your number's messaging health and quality. For Coexistence, open the WhatsApp Business App at least once every 13 days; Dualhook provides countdowns, reminder emails, and confirmed check-ins as a safety net. Your team can keep handling conversations in the app while your backend runs Cloud API automation.
- Prerequisite
- Open the WhatsApp Business App at least once every 13 days
- Time
- Ongoing
- You get
- App + API operations without storing message content in Dualhook
Step 4 · Production-ready direct routingTraditional BSPthe old wayMetaApp+Cloud APIBSPstores + proxiesYour Servervia BSP1 message stored on BSPDualhookthis is usMetaApp+Cloud APIDualhookconfig onlydirectYour Serverdirect delivery0 messages stored on Dualhook
What is the 13-day heartbeat requirement?
WhatsApp Coexistence is not purely a one-time toggle. The app still needs to be opened periodically so the coexistence state remains healthy. Dualhook tracks that requirement, highlights the risk in the dashboard, and gives teams a clear place to manage it.
Frequently asked questions about WhatsApp Coexistence
What is WhatsApp Coexistence?
WhatsApp Coexistence is the setup that lets a business keep using the WhatsApp Business App while also running Cloud API on the same phone number.
Can I use the WhatsApp Business App and Cloud API on the same number?
Yes. That is the core purpose of WhatsApp Coexistence. Dualhook helps teams configure the required Webhook Override and operational monitoring around it.
What does Dualhook do in a WhatsApp Coexistence setup?
Dualhook configures the coexistence flow, applies Webhook Override so message events go directly from Meta to your endpoint, and tracks the 13-day heartbeat requirement.
Do messages hit Dualhook during coexistence?
With Dualhook, Meta routes message webhooks directly to your server. Dualhook stores only configuration and operational metadata.
Keep reading
Use the supporting docs and comparisons behind this WhatsApp Coexistence overview.
Coexistence documentation
Read the implementation details, eligibility notes, and limitations for WhatsApp Coexistence.
13-day heartbeat guide
See why the WhatsApp Business App still needs periodic app activity after coexistence is enabled.
Dualhook vs DIY setup
Compare manual coexistence implementation work against Dualhook's guided setup and monitoring.
Ready to set up WhatsApp Coexistence?
Start with Dualhook if you want the Business App, Cloud API, and direct routing without turning message storage into another project.