DualhookReady 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.
14-day free trial, cancel anytime.
16:05WhatsApp Coexistence
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, uses a 13-day safety reminder ahead of Meta's approximately 14-day inactivity window, and routes message-path webhooks directly from Meta to your endpoint instead of using Dualhook as a message-storage layer.
- No message storage
- Direct Meta webhooks
- Same number, app + API
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, including your own AI agent.
- 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.
- The OBA blue badge is not available for coexistence numbers; business verification works as usual.
- 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.
Onboarding runs entirely inside Meta's own popup and takes about five minutes. The Embedded Signup walkthrough shows every screen you will see, on desktop and in the WhatsApp Business app.
WhatsApp Coexistence · Setup guide · ~5 minutes
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.
- Step 01 · ≈1 minute
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 02 · ≈2–3 minutes
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 03 · Active when onboarding completes
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 04 · Ongoing
Keep the connection production-ready
Use Dualhook to test endpoint availability, manage templates and media, and monitor your number's messaging health and quality. Meta may disconnect Coexistence after approximately 14 days of primary-device inactivity; Dualhook warns at 13 days as a conservative safety margin and provides countdowns, reminder emails, and confirmed check-ins. Your team can keep handling conversations in the app while your backend runs Cloud API automation.
- Prerequisite
- Open the WhatsApp Business App regularly; Dualhook warns at 13 days
- Time
- Ongoing
- You get
- App + API operations without storing message content in Dualhook
What is the Coexistence inactivity requirement?
Meta may disconnect Coexistence after approximately 14 days of primary-device inactivity. Dualhook uses a 13-day reminder and confirmation timer as a conservative safety margin. The confirmation records your check-in; Meta does not expose live app-open activity to Dualhook.
Read about the heartbeat safety marginFrequently 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 uses a 13-day reminder threshold ahead of Meta's approximately 14-day primary-device inactivity window.
Do messages hit Dualhook during coexistence?
With Dualhook, Meta routes message webhooks directly to your server. Dualhook stores only configuration and operational metadata.
Guides & comparisons
Keep reading
Use the supporting docs and comparisons behind this WhatsApp Coexistence overview.
Today