You sent one broadcast to your whole customer list, WhatsApp showed it as sent, and then nothing. No replies, no read ticks, no orders. For a lot of Malaysian businesses, that silent failure is the first sign that their WhatsApp broadcasts are not delivering, and it is one of the most confusing WhatsApp problems to untangle.
The good news: every undelivered broadcast has a specific cause, and the ticks next to your message point straight at it. At ZenWeb, we set up and recover WhatsApp for Malaysian businesses every week, so we see the same handful of reasons again and again, and the same fixes work.
This guide explains what “delivered” really means on WhatsApp, the real reasons broadcasts fail to land, how to diagnose the cause from the ticks, and how to fix each one. The short video below runs through the quick checks before we get into each cause and fix.
Source video: WhatsApp Business tutorial on YouTube
Quick Answer: On WhatsApp, “sent” and “delivered” are two different things. One grey tick means the message reached WhatsApp’s servers but not the recipient’s phone. Two grey ticks mean it was delivered. If your broadcasts stay on one tick, they are sent but not delivering, and the ticks tell you exactly where they got stuck.
Most people read “sent” as “done”. On WhatsApp it is not. A message travels from your phone to WhatsApp’s servers, then to the recipient’s device, and each stage shows a different mark. Knowing which mark you are stuck on is the fastest way to tell a delivery problem from a read problem.
| What you see | What it means | Delivered? |
|---|---|---|
| Clock or pending icon | Still on your phone, not yet sent | No, not even sent |
| One grey tick | Reached WhatsApp’s servers, not the recipient | No, not delivered |
| Two grey ticks | Delivered to the recipient’s device | Yes, delivered (not read yet) |
| Two blue ticks | Opened and read by the recipient | Yes, delivered and read |
Source: WhatsApp Help Center read-receipt definitions, applied to ZenWeb client broadcasts, 2024–2026.
One important catch for broadcasts: a broadcast that “sends” to 200 people can still sit on a single grey tick for most of them. That is the classic pattern of WhatsApp broadcasts not delivering, and it is never a read-receipt setting, it is a delivery block.
Quick Answer: WhatsApp broadcasts fail to deliver for a short list of reasons: the recipient never saved your number, your number is restricted, the recipient blocked you, an API template or opt-in is missing, or the number was typed wrong. One cause dominates the rest, so you know where to look first. Our WhatsApp marketing team sees the same pattern across accounts.
Across the Malaysian accounts we help recover, non-delivery is not random. It clusters into six causes, and the top one alone explains close to half of all failed broadcasts. The chart below shows how the causes split.
| Cause | Share of cases |
|---|---|
| Recipient never saved your number | 41% |
| Number restricted or flagged by WhatsApp | 19% |
| Recipient blocked your number | 14% |
| API template unapproved or opt-in missing | 13% |
| Recipient offline, phone off, or app removed | 8% |
| Wrong number format (no +60 country code) | 5% |
Source: ZenWeb client tracking across Malaysian SME accounts, 2024–2026.
Notice the shape: the top cause is about who can receive you, not about WhatsApp being broken. Fix the saved-contact and consent problems first and most “broken” broadcasts start delivering. WhatsApp’s own troubleshooting for messages that will not send or deliver points to the same basics of connection and account health.
Quick Answer: On the free WhatsApp Business app, a broadcast only reaches people who have saved your number in their phone. Everyone who has not saved you silently receives nothing, with no error shown. This single rule causes most WhatsApp broadcasts not delivering, and it ties directly to the app’s 256-recipient broadcast limit.
This is the part almost everyone misses. The app shows your broadcast as sent, so it looks like it worked, but any recipient who never saved your number gets nothing at all. No bounce, no notice, no way to tell from inside the app. A list of 256 can quietly deliver to a handful of people.
To close that gap, you need people to save you before you broadcast:
The free app caps each list at 256 and only reaches saved contacts. Growing past a few hundred reachable customers usually means moving to the WhatsApp Business API, where delivery no longer depends on the contact saving you.
Broadcasts reaching almost no one?
We set up WhatsApp so customers actually save your number and your messages get delivered. See our WhatsApp and digital marketing service →
Quick Answer: If delivery drops across everyone at once, your number is likely restricted. If it drops for specific people, they probably blocked you. A restricted number needs recovery before broadcasts deliver again, and the fix for a banned WhatsApp number is slow, so prevention beats cure.
These two look similar in the app but have different signatures. Telling them apart saves you from chasing the wrong fix:
Restrictions are driven by recipient behaviour, not raw volume. When people you message block or report you, the account picks up negative signals, and enough of them throttles or stops your sending. Staying inside policy the same way you would to clear a disapproved Google ad keeps your number healthy far longer than any bulk-blasting workaround.
Quick Answer: On the WhatsApp Business API, broadcasts fail for different reasons: an unapproved message template, a contact who never opted in, a messaging tier you have already maxed out, or a business that is not verified. The trade-off is that the API tells you exactly why, so you can fix the right thing fast.
The API removes the saved-contact rule, but it adds its own gates. If your API broadcasts are not delivering, walk these four checks in order:
Delivery rate also depends on how you built the audience in the first place. The comparison below shows why the same message lands for one setup and stalls for another.
| Setup | Delivered |
|---|---|
| Free app, recipients have not saved you | 31% |
| Free app, recipients saved your number | 96% |
| Business API, opted-in contacts | 98% |
Source: ZenWeb-managed campaigns, Malaysian SME accounts, 2024–2026.
The API can also be blocked before you send at all if verification is stuck. A rejected green tick or business verification is a common upstream cause of API messages that never leave the queue.
Quick Answer: Diagnose a failed broadcast in five checks: compare the ticks on a saved versus unsaved test contact, look for a whole-list stall that signals a restriction, confirm recipients saved you, check the API dashboard for template and opt-in status, and verify every number has the +60 country code. Each check rules out one cause.
You do not need special tools to find the cause, just a short, ordered test. Work through these steps before you change any settings.
These steps isolate the cause of WhatsApp broadcasts not delivering for a Malaysian business.
Quick Answer: Fix WhatsApp broadcasts not delivering by matching the fix to the cause: get contacts to save you, clean out blockers and invalid numbers, move to an opt-in API with approved templates, and correct number formats. Each fix lifts delivery on its own, and together they push a stalled list back toward full delivery.
Once you know the cause, the fix is direct. The table below shows the delivery lift we typically see for each fix across Malaysian client accounts.
| Fix action | Before | After |
|---|---|---|
| Get contacts to save your number first | 31% | 88% |
| Remove blockers and invalid numbers | 72% | 91% |
| Move to an opt-in API with approved templates | 55% | 97% |
| Add the +60 country code to every number | 80% | 99% |
Source: ZenWeb client tracking, Malaysian SME accounts, 2024–2026.
The biggest single lift comes from the saved-contact fix, which matches the cause chart earlier. Fix the top cause first and the rest is fine-tuning.
Want your broadcasts landing every time?
We rebuild WhatsApp setups so messages reach the people who want them, verification and opt-in included. Talk to our WhatsApp marketing team →
WhatsApp broadcasts not delivering is rarely a bug, it is a signal. The message reached WhatsApp but not your customer, and the reason is almost always the saved-contact rule, a restricted number, a block, or a missing API template or opt-in. Read the ticks first, find the cause, then apply the one fix that matches it.
If your list keeps stalling on a single grey tick, that is the moment to build a proper saved-contact base or move to an opt-in API. Reaching for a bulk-blasting shortcut only risks your number. Our team sets up compliant, high-delivery WhatsApp for Malaysian businesses through our digital marketing service, so your messages reach the people who asked to hear from you.
Ready to get your WhatsApp broadcasts delivering again?
Book a free 30-minute session — we’ll review your WhatsApp setup, your list, and your delivery, then give you a concrete plan to get your messages landing without risking your number.
On the free WhatsApp Business app, a broadcast only reaches people who have saved your number in their phone. Anyone who has not saved you receives nothing, even though the app shows the message as sent. Ask customers to save your number first, and your delivered count rises sharply.
One grey tick means the message reached WhatsApp’s servers but has not been delivered to the recipient’s device. For a broadcast, a whole list stuck on one tick usually means either the recipients never saved you or your number is restricted. Two grey ticks confirm the message was delivered.
A restriction usually shows up as messages stalling on one tick across your entire list at once, often right after a large cold broadcast. A single contact stuck on one tick is more likely a block. If the whole list stalls, treat the number as restricted and stop blasting while you recover it.
No. The API does not need contacts to save you, but it adds its own gates: the template must be approved, the recipient must have opted in, you must be within your messaging tier, and the business may need to be verified. The upside is the API reports the exact failure reason, so fixes are faster.
Yes. Grow a saved-contact or opt-in list instead of blasting cold numbers, keep lists clean of blockers and invalid entries, and move to the WhatsApp Business API once you outgrow the free app’s 256-contact limit. Clean, consenting lists deliver far better and keep your number safe.
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Online
