How to Connect WhatsApp Business to Converge

Converge connects to WhatsApp through Meta's Cloud API, using Meta's Embedded Signup flow. You do not host a WhatsApp Business API server, and you do not have to build anything in Meta Business Suite in advance.

You do not need an existing WhatsApp Business account

This is the most common misconception, and following it wastes an afternoon. Embedded Signup creates the missing pieces while you are inside it. Meta's documentation lists what the flow can do: select an existing business portfolio or create a new one, select an existing WhatsApp Business account (WABA) or create a new one, enter and verify a business phone number, and set the display name customers see in place of the number (Meta, Embedded Signup). If you already have a WABA, you pick it from a list instead.

What you actually need

• A Facebook account with admin access to the business portfolio you want to use, or permission to create one.
• A phone number that can receive an SMS or a voice call and is not currently active on WhatsApp or the WhatsApp Business app.
• A payment method you can attach to the WhatsApp Business account afterwards. Meta requires businesses onboarded by a Tech Provider to add one before they can send messages.

Do not install the WhatsApp Business app for this

Older guides tell you to download the WhatsApp Business app first. For Converge that advice backfires. A number already in use with the WhatsApp Business app can only be onboarded through Meta's customized "coexistence" flow (featureType: whatsapp_business_app_onboarding), which Converge's connect button does not use — it runs Meta's default flow. If the number is live in either WhatsApp app, registration fails and you have to remove it before you can continue.

Nearly every failed WhatsApp connection traces back to the phone number still belonging to something else. Clear it before you open the connect flow, not after.

Remove the number from WhatsApp and WhatsApp Business

If the number is signed in on the consumer WhatsApp app or the WhatsApp Business app, open that app on the phone holding the number and go to Settings → Account → Delete my account. Wait a few minutes before returning to Converge, because Meta needs time to release the number. Skip this and Converge tells you exactly what happened: "This phone number is linked to an existing WhatsApp account. Please disconnect it first, wait 3 minutes, and try again." Meta sometimes wraps the same cause in a vaguer "Invalid parameter" or "Cannot create certificate" message, translated into whatever language your Facebook account uses.

Two-step verification

Two-step verification is a 6-digit PIN that Meta requires when a business phone number is registered for Cloud API use (Meta, Two-Step Verification). Converge generates a PIN and registers the number for you during the connect flow, so you never type one in. If the number already carries a PIN from a previous provider, Converge detects the mismatch and skips registration rather than failing the whole connection.

Meta's documentation states there is no endpoint to disable two-step verification once it is set. The only remedy is to change the PIN in WhatsApp Manager under your phone number → Settings → Two-step verification → Change PIN. If the number is still on the consumer WhatsApp app, turn two-step verification off there before you delete that account.

In Converge, open Settings → Platforms and click WhatsApp. You get two buttons, and they behave differently.

Connect WhatsApp Business (the main button)

This opens Meta's Embedded Signup in a pop-up window, not a full-page redirect. Converge loads Facebook's JavaScript SDK to launch it, so a pop-up blocker or an ad blocker stops the flow before it starts — Converge reports "Facebook SDK failed to load. Check if an ad blocker is preventing it." Allow pop-ups for the Converge app domain, pause the blocker, and retry.

Inside the window Meta asks you to authenticate, accept the Cloud API, WhatsApp Business and Meta Business Tool terms, choose or create a business portfolio and WhatsApp Business account, add and verify the phone number, and pick a display name. Converge requests two permissions: whatsapp_business_management for account settings and message templates, and whatsapp_business_messaging for phone number settings and for sending and receiving messages.

Connect via Meta (the alternative button)

The second button opens Meta's hosted onboarding page on business.facebook.com in a new tab, then Converge polls in the background and updates the screen on its own when the account appears. Use it when a browser extension or a corporate policy blocks the pop-up flow. Only one hosted connection can run at a time across the platform, so if another business is mid-setup you get "Another connection is in progress. Please try again in a few minutes." The attempt times out after 10 minutes, and there is a Cancel button if you change your mind.

Embedded Signup hands back your WhatsApp Business account ID, your business phone number ID and a one-time code. Converge then runs four server-side steps before the connection shows as live:

1. Exchanges the code for a business access token scoped to your account.
2. Reads the display phone number so the connection can be labeled with it.
3. Subscribes to webhooks on your WhatsApp Business account, which is what makes incoming messages arrive.
4. Registers the phone number for Cloud API use with a generated 6-digit PIN.

Webhook subscription happens during that call, not on a delay. If messages are not arriving afterwards, something is genuinely wrong and waiting will not fix it — see WhatsApp connection issues.

One WhatsApp Business account, one Converge company

Converge refuses to attach a WABA that another Converge company already holds, and says so: "This WhatsApp Business account is already connected to another company." The other company has to disconnect first, or you use a separate WhatsApp Business account with its own phone number.

Add a payment method — there is a hard deadline

Meta requires businesses onboarded by a Tech Provider to add a payment method to their WhatsApp Business account before they can send messages. That has become urgent. From October 1, 2026 Meta charges per message for service messages — the free-form replies you send inside the 24-hour window — and it has said it will stop delivering service messages for any business without a payment method on file by September 30, 2026 (Meta, pricing updates for service and utility messages). Add the card in Meta's Billing Hub or WhatsApp Manager as soon as the connection is live.

Ask a colleague to message your business number from their own WhatsApp. The message should land in your Converge inbox within a few seconds, carrying the sender's WhatsApp profile name, and your reply should reach them in the WhatsApp app.

The Connection Health panel

Once WhatsApp is connected, Settings → Platforms → WhatsApp shows a Connection Health row. Opening it queries Meta live and reports the phone status (you want CONNECTED), the display-name review status (you want APPROVED), whether the business is verified, when the access token expires, and any issues Meta is flagging. Re-checks are rate limited, so the button shows a countdown instead of letting you hammer it.

"Another provider is still connected"

If you previously used another WhatsApp Business Solution Provider — Twilio, 360dialog, Brevo, MessageBird — that provider can still be subscribed to your WhatsApp Business account, and Meta then refuses your sends with Error 200 even though the token and permissions look healthy. Converge detects this and shows a red panel naming the other apps. Fix it in Meta Business Settings: select your WhatsApp Business Account, open the Partners tab, remove the old provider, then confirm a payment method is configured in WhatsApp Manager.