WhatsApp Coexistence without message-storing middleware
Dualhook helps teams use the WhatsApp Business App and the WhatsApp Cloud API on the same number through WhatsApp Coexistence.
It is built for companies that want API access, direct infrastructure control, and a privacy-first WhatsApp architecture without adding another shared inbox or message-storing middleware layer.
Dualhook is not another WhatsApp inbox. It is the control layer that lets Meta send WhatsApp webhooks straight to your own infrastructure.
What makes Dualhook different
Most WhatsApp tools sit between Meta and your team as an inbox, proxy, or CRM layer.
Dualhook takes a different approach.
Meta sends message-path webhooks directly to your own endpoint via Webhook Override. Dualhook handles the operational setup around that connection, but does not store or proxy WhatsApp message content.
That means:
• no Dualhook inbox
• no message-body storage by Dualhook
• no message proxying by Dualhook
• direct Meta-to-your-server webhook routing
• more control over your WhatsApp infrastructure
Built for WhatsApp Coexistence
Dualhook is especially useful for teams that want to keep using the WhatsApp Business App while also connecting the same number to the Cloud API.
This lets teams keep the familiar mobile app workflow while building custom automations, integrations, and backend processes on top of the WhatsApp API.
What Dualhook helps with
• WhatsApp Business App + Cloud API Coexistence
• Embedded Signup setup
• Webhook Override configuration
• direct webhook routing to your endpoint
• template management
• phone number health monitoring
• Coexistence heartbeat monitoring
• operational logs and metadata
• privacy-first WhatsApp API operations
Who it is for
Dualhook is built for developers, agencies, SaaS teams, and privacy-conscious companies that want more control over their WhatsApp stack.
It is a good fit if you want the WhatsApp API without handing your message flow to a third-party inbox or middleware provider.
SaaS platforms
For SaaS products onboarding many customer WhatsApp accounts, Dualhook Platform adds a multi-tenant onboarding API, co-branded Embedded Signup, tenant mapping, and signed lifecycle event webhooks.
This lets your customers connect WhatsApp from inside your own product while message webhooks still route directly to the configured endpoint.
Privacy-first by design
Dualhook stores the operational data needed to manage the connection, such as account identifiers, webhook configuration, template metadata, and health state.
It does not store WhatsApp message bodies or media.
The goal is simple: help teams run WhatsApp Business API infrastructure with less middleware, cleaner routing, and better privacy boundaries.
