Dualhook vs. DIY Coexistence Setup

WhatsApp Coexistence lets you use the WhatsApp Mobile App and Cloud API on the same number. Setting it up yourself is possible, but it requires significant engineering effort and ongoing maintenance.

Create and configure a Meta App

DIY: You need to create a Meta App, configure Login for Business, set up Embedded Signup permissions, and pass Meta's App Review. This process typically takes days to weeks depending on review cycles.

Dualhook: Click connect, complete the OAuth flow in a popup, and Dualhook automatically exchanges the token, discovers your WABA and phone number, and configures everything in a single atomic operation. Setup takes about five minutes.

Implement Embedded Signup

DIY: You must integrate the Facebook JavaScript SDK, handle the OAuth popup, capture the authorization code, exchange it for an access token on your server, and extract the waba_id and phone_number_id from the session response. Edge cases like missing IDs require fallback discovery through the Graph API.

Dualhook: Embedded Signup is built in. Token exchange, WABA discovery, and phone number extraction happen automatically during the connection flow.

Configure Webhook Override

DIY: After signup, you must call the subscribed_appsendpoint with your customer's webhook URL and verify token to activate the Webhook Override. A mistake here means messages go to the wrong server or are lost entirely.

Dualhook: The Webhook Override is configured automatically during the Embedded Signup flow. No manual API calls required.

Handle token refresh

DIY: Access tokens expire. You need to track issuance and expiry timestamps, implement automatic refresh logic, and handle token invalidation gracefully. A lapsed token silently breaks your entire integration.

Dualhook: Dualhook tracks token issuance and expiry, surfaces warnings before tokens expire, and handles error states with clear dashboard indicators.

Build a template management UI

DIY: Message templates require a submission interface, approval status tracking, media header uploads via resumable upload sessions, and variable management. This is a full product feature, not a simple API call.

Dualhook: Create, edit, and monitor message templates directly from the dashboard. Upload media headers for IMAGE, VIDEO, and DOCUMENT types via integrated upload sessions. Track approval status and category assignments.

Monitor the heartbeat

DIY: Coexistence requires opening the WhatsApp Business mobile app at least once every 13 days to keep the Coexistence link active. Miss this window and Cloud API webhook delivery may stop silently. Because you don't see message content on Dualhook's side, app-open activity can't be tracked automatically — you have to build the reminder UX yourself.

Dualhook: A safety-net layer for the 13-day app-open requirement: dashboard badges showing days remaining, email reminders via Resend, and a one-click acknowledgment button to log check-ins so you can prove the app was opened in time.

Health, quality, and webhook monitoring

DIY: You need to build custom monitoring infrastructure for phone number health, quality ratings, and webhook delivery tracking.

Dualhook: Real-time phone number status, quality rating checks, and webhook delivery logs are available out of the box. No custom monitoring infrastructure required.

When Dualhook is not the right fit

Dualhook may not be worth it if you enjoy full control over every integration detail and don't mind maintaining Embedded Signup, token refresh, Webhook Override, heartbeat tracking, and monitoring infrastructure yourself. If your team has dedicated engineering bandwidth to build and maintain the plumbing long-term, or you only need a single number with no operational dashboard and raw API calls are enough, the DIY route can work well.

Looking specifically at raw Meta Cloud API without any platform? See Meta Direct vs. Dualhook.