Before you start, get these three things ready
Almost every setup that stalls, stalls on paperwork rather than on code. Have these in hand before you open Meta Business Manager and the rest of the process is mechanical.
- A registered business name and address that match your incorporation documents exactly.
- A phone number that is not currently active on the WhatsApp consumer app or WhatsApp Business app. Migrating an in-use number is possible, but it has to be deleted from the app first.
- Access to that number for a one-time verification code, by SMS or voice call.
Step 1 — Create and verify your Meta Business Account
Business verification is Meta reviewing that your company is real. You upload an incorporation certificate, a utility bill or a bank statement showing the business name and address, and wait. Review usually takes a few working days.
The single most common rejection is a mismatch between the name on your document and the name typed into the form. An abbreviation, a missing 'Pvt Ltd', a different address line — any of these sends you back to the start of the queue. Copy the document exactly.
Step 2 — Add a WhatsApp Business Account and register your number
Inside your verified Business Account, add the WhatsApp product and register your phone number. Meta issues a phone number ID and an access token. Those two values, plus a webhook verify token you choose yourself, are everything a platform needs to send and receive on your behalf.
Treat the access token like a password. In Waboxa it is encrypted before it is stored and is never returned to the browser — not in an API response and not in the settings form you typed it into. Any platform that shows it back to you in plain text is storing it in plain text.
Step 3 — Point the webhook at your platform
Meta delivers inbound messages and delivery receipts by calling a URL you nominate. Two things matter here. The first is that the endpoint answers Meta's verification challenge with the token you configured. The second is that it answers fast — Meta gives a webhook a few seconds and treats anything slower as a failed delivery, which it then retries.
That retry behaviour is why serious implementations acknowledge the delivery immediately and do the real work behind it. If a platform runs an AI model call inline on the webhook request, a slow model turns into a duplicate reply in front of your customer.
Waboxa also verifies the X-Hub-Signature-256 header on every inbound call, so a request that did not come from Meta is refused rather than processed.
Step 4 — Submit your first template
You cannot message a customer out of the blue with free text. Business-initiated conversations start from a template that Meta has reviewed. Utility templates — order confirmations, delivery updates, OTPs — are usually approved quickly. Marketing templates take longer and are held to a higher bar.
Write the template in clear language, put every variable in context rather than stranding a bare {{1}} at the start of a line, and give a genuine opt-out route. Templates that read like they were built to dodge the review are the ones that get rejected.
Once a template is approved, you can broadcast to contacts who opted in. From there, every reply lands in the inbox as an ordinary conversation, and the 24-hour service window opens for free-text replies.
What to check once you are live
Send yourself a message from a second phone and confirm three things: the contact was created automatically, the message appears in the inbox, and the delivery ticks progress from sent to delivered to read. If all three work, the wiring is correct and everything after this is configuration rather than plumbing.