WhatsApp Solutions Overview
WhatsApp has multiple products that serve different use cases.
WhatsApp Messenger
The consumer app for personal communication between individuals. It is not intended for business operations at scale.
WhatsApp Business App
The business app for small teams that need business profiles, quick replies, labels, and basic workflows. With Coexistence enabled, this app can be used alongside Cloud API on the same number.
WhatsApp Business Platform (Cloud API)
The API platform for programmatic messaging at scale. It is used by product teams, automation systems, and integrations that need webhook-driven workflows.
Meta also offers a separate Marketing Messages API (MM API) for WhatsApp layered on top of the platform, with its own performance optimizations and conversion-tracking endpoints. Dualhook focuses on Cloud API; MM API send paths are not part of Dualhook's managed surface.
Where Dualhook Fits
Dualhook is a privacy-first WhatsApp operations platform for teams using Cloud API and Coexistence. It provides direct webhook routing, template management, health monitoring, and operational tooling without acting as a shared inbox or storing message content.
Dualhook configures and monitors coexistence so your number can keep mobile app usage while your backend receives API webhooks directly from Meta.
- You keep your own Meta Business assets (WABA, phone numbers, app access).
- Meta sends message webhooks directly to your endpoint via Webhook Override.
- Dualhook handles setup and management metadata — not message content.
- Dualhook billing is separate from Meta messaging charges.
Core Capabilities
Connection and Onboarding
- Embedded Signup support for connection setup
- WABA and phone number ID discovery
- Guided webhook URL and verify token configuration
Webhook Routing
- Webhook Override configuration for direct Meta-to-customer endpoint message delivery
- Webhook testing and delivery monitoring
- Management-event visibility in the Dualhook dashboard
Template and Number Operations
- Template sync, create, edit, duplicate, and delete
- Health signals such as
AVAILABLE,LIMITED, andBLOCKED - Heartbeat reminders for the 13-day coexistence requirement
Compliance and Privacy
- No message proxying and no message content storage
- Operational metadata retention controls (7, 30, or 90 days)
- CSV export for webhook operational logs
Getting Help from Dualhook
Dualhook includes an in-app support chat inside the dashboard so teams can ask questions, report bugs, and follow up without leaving the product.
- Open the support bubble in the dashboard to start a conversation.
- Use it for onboarding issues, webhook routing questions, billing questions, and bug reports.
- Attach screenshots or PDFs when the issue is easier to explain visually.
For the full workflow, see Support, Contact, and Bug Reports. For privacy or legal requests, use the contact path described in the Privacy Policy.
Responsibility Split
| Area | Owner |
|---|---|
| Message transport and delivery pricing | Meta |
| Coexistence configuration and operational dashboarding | Dualhook |
| Webhook endpoint logic, message storage, business workflows | Customer system |
Webhooks in Practice
Webhooks are the backbone of WhatsApp Cloud API operations. Inbound messages and delivery statuses are sent asynchronously from Meta.
In a Dualhook setup:
- Message events go directly to your webhook endpoint in standard override setups.
- Dualhook primarily handles management events required for dashboard and health visibility.
For details, see Webhook Events & Notifications.
What Dualhook Is Not
- Not a BSP-style message proxy
- Not a billing intermediary for Meta message charges
- Not a conversation archive for message bodies or media
- Not a replacement for your backend message processor