ChatBridge24

SETUP, END TO END

Documentation

Everything between creating an account and sending your first approved template, in the order it actually happens — including the three steps that are decided by Meta rather than by us.

Read this once before you start. Three of the steps below are Meta’s decisions rather than ours — verifying a number, approving a display name and approving a template — and knowing which three stops a wait looking like a fault. If you would rather watch it done first, book a live demo.

1 · Create a workspace

An account at app.chatbridge24.com. No CRM required to get this far.

Sign up at app.chatbridge24.com with an email address, a password and your WhatsApp number. Signing in takes a second step: a code sent on WhatsApp, or one from an authenticator app. A workspace holds your connected numbers, your colleagues and your subscription; a colleague is invited with a role rather than a number of their own, because the subscription is per connected number and there is no seat charge to ration.

If your team works in Bitrix24, install the ChatBridge24 app from the Bitrix24 Marketplace instead. Your Bitrix24 portal is then the account, everyone signs in through Bitrix24, and the steps below happen inside the app.

2 · Connect a WhatsApp Business number

Through Meta’s own flow, on your own business portfolio.

01

Have the number ready

It must be a number you control that can receive an SMS or a voice call, and it must not be active in the WhatsApp or WhatsApp Business app. A WhatsApp Business app number you want to keep on the phone connects with “Add Business App number” instead — see WhatsApp coexistence. A number already live with another provider is a migration rather than a new connection — see step 3.

02

Run Meta’s sign-up flow

Meta’s own sign-up page opens. You sign in with the Facebook account that owns (or will own) the business portfolio, and you pick or create the WhatsApp Business Account the number will live on. The account and the number stay yours throughout.

03

Finish it in the app

If the number still needs registering we ask for the six-digit two-step PIN. If the number has never been verified, we ask Meta to text or call it and you type the code. Both steps are shown as what they are rather than as a generic error.

3 · If the number is already with another provider

It is a migration, and two things must be true first.

Turn off two-step verification at the current provider, then run the same connect flow choosing the destination account. The display name, the quality rating, the messaging limits and the high-quality approved templates travel with the number.

One precondition is easy to miss: if the current provider stores your messages in a particular region, that setting travels too and has to be set on the destination before the number can be registered. We read Meta’s own refusal, set the region it names and try once more — so the usual symptom is a short delay rather than a dead end.

4 · Get the display name approved

Meta reviews the name your customers will see. We do not.

The display name is reviewed against Meta’s own policy and the result is a state on the number: approved, under review, or rejected with a reason. A number can send while the name is still under review.

Two states are routinely misread. A code verification that reads as expired is normal on a number that was verified a while ago — it describes the one-time code, not the number. And business verification is not the blue tick: the tick is a separate, rarer grant, and this product only ever shows one where Meta itself shows one.

5 · Get a template approved

Required for anything outside the free-text window.

Build the template in the app, submit it, and watch the review. Approval is Meta’s and usually arrives in minutes, though it can take longer. A rejected template comes back with Meta’s own reason attached.

One mechanism is worth understanding before you build a template with a picture in its header: the file you upload at build time and the file identifier used at send time are two different objects at Meta, and the second cannot be derived from the first. That is why we keep the bytes you uploaded — and why a template built outside this app can still be sent, because we adopt the sample Meta itself approved.

6 · Wire it to where your team works

Our inbox, your CRM, your own software — or more than one.

  • Our workspace needs no wiring: invite the people who answer the number. What that includes: the standalone WhatsApp workspace.
  • Bitrix24: install the ChatBridge24 app from the Bitrix24 Marketplace, and bind the number to an Open Channel if your team works in Open Channels. Everything the app registers in your portal is checked and restored automatically, including after an update. How the Bitrix24 WhatsApp integration works.
  • Any other CRM, or your own software, uses a scoped API key and a webhook endpoint: new messages arrive as signed webhooks and, on the Enterprise plan, approved templates go out through the WhatsApp REST API. Step by step: WhatsApp for any CRM.

7 · Call the API

One key, one endpoint of yours, one required header.

The API and the webhooks serve numbers connected to the WhatsApp Business API. Keys, the read routes and the webhooks are part of every plan for those numbers; sending approved templates through the API is part of the Enterprise plan.

Create a key in the app, give it only the scopes it needs, and store it as a secret — it is shown once and kept as a hash, so it cannot be read back out of our database by anybody.

Every send requires an idempotency key. That is not a convention here, it is enforced: a send without one is refused, because a retried send is a real message to a real person and a real charge. Register a webhook endpoint for inbound messages and delivery state, and verify the signature over the raw body before you parse it.

Questions that come up during setup

How long does the whole thing take?
The parts we control are minutes. The parts Meta controls — verifying the number, approving the display name, approving the first template — are the ones that set the pace, and each is shown as a state on the number rather than as a spinner.
Can I use a number that is in the WhatsApp app on somebody’s phone?
Not if it is a personal WhatsApp account: it has to be deleted from the app first, or you connect a different number. A number on the WhatsApp Business app can stay on the phone and be connected through coexistence, with “Add Business App number”.
Do I need a Facebook Page?
You need a Meta business portfolio, which Meta’s sign-up flow will create if you do not have one. The portfolio and the WhatsApp Business Account stay yours.
What happens to my messages if we stop paying?
A number stops sending when its subscription ends. Your data is deleted automatically within thirty days of closing the workspace or uninstalling the app from Bitrix24. How deletion works.

Reference

WhatsApp REST API and webhooks

Keys, scopes, the required idempotency key and the webhook queue.

WhatsApp Business API, explained

What the official transport is and what it is not.

WhatsApp data protection

Where everything is stored, who can reach it, and for how long.

From the blog

Further reading on this subject.

Templates approved first time

The three categories and the rejection reasons that cost the most time.

WhatsApp CRM integration for any CRM

Webhooks, the REST API and the lead source a customer arrives with.