WhatsApp Broadcast Not Delivering to Everyone? The Saved-Number Rule and the Real Limits

If half your list received the message and half did not, the cause is almost never technical. It is the rule most people never read.

The saved-number rule#

A broadcast list message is delivered only to recipients who have your number saved in their phone's contacts.

Everyone else is skipped. Silently. They get nothing, you get no error, and the message shows as sent on your side.

This is intentional: it stops broadcast lists being used to message strangers. It also means the effective reach of any broadcast list is not the size of the list, but the number of people who once bothered to save you.

For a consumer brand, that fraction is usually small. For a business whose customers saved the number to place orders, it can be most of the list. Either way, you should measure it rather than guess.

Verify it in two minutes#

1. Pick three recipients who did not receive the broadcast.
2. Ask them to check whether your number is in their contacts.
3. Have one of them save it, then send the broadcast again to a test list containing only those three.

If the person who saved you receives it and the other two do not, you have your answer, and nothing else needs debugging.

The other causes, ranked#

1. Blocks. A blocked contact receives nothing. Blocks accumulate quietly on numbers that send a lot of promotional content, and they also feed the quality signals that eventually restrict your number — see account banned or restricted.

2. List size ceiling. Broadcast lists have a maximum size in the app. Beyond it, you cannot add recipients. Teams work around this by splitting into several lists, which multiplies the manual work and the risk of duplicate sends.

3. Recipient unreachable. Phone off, no data, storage full, or the app not opened for a long time on a device with aggressive battery management. These usually resolve themselves and deliver late.

4. Rate limiting. Several large broadcasts in quick succession from a consumer or Business app account can be throttled. Sends slow down or stall; the fix is to stop, not to retry harder.

5. Number formatting. A contact saved locally without a country code may be unreachable from your account. Store every number in full international format — same rule as chat links.

6. Deleted or migrated accounts. Numbers that left WhatsApp, or moved to a business account elsewhere, quietly drop off.

Why the Business app cannot solve this for you#

The broadcast list is a consumer feature wearing a business hat. Three limits make it unsuitable the moment your list grows:

• Reach depends on whether strangers saved you.
• List sizes are capped and managed by hand.
• There is no delivery reporting: you cannot see who received it, only that you sent it.

You can work around the first by asking customers to save your number, which works about as well as it sounds.

What changes on the Business Platform#

Sending the same campaign as a template message through the WhatsApp Business Platform changes the rules:

The trade is explicit: you pay per message and submit content for review, and in exchange the message actually arrives and you can prove what happened to it.

A pre-send checklist for any list over a few hundred#

1. Confirm every recipient opted in, and that you can show when and how — opt-in done right.
2. Store numbers in international format, deduplicated.
3. Send to a small internal test segment first and confirm delivery states.
4. Stagger large sends rather than firing everything at once.
5. Include a clear opt-out instruction and honour it the same day.
6. Watch block and opt-out rates after every campaign. A rise there is the earliest warning you have.

If your broadcasts are reaching a fraction of the list, that is a structural limit, not a setting. Send campaigns that do not depend on saved contacts — with delivery, read and failure reporting per recipient.

Next: broadcasting at scale, and when to move to the API.