WhatsApp Business API Integration: What Businesses Should Know

Imagine a multi-branch coaching institute wanting to send fee-due reminders, batch-timing changes, and answer parent queries across its centres. That's a legitimate use case: transactional and support messaging to people who already have a relationship with the business. What it isn't for is buying a phone number list and sending an unsolicited promotional blast, which is exactly the kind of use that gets accounts flagged.

The distinction Meta draws is consent, not message content alone. A reminder to a parent who enrolled their child is a service message; the same reminder sent to a number scraped from a public directory is not, regardless of how useful the content might be.

Setting up API access means going through Meta's business verification and connecting through a Meta Business Partner or directly via the Cloud API, and any message sent outside an existing 24-hour conversation window has to use a pre-approved message template — free text can only be sent as a reply within that window, not to initiate contact.

Meta's onboarding, verification and template-review requirements have changed multiple times over the past few years, so the current process should be checked directly against Meta's own developer documentation at the time of setup rather than assumed from an earlier project or a vendor's outdated guide.

Meta requires businesses to obtain a person's opt-in before messaging them, and — as of Meta's own current policy — that opt-in does not need to specifically mention WhatsApp; a general marketing or service-communication consent collected through any channel is acceptable as long as it clearly states the business's name and that the person is agreeing to receive communication, and it still has to satisfy applicable local law (developers.facebook.com, checked 2026-09-08).

Beyond the bare minimum, it's worth letting customers choose categories — order updates versus promotional offers, for instance — and giving a clear way to opt out of each category, which reduces the chance of a customer blocking the business entirely over one unwanted message type. Any automated flow also needs a defined point where a real person picks up the conversation, for the queries a bot or template genuinely can't resolve.

Since 1 July 2025, Meta has charged for the WhatsApp Business Platform on a per-message basis rather than the older per-conversation model — a business is billed when a template message is delivered, with rates that vary by destination country and message category (marketing, utility, or authentication), and non-template replies sent within the 24-hour customer service window remain free (developers.facebook.com, checked 2026-09-08).

On top of Meta's own per-message rate, a Business Solution Provider — the company actually giving you API access and tooling — typically adds its own markup or subscription fee, so the real per-message cost a business pays is Meta's rate plus that provider's fee, and both should be confirmed directly from the specific provider's current published pricing before budgeting, since Meta has signalled further pricing changes through 2026.

Once live, a business's WhatsApp number carries a quality rating that Meta tracks based on block rates and complaint volume, and a number that drops too low can be restricted in how many people it's allowed to message per day, or lose access altogether. This makes ongoing monitoring, not just the initial setup, part of running the integration.

Delivery failures — a template rejected for a formatting change, a number that's opted out being messaged anyway — should be visible in a dashboard someone checks regularly, the same way any other integration's exception queue would be, rather than only being discovered when a customer complains.