WhatsApp Cloud API for Business: Bulk Client Updates That Actually Arrive

Bulk WhatsApp works if you respect templates, opt-in and rate limits. What we learned wiring the Meta Cloud API into a real client communication system.

WhatsApp Cloud API for Business: Bulk Client Updates That Actually Arrive

Email open rates for routine client updates are dismal. WhatsApp is where those messages actually get read, which is why every business we work with eventually asks the same thing: can we send this to four hundred clients at once?

Yes — through the WhatsApp Cloud API from Meta. But the rules are stricter than people expect, and breaking them does not produce an error message. It produces a quietly throttled number.

You cannot send whatever you like

Outside a 24-hour window after a customer messages you, every message must use a pre-approved template. You submit the wording to Meta, it gets reviewed, and only then can you send it with variables filled in.

This shapes the whole feature. Bulk messaging is not a text box — it is a set of approved templates plus a recipient list plus the values that vary. Design it that way from the start or you will rebuild it.

Opt-in is the part that protects the number

Users can report a business message as spam from inside WhatsApp, and enough reports lower your quality rating, which lowers your sending limit. The defence is unglamorous:

  • Record how and when each contact opted in, and store it against the contact.
  • Honour opt-outs immediately and permanently, in the same system that sends.
  • Send things people asked for. Reminders and statements are welcome; unsolicited offers are what gets reported.

Bulk means queued, not looped

Meta rate-limits per number, and your send tier grows with your quality rating rather than your ambitions. A loop over four hundred contacts will fail partway and leave you with no idea who received what.

Queue the sends, persist a per-recipient status, and process the queue with retries and backoff. Then a partial failure is a report you can act on, not a mystery. Delivery and read receipts arrive later by webhook, so the status has to be a field you can update — not a log line.

What this looked like in practice

For Dek N Tax we built bulk WhatsApp messaging into a client management system that also handles Excel bulk import and role-based admin access. The messaging is the visible half; the client records, the opt-in state and the send history underneath it are what make it safe to use. It is listed on our projects page.

Before you start

You will need a Meta Business account, a verified business, a dedicated phone number that is not already on the WhatsApp app, and templates written before development rather than after. That approval queue is the slowest part of the project and the easiest to leave too late.

Tell us what you want to send and to how many people and we will tell you what the setup involves.

← Back to Blog

Have something like this in mind?

Tell us what you are trying to fix and we will tell you what it takes.

Start a project