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 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. No BSP. No message proxy.
- 1
Connect your existing Business App number with Meta Embedded Signup
Launch Meta's official Embedded Signup flow from inside Dualhook. Choose your Facebook Business Portfolio, pick the phone number already running in the WhatsApp Business App, and approve WhatsApp permissions in one click. Dualhook links your WhatsApp Business Account automatically — no tokens to copy, no developer console detours.
- Prerequisite
- WhatsApp Business App v2.24.17+, a verified Meta Business Portfolio
- Time
- ≈60 seconds
- You get
- Your existing number linked to the WhatsApp Cloud API
Step 1 · Linking your existing number via Meta Embedded SignupTraditional BSPthe old wayMetaAppBSPproxyYour ServerwaitingSetting up…Dualhookthis is usMetaApp
Dualhookconfig onlyYour ServerwaitingSetting up… - 2
Enable WhatsApp Coexistence on the same phone number
Dualhook enables WhatsApp Coexistence on your number, so the WhatsApp Business App and the WhatsApp Cloud API run side-by-side on the same phone number. Your team keeps replying from the mobile app; your Cloud API sends templates, automations, and freeform replies. Meta requires the app to be used at least once every 13 days — Dualhook tracks this heartbeat and emails you 48 hours before it expires.
- Prerequisite
- An active Business App session on the number within the last 13 days
- Time
- ≈30 seconds
- You get
- One number on two platforms, zero downtime
Step 2 · WhatsApp Coexistence enabled — one number, two platformsTraditional BSPthe old wayMetaApp+Cloud APIBSPproxyYour ServerwaitingSetting up…Dualhookthis is usMetaApp+Cloud APIDualhookconfig onlyYour ServerwaitingSetting up… - 3
Set up Webhook Override so Meta sends webhooks to your server
Paste your server's webhook URL and verify token. Dualhook writes the Webhook Override on your phone number so Meta delivers inbound messages, message statuses, and template events straight to your server — bypassing Dualhook entirely. Validate inbound POSTs on your side by checking the WhatsApp envelope shape, your WABA ID, and your phone_number_id, and keep the override URL private and high-entropy.
- Prerequisite
- An HTTPS endpoint that responds 200 within 20 seconds
- Time
- ≈45 seconds
- You get
- Direct Meta → your server webhook delivery. Zero message storage on Dualhook.
Step 3 · Webhook route configuredTraditional BSPthe old wayMetaApp+Cloud APIBSPproxyYour ServerwaitingRouted via BSP proxyDualhookthis is usMetaApp+Cloud APIDualhookconfig onlydirectYour ServerwaitingDirect webhook configured - 4
Test your first incoming message and webhook delivery
Send a test WhatsApp message to your business number from any phone. Meta forwards the payload straight to your webhook URL; Dualhook never sees the message body. Your dashboard confirms delivery from Meta's signal alone — not the content. From here, your Cloud API sends templates and freeform replies inside the 24-hour session window, while the mobile app keeps working exactly as before.
- Prerequisite
- A live webhook handler
- Time
- live
- You get
- Production-ready WhatsApp Cloud API + Coexistence on the same number
Step 4 · First message deliveredTraditional 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.