About Dualhook

What Dualhook is, where it fits in the WhatsApp ecosystem, and how it works.

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.

Where Dualhook Fits

Dualhook is a privacy-first coexistence configuration layer for teams that use both the WhatsApp Business App and Cloud API. It is not a message transport layer and not a shared inbox.

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, and BLOCKED
  • 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

Responsibility Split

AreaOwner
Message transport and delivery pricingMeta
Coexistence configuration and operational dashboardingDualhook
Webhook endpoint logic, message storage, business workflowsCustomer 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.
  • Dualhook receives only 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

Related

  • Quick StartSet up Dualhook and connect your first WhatsApp Business Account in minutes.
  • Webhook OverrideHow Dualhook uses Meta's Webhook Override to route message webhooks directly to your server.
  • WhatsApp CoexistenceHow Coexistence mode works: using WhatsApp Business App and Cloud API on the same number.
Browse more docsGet started with Dualhook