Quick Start

Quick Start

Dualhook can be connected in a few minutes if your webhook endpoint is ready.

1. Create or select your organization in Dualhook.
2. Click New Connection.
3. Enter your connection name, HTTPS webhook URL, and webhook verify token.
4. Complete Meta Embedded Signup.
5. Run the Test Ping to confirm Meta can reach your endpoint.
6. Send a real test message and verify inbound + status webhooks arrive at your server.

That is everything. Messages now flow directly from Meta to your server. Management events (template updates, quality changes, account alerts) are handled by Dualhook so you can monitor them from the dashboard.

Organization and Connection Model

All data in Dualhook is organization-scoped. A connection binds your Meta IDs and webhook settings together:

• waba_id — your WhatsApp Business Account
• phone_number_id — the specific sending number
• webhook_url — where Meta delivers message webhooks
• webhook_verify_token — used by Meta to verify your endpoint

Prerequisites

Before connecting, make sure you have:

• An active Meta Business Portfolio and WABA
• A phone number eligible for your coexistence or API setup
• A public HTTPS webhook endpoint
• A verify token (we recommend a long random value, at least 16 characters)

Dualhook validates that the webhook URL uses HTTPS and that the verify token is at least 16 characters.

Test Ping

Dualhook includes a synthetic webhook connectivity test. When you click Test Ping, Dualhook sends a payload like this to your endpoint:

{
  "event": "dualhook.test_ping",
  "source": "dualhook.com",
  "timestamp": "2026-02-28T12:00:00Z",
  "organization_id": "<ORG_ID>",
  "connection_id": "<CONNECTION_ID>",
  "message": "This is a test payload from Dualhook. Your webhook is working!"
}

Headers included with the test:

• X-Dualhook-Event: test_ping
• X-Dualhook-Timestamp: <ISO_TIMESTAMP>

Go-Live Checklist

Before production traffic:

1. Confirm webhook override is active for your connection.
2. Confirm webhook verification and inbound webhook POST payload validation are working.
3. Confirm your receiver returns a fast HTTP 200 and processes asynchronously.
4. Confirm idempotency and retry handling for duplicates and timeouts.
5. Confirm heartbeat owner and operating routine are assigned.

Support and Escalation

If setup stalls or a production readiness check fails, use the in-app support chat in the Dualhook dashboard.

Include the connection name, failing step, expected result, actual result, and any relevant screenshots. For webhook issues, it also helps to mention whether the problem is verification, override routing, or downstream processing.

Use Support, Contact, and Bug Reports for the recommended reporting format.