Delivery Reports Missing: How to Get Full Status Back
Why WhatsApp, SMS, or email delivery status disappears — and how to restore full visibility.
You send a batch of messages, check back an hour later, and half of them show no status at all — not "delivered," not "failed," just blank. Delivery reports missing almost always comes down to where the status is generated versus where WaSMS is reading it from — the gateway, the carrier, or the channel's own status feed. Understanding that path is the fastest way to find the gap and close it.
What Delivery Reports Include
A full delivery report has up to four stages depending on channel: Sent (left WaSMS), Delivered (reached the device or inbox), Read (opened, WhatsApp only), and Failed (with a reason code). SMS and email typically stop at Delivered — read tracking isn't standard on those channels, so don't expect the same visibility you get on WhatsApp.
Where Reports Come From
WaSMS doesn't generate delivery status itself — it relays what the underlying channel reports back. For WhatsApp, that's your own paired number and gateway. For SMS, it's the Android phone acting as the gateway. For email, it's Brevo's delivery webhook. If any of those three stop reporting back, the report column in WaSMS goes blank rather than showing a false status.
A blank status is not the same as "failed." It means WaSMS hasn't received a status update yet — the message may have gone through fine.
Why Delivery Reports Go Missing
Three things cause the majority of gaps we see:
- Gateway offline — if the phone running the SMS gateway app lost connection, or the WhatsApp-paired device went offline, no further status updates come in until it reconnects. See gateway offline troubleshooting.
- Carrier doesn't send DLRs — some carriers, especially on SMS, don't return delivery receipts at all, even when the message arrived. This isn't a WaSMS limitation; it's a carrier-level choice.
- Bulk sending outpaced status processing — on very large bulk sends, status updates can lag a few minutes behind the send before catching up.
Restoring Full Reporting
Start with the gateway: open Channels and confirm both your WhatsApp and SMS gateways show "Connected," not "Idle" or "Offline." A reconnect usually backfills any status updates that were queued upstream. If a specific carrier consistently shows blanks for SMS, that's expected — check with that carrier's own reporting if you need certainty on a specific message. For email, check your email deliverability basics — Brevo's own dashboard has more granular bounce and spam-complaint detail than the summarized view inside WaSMS.
Reading the Report Screen
Each row in Reports shows the last status WaSMS received, with a timestamp. Hover over a status to see the reason code where one exists — a failed SMS often includes "invalid number" or "carrier rejected." If you're building your own dashboards, the same data is available through the API rather than just the UI, useful if you're running SMS marketing at scale and want your own tracking alongside WaSMS.