Documentation

Sign up with an email address and a password. 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 you work inside a supported CRM you can install the app there instead, and the workspace is created for you as part of the install.

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 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.

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.

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.

• Our workspace needs no wiring: invite the people who answer the number. What that includes.
• A supported CRM is installed from its own marketplace and then binds the number to a channel. Registrations re-assert themselves, because a CRM can delete a registered step on an app update. How the Bitrix24 connector works.
• Your own software uses a scoped API key and a webhook endpoint. The API and webhooks.

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.