Your WhatsApp broadcast isn't delivering mainly because recipients haven't saved your number as a contact, and WhatsApp silently drops broadcast messages to anyone who has not saved you.
- Recipients haven't saved your number as a contact (the #1 silent reason broadcasts don't deliver).
- You've hit the 256-recipient-per-list cap and the rest never receive it.
- Your number is being spam-throttled or temporarily restricted for bulk sending.
- You're using a group, or confusing a broadcast with a group, instead of a broadcast list.
- A new or "unwarmed" number, or business-account limits, are suppressing delivery.
- Recipients have blocked you, changed numbers, or left WhatsApp.
Here is the part that trips up almost everyone: most "whatsapp broadcast not delivering" cases are not really failures. They are silent under-deliveries. Your broadcast went out, WhatsApp reported no error, and it quietly reached a fraction of the list because most of those people never saved your number. You see a sent broadcast. They see nothing. Below is how to tell which of the six causes is yours, and how to fix it.
Why is my WhatsApp broadcast not delivering?
Your WhatsApp broadcast is not delivering because of one or more of six causes, and the biggest by far is the saved-contact rule: native broadcast lists only reach people who have your number in their phone. The other five are the 256 cap, spam throttling, group-versus-broadcast confusion, an unwarmed number, and recipients who blocked you or left.
Start by ruling in the likely culprit before you touch anything:
- You sent to a list of leads or new customers, not close contacts. Almost certainly the saved-contact rule. This is the default answer for "why is my whatsapp broadcast not working" when the recipients are people who do not already have you saved.
- Some people got it, others didn't, and you can't see a pattern. Also the saved-contact rule. The ones who received it had you saved; the silent ones did not.
- The list was large and delivery just stopped past a point. The 256-recipient cap, or spam throttling on a high-volume send.
- Nothing sent at all, or sends failed. A "whatsapp broadcast not sending" symptom points at account restrictions, a brand-new number, or being blocked, not the saved-contact rule.
The rest of this guide takes each cause in order, starting with the one behind roughly the majority of complaints.
Do recipients need to save your number for a broadcast to deliver?
Yes. WhatsApp broadcast lists only deliver to recipients who have saved your number in their phone's address book. Anyone who has not saved you receives nothing, and WhatsApp shows you no error, no bounce, and no warning. This single rule is why a broadcast to 200 people can reach 30.
WhatsApp states it plainly in its Help Center. Per WhatsApp's broadcast lists FAQ, "only contacts who have added you to their phone's address book will receive your broadcast message." There is no way around this inside the native feature. It is not a setting you forgot to toggle. It is how broadcast lists are designed.
Think about what that means for a marketing list. Your newest leads, the people you most want to reach, are exactly the people least likely to have saved your business number. So the native broadcast tool works worst on the audience it should serve best. A loyal regular who saved your bakery two years ago gets every broadcast. The lead who messaged you once last week gets silence.
There is a second design fact worth knowing: broadcasts are one-way in feel but private in delivery. WhatsApp's FAQ notes that recipients "will receive the message as a normal message," and when they reply, "it will appear as a normal message" in your chats, and "their reply will not be sent to other recipients." So a broadcast is a batch of individual 1:1 messages, not a shared thread. Recipients never see each other. That privacy is good. The saved-contact tax is the price.
The quick test: send one broadcast to two of your own numbers, one that has you saved and one that does not. The saved number receives it. The unsaved number gets nothing. That five-minute test proves the rule on your own account before you blame anything else.
How many contacts can one WhatsApp broadcast reach?
A single WhatsApp broadcast list is capped at 256 recipients. Per WhatsApp's broadcast lists FAQ, "you can select up to 256 contacts in each Broadcast list." If your list is larger, everyone past 256 simply is not on it, so they never receive the message.
This article owns the troubleshooting angle, so I will not re-teach the limit here. If you want the full explainer on the cap and where it comes from, read our WhatsApp broadcast limit guide. And if you need to message more than 256 people, the workarounds (multiple lists, labels, and the trade-offs of each) are covered in how to broadcast to more than 256 contacts. Read those two for the "how many" and "how to go bigger." Back here, keep going for why even a within-cap broadcast under-delivers.
Is your number being throttled or flagged as spam?
WhatsApp can slow or restrict delivery from a number that looks like a spam source: rapid identical sends, a brand-new number with no history, or a spike in blocks and reports. When this happens, messages queue, land late, or stop, and the account can be temporarily restricted. Being honest about the numbers matters here, because there is a myth to clear up.
There is no official published daily limit for personal WhatsApp broadcast lists. WhatsApp does not put out a "whatsapp broadcast message limit per day" figure for regular accounts, so any specific per-day number you have seen quoted is someone's guess, not a documented rule. Do not plan around an invented ceiling. What actually governs throttling is behavior, not a counter:
- Velocity. Firing many broadcasts back to back, especially the exact same text, reads as automated spam.
- Reports and blocks. When recipients tap "block" or "report," WhatsApp's systems notice fast. A wave of these is the strongest signal that gets a number restricted.
- Cold sending. A number created yesterday that immediately blasts hundreds of messages has no trust history, so it gets scrutinized harder than an aged, well-used number.
The mechanics are reputational, not a fixed quota. Meta describes its enforcement in the WhatsApp Business Messaging Policy, which allows it to limit or remove access for accounts that send unsolicited or bulk messaging that people report. The takeaway: your delivery health is driven by how recipients react, not by hitting some secret number. Slow down, vary your content, and message people who actually want to hear from you, and throttling is rarely your problem.
WhatsApp broadcast vs group: which are you actually using?
A broadcast list sends private, individual 1:1 messages, requires the saved-contact rule, and recipients never see each other. A group is one shared thread where everyone sees every member and every reply, with no saved-contact requirement. Mixing these up is a common reason delivery behaves in a way you did not expect.
The "whatsapp broadcast vs group" confusion cuts both ways. If you think you set up a broadcast but actually created a group, everyone receives the message (no saved-contact rule) but they also see each other's numbers and can reply to the whole room, which is a privacy problem for a customer list. If you think you are in a group but actually built a broadcast list, delivery quietly collapses to only the people who saved you, and you wonder why half the room went dark. Here is the clean comparison:
| Broadcast list | Group | |
|---|---|---|
| Message delivery | Private 1:1 to each recipient | One shared thread |
| Saved-contact requirement | Yes, recipients must have saved you | No |
| Do recipients see each other | No | Yes, all numbers visible |
| Replies | Come to you as a normal 1:1 chat | Visible to the whole group |
| Max size | 256 per list | Large, but everyone is public to each other |
| Best use | One-way updates to people who saved you | Two-way community discussion |
The practical rule: use a broadcast list when you want private one-way updates and your recipients have you saved. Use a group when you want an open conversation and privacy between members is not a concern. If neither fits, that gap is exactly what the last section solves.
How to check whether your broadcast actually delivered
To check delivery, open the broadcast list, tap a sent message, and read the per-recipient delivery ticks in the message info; run the saved-versus-unsaved two-number test; and confirm no key recipient has blocked you. Native broadcasts give you very little delivery visibility, so these manual checks are the best you get.
Work through this in order:
- Open the broadcast list and tap the message. In the message info screen you can see which recipients show delivered (double gray tick) and read (double blue tick). Names with a single tick did not receive it, which usually means the saved-contact rule or a block.
- Run the two-number test. Send to one number that has you saved and one that does not. If only the saved one receives it, the saved-contact rule is your bottleneck, confirmed on your own account.
- Check for blocks. If a specific important contact never gets delivery, you may be blocked by them. Signs include your messages never moving past a single tick to that person and their profile photo or last-seen no longer updating.
- Watch for a hard stop past a point in a big list. If the first chunk delivered and the tail did not, suspect the 256 cap or throttling rather than the saved-contact rule.
The honest conclusion: the native tool tells you almost nothing at scale. Per-recipient ticks are fine for a list of 12. For a list of 250 you are squinting at a status screen with no export, no delivery report, and no way to see failures in aggregate. That visibility gap is the real cost of native broadcasting, and it is the setup for a better approach.
How to reach everyone reliably, even people who haven't saved your number
To reach people who have not saved your number at scale, you have two honest options: the WhatsApp Business API, or a tool like Blueticks that sends personalized individual messages from your own number. Both sidestep the native broadcast list's saved-contact limitation, but they work very differently, and neither is a license to spam.
Option 1: the WhatsApp Business API (Meta). This is Meta's official infrastructure for business messaging at scale. It reaches users who have not saved you, but it comes with real overhead: per-message conversation fees, opt-in requirements, and pre-approved message templates for anything promotional. It is powerful and fully sanctioned, and it is also a project to set up and a running cost that scales with volume. For many small businesses that is more machinery than they need.
Option 2: a tool like Blueticks. Blueticks sends personalized, individual WhatsApp messages from your own number. Because each message goes out as a normal 1:1 message rather than through a native broadcast list, it is not subject to the saved-contact rule that silently drops your unsaved leads. You also get per-recipient delivery tracking and automated follow-ups, so you finally see who received what instead of squinting at tick marks.
Be clear on the boundary, because it is a real one. Blueticks is not the WhatsApp Business API. It sends from your existing number over WhatsApp, with no per-message conversation fees and no template approval queue. But it does not exempt you from WhatsApp's rules. Consent and anti-spam responsibility stay with you, the sender. Message people who want to hear from you, honor opt-outs, and do not blast strangers. No tool, this one included, can promise guaranteed delivery or shield you from a restriction if recipients report you. Deliverability follows from sending wanted messages, not from the software.
For the full mechanics of sending to many contacts at once without tripping WhatsApp's limits, see our guide to sending bulk WhatsApp messages.
Take a realistic example. Novara Skincare had a list of 220 opted-in customers and kept broadcasting new-arrival alerts natively.1 Their message info showed delivery to only about 40 people, because the rest were newer buyers who had never saved the shop's number. Switching to personalized individual sends from their own number, to the same consented list, put the message in front of all 220 with a delivery record they could actually read. Same audience, same consent, roughly five times the reach, because the saved-contact tax was gone.
Broadcast reaching only a fraction of your list? Send from your own number to everyone, saved contact or not, with per-recipient delivery tracking and automated follow-ups. Start free with Blueticks campaigns →
FAQ
Why is my WhatsApp broadcast not working? The most common reason is the saved-contact rule: native broadcast lists only deliver to recipients who have added your number to their phone's address book, and WhatsApp shows you no error for the rest. Other causes are the 256-recipient cap, spam throttling on high-volume sends, and using a group instead of a broadcast list.
Why do only some people get my broadcast? Because only the recipients who saved your number receive it. Per WhatsApp's official FAQ, contacts who have not added you to their address book will not get your broadcast message, and you see no warning. The people who received it had you saved; the silent ones did not.
Is there a daily limit on WhatsApp broadcasts? There is no official published daily delivery limit for personal WhatsApp broadcast lists, so any specific per-day number you have seen is unverified. What actually triggers throttling is behavior: rapid identical sends, a brand-new unwarmed number, and a spike in blocks or reports. Send wanted messages at a reasonable pace and this rarely becomes an issue.
What's the difference between a broadcast and a group? A broadcast list sends private, individual 1:1 messages and requires recipients to have saved your number, and recipients never see each other. A group is one shared thread where everyone sees every member and reply, with no saved-contact requirement. Broadcasts are for one-way updates; groups are for open discussion.
How do I broadcast to people who haven't saved my number? Two honest options: the WhatsApp Business API, which reaches unsaved users but adds per-message fees, opt-in, and template approval, or a tool like Blueticks that sends personalized individual messages from your own number, which sidesteps the saved-contact rule without those API costs. Either way, consent and anti-spam responsibility remain yours as the sender.
Platform behavior in this article is grounded in WhatsApp's official Help Center: the broadcast lists FAQ for the saved-contact requirement, the 256-recipient cap, and reply behavior, and the WhatsApp Business Messaging Policy for enforcement. WhatsApp does not publish a per-day broadcast delivery limit for personal accounts; claims of a specific daily number are unverified. Verify current WhatsApp behavior at the linked sources before relying on it.
Footnotes
-
Novara Skincare is a synthetic example, and the reach figures (about 40 of 220 delivered natively, versus 220 with individual sends) are illustrative of the saved-contact effect, not a measured case study. The mechanism is real: unsaved recipients do not receive native broadcasts. The exact ratio for your list depends on how many of your contacts have saved you. ↩
