Sending to a list without destroying your number
The number of recipients is not what puts a number at risk. The proportion of them who block you is. That single sentence should decide how you segment, what you send, and whether you send at all.
The arithmetic nobody does
Suppose two businesses each send to a list. One sends to 5,000 customers who bought last month; two hundred of them block it. The other sends to 500 numbers from a bought list; two hundred of them block it. Identical complaint counts, wildly different outcomes - one is a four percent block rate on a warm list, the other is forty percent from a number with no history.
This is why "how many can I send" is the wrong question and "who am I sending to" is the right one.
What the app's broadcast lists actually do
The WhatsApp Business app has broadcast lists capped at 256, and they carry a rule people forget: a broadcast reaches only people who have your number saved in their contacts. Sending to 256 and having 60 receive it is not a bug, and it is the reason app broadcasts feel unreliable.
That contact-saved rule is also a crude consent filter, and removing it - which is what moving to an API does - removes a safety rail you may not have noticed you had.
Segmenting so a bad send cannot take everything
- Split by relationship, not by size. Bought in the last 90 days, bought once a year ago, never bought. These have completely different block rates and should not share a send.
- Separate transactional and promotional numbers. If the promotional number is lost, order updates keep working. If they share a number, one bad campaign takes out your receipts.
- Send to a small slice first. A few hundred, then wait. Replies and opt-outs in the first hour predict the rest.
- Pace it. Not because a rate limit says so, but because a burst is a signature and because a staggered send gives you time to stop.
- Have a stop button, and test it. The moment you want it, you will want it immediately.
What to send
The messages that get blocked are the ones that are obviously about you rather than about the recipient. A specific, useful, short message to a segment that plausibly wants it will outperform a general offer to everybody on both response and complaints - and the second of those is what decides whether you get to do it again.
- Name the reason they are hearing from you: "you bought tyres from us in March".
- One thing to do, one link.
- The opt out, in the message, every time.
- A real name to reply to. Broadcasts that invite replies get fewer blocks, because the alternative to blocking is obvious.
The uncomfortable conclusion
If your list is large and cold, there is no safe way to message it on WhatsApp. The channel's whole value is that it is where people talk to people they know, and that value is exactly what the abuse systems protect. A cold list is an email problem, and treating it as a WhatsApp problem is how businesses lose the number their real customers use.
Questions people actually ask
How many people can I message at once on WhatsApp?
The app's broadcast lists cap at 256 recipients and only deliver to people who have your number saved. Through an API there is no such cap, which makes the limit behavioural rather than technical - and behavioural limits are the dangerous kind.
Do broadcast messages look different to the recipient?
No. A broadcast arrives as an ordinary one to one message, which is exactly why it works and exactly why abusing it is treated so harshly.
Njiwa
One inbox for WhatsApp, Facebook and Instagram, and an API that sends over either WhatsApp rail. 7 days free, no card.