You completed Meta's Embedded Signup and may even see Dualhook in the WhatsApp Business app, but no connection appears in the Dualhook dashboard. This usually means Meta completed its side of the link but the final browser handoff did not return to the original Dualhook tab.
What Happened
Embedded Signup has two sides:
- Meta links the WhatsApp Business Account and grants Dualhook access inside its popup.
- The popup sends the selected WABA and phone IDs plus a one-time authorization result back to the original Dualhook tab.
Dualhook can create the dashboard connection only after the second step reaches it. Popup restrictions, privacy extensions, Brave Shields, blocked cookies, an in-app browser, or closing the original tab can interrupt that return even though Meta already shows the partner link.
Dualhook records only operational signup signals. It never stores the one-time OAuth code in the recovery ledger. If a launched attempt remains unfinished, the Connections page may show a Your WhatsApp connection may need one more try banner.
Retry in a Clean Browser
- Use desktop Chrome or Firefox in a normal window or a fresh browser profile.
- Allow popups and cookies for
dualhook.com,facebook.com, andweb.facebook.com. - Temporarily disable ad blockers, content blockers, privacy extensions, and Brave Shields.
- Do not start from an in-app browser inside WhatsApp, Instagram, an email app, or another mobile app.
- Keep the original Dualhook tab open while completing the Meta popup and the WhatsApp Business app confirmation.
- Return to the original tab and wait for Dualhook's finalizing screen to finish.
If the dashboard recovery banner is visible, use Retry connection there. If Meta instead shows a numbered error, check the Embedded Signup error index.
What Not to Delete
Do not delete the phone number, WABA, Meta Business Portfolio, or WhatsApp Business account just because the Dualhook connection is missing. Do not deregister the number or reinstall WhatsApp Business as a first troubleshooting step. Those actions solve a different class of problem and can affect service or message history.
If Meta says the account is already shared with another partner, follow the dedicated error #2655093 guide instead.
Billing and Retrying
Retrying Embedded Signup does not send a WhatsApp message, so it does not create a Meta messaging charge. Meta bills eligible delivered messages; Dualhook billing is a separate subscription described on the Pricing page.
A failed browser return with no Dualhook connection row does not create an additional metered Dualhook connection. If the connection already appears in the dashboard, use that connection instead of starting another signup.
When to Contact Support
If two clean-browser attempts still do not produce a connection, contact us through the in-app support chat.
For the normal flow and server-side fallback discovery, see Embedded Signup. For webhook routing after connection, see Webhook Override and Troubleshooting.