How many people can a WhatsApp broadcast reach?
PingPlug · Updated
A broadcast list in the WhatsApp or WhatsApp Business app holds up to 256 contacts, and only those who have saved your number receive what you send to it. On the WhatsApp Business Platform neither restriction exists. What bounds you there is your messaging limit: how many distinct people you may open a conversation with in a rolling 24 hours, a figure Meta raises or lowers based on your quality rating and how you send.
What the 256 figure is, and what it is not
It is the capacity of a single broadcast list, not a daily allowance. Nothing stops you creating several lists.
Which is also why it is rarely the limit that matters. Splitting 800 contacts across four lists is trivial; getting the message to all 800 is not, because the saved-contact rule applies to every one of them.
The rule that actually reduces your reach
A recipient who has not saved your number receives nothing at all. The send reports no failure, so the gap is invisible from the sending side.
For a business this reverses the usual assumption. Your newest customers — the ones least likely to have stored your number — are precisely the ones a broadcast list misses.
What replaces the cap on the Business Platform
There is no list size and no saved-contact condition. Instead every number carries a messaging limit, which counts the distinct people you may open a conversation with in a rolling 24 hours.
It behaves nothing like the 256 cap: it is a daily allowance rather than the size of a saved list, it applies across everything you send from that number, and Meta moves it up or down on its own. How the tiers work, and why sending harder is not how you climb them, is set out on the messaging limits page.
A reply to somebody who wrote to you first is not an opened conversation and does not draw on it.
Throughput is a separate constraint
How many people you may start conversations with and how fast the API accepts messages are different ceilings. A list well inside your messaging limit can still take time to go out.
This matters for anything time-sensitive. A flash offer sent to a large list arrives over a span, not at an instant.
PingPlug reads your messaging limit and quality rating from Meta rather than asking you to track them, and a broadcast that Meta stops accepting — a paused template, or a restriction on the account — halts after the batch in progress instead of spending the rest of the list on failures.