---
title: "Sent vs Delivered vs Read vs Failed: Message Status Explained"
description: "What sent, delivered, read and failed mean on WhatsApp, SMS and email, why messages fail, how to fix them, and how to report campaign delivery correctly."
canonical: "https://omnichannels.ai/blog/message-delivery-status-explained/"
language: "en"
updated: "2026-10-09"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "marketing"
primaryQuery: "message delivery status sent delivered read failed"
keywords: ["whatsapp message status", "sms delivery report", "whatsapp failed message reasons", "email bounce types", "campaign delivery rate", "read rate whatsapp", "delivery receipt meaning"]
published: "2026-10-09"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 8
answer: "Sent means the platform accepted and dispatched the message; delivered means it reached the device or mailbox; read means the recipient opened it, where the channel reports that; failed means it could not be sent or delivered. WhatsApp reports all four, SMS usually reports delivery but not reads, and email reports bounces and estimated opens. Report each stage separately, using delivered messages as the base for engagement rates."
takeaways: ["On WhatsApp, Meta defines sent as one checkmark, delivered as two, read as two blue checkmarks and failed as a red error triangle.", "Read receipts can be switched off by WhatsApp users, so read counts understate real reading.", "SMS delivery receipts come from operators and confirm handset delivery, not reading.", "Email open tracking is affected by privacy features that preload images, so opens are an estimate.", "Compute engagement rates on delivered messages, and report failures by reason code, not as one number."]
faq: 
  - q: "Why is a WhatsApp message stuck on sent and never delivered?"
    a: "A single checkmark usually means the recipient's phone has not connected to WhatsApp since the message was sent, for example because it is off, offline or roaming without data. Messages can also stay undelivered if the number is no longer active on WhatsApp. Wait for the delivery window, then retry through another channel such as SMS for time-critical messages."
  - q: "Can a message be read without being marked delivered?"
    a: "On WhatsApp, a message must be delivered before it can be read, but Meta notes that if the user reads it immediately, you may receive a read status without a separate delivered status. Reporting should therefore count read messages as delivered too, otherwise your delivered total will look lower than reality."
  - q: "Do SMS messages have read receipts?"
    a: "Standard SMS does not provide read receipts to the sender. Operators return delivery receipts that confirm whether the message reached the handset or failed, with a status or error code. Engagement on SMS is measured through replies, link clicks with tracked URLs, or downstream actions such as bookings or payments."
  - q: "What is the difference between a hard and a soft email bounce?"
    a: "A hard bounce is a permanent failure such as a non-existent address or domain; remove that address. A soft bounce is temporary, such as a full mailbox or a receiving server deferring mail; retry later and suppress the address if it keeps failing. Mailbox providers watch how senders handle bounces as part of reputation."
  - q: "Should I report open rate or read rate to management?"
    a: "Report them, but label them as indicators rather than exact counts. WhatsApp read rates exclude users who disabled read receipts, and email open rates can be inflated by privacy features that load images automatically. Pair them with clicks, replies, conversions or revenue so decisions do not rest on a single soft metric."
sources: 
  - title: "Status messages webhook reference — Meta for Developers"
    url: "https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks/reference/messages/status"
  - title: "WhatsApp Cloud API error codes — Meta for Developers"
    url: "https://developers.facebook.com/docs/whatsapp/cloud-api/support/error-codes"
  - title: "Email sender guidelines — Gmail Help"
    url: "https://support.google.com/mail/answer/81126"
  - title: "RFC 3464: An extensible message format for delivery status notifications — IETF"
    url: "https://datatracker.ietf.org/doc/html/rfc3464"
---

# Sent vs Delivered vs Read vs Failed: Message Status Explained

Canonical: https://omnichannels.ai/blog/message-delivery-status-explained/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for marketing and CX managers who need to read delivery reports correctly and explain campaign results without overstating them. You will learn what each status means on WhatsApp, SMS and email, the most common failure reasons and their fixes, and a reporting structure that holds up when finance or leadership asks questions.

## What do sent, delivered, read and failed mean?

They are stages in a message's journey: accepted and dispatched, arrived at the device or mailbox, opened by the recipient, or stopped with an error. Not every channel reports every stage, and each stage is reported by a different system.

Meta's WhatsApp status reference defines them precisely:

- **Sent:** WhatsApp's servers sent the message (one checkmark).
- **Delivered:** the message reached the user's device (two checkmarks).
- **Read:** the message was displayed in an open chat on the device (two blue checkmarks).
- **Failed:** the message could not be sent or delivered (red error triangle).

Meta also lists a **played** status for voice messages. A message must be delivered before it is read, but if the user reads it immediately you may only receive the read status.

## How do status receipts differ by channel?

WhatsApp gives the richest receipts, SMS confirms handset delivery, and email confirms acceptance by the receiving server and estimates opens. Compare like with like.

| Status | WhatsApp | SMS | Email |
|---|---|---|---|
| Sent / submitted | Accepted and sent by WhatsApp servers | Accepted by the provider and submitted to the operator | Accepted by your sending server |
| Delivered | Reached the device | Operator delivery receipt confirms handset delivery | Receiving server accepted the message (it may still land in spam) |
| Read / opened | Read receipt, unless the user disabled read receipts | Not available | Estimated via tracking pixel; affected by image preloading and privacy features |
| Failed | Error code returned by Meta | Operator or provider error (invalid number, absent subscriber, blocked) | Hard or soft bounce, often with a status code defined by RFC 3464 |
| Engagement beyond read | Button clicks, replies | Replies, tracked link clicks | Clicks, replies, unsubscribes |

Two practical consequences follow. First, an email marked delivered is not proof of inbox placement. Second, a WhatsApp read rate is a floor, not a ceiling, because people who disabled read receipts can read without reporting it.

## Why do messages fail, and how do you fix them?

Most failures fall into four groups: the recipient cannot receive, the message breaks a platform rule, the account has a setup or billing problem, or you are sending too much too fast. Each group has a different fix, which is why you should report failures by reason.

### Common WhatsApp failures

Meta publishes error codes for the Cloud API. The ones campaign teams meet most often include:

| Error code | Meta's description (summarised) | What to do |
|---|---|---|
| 131026 | Message undeliverable; the number may not be on WhatsApp, the user may not have accepted latest terms, or the app is outdated | Reach the contact on another channel; do not keep retrying |
| 131047 | More than 24 hours since the recipient last replied | Send an approved template instead of a free-form message |
| 131049 | Not delivered to maintain healthy ecosystem engagement, possibly a marketing limit | Wait at least 24 hours before retrying that template; review targeting and frequency |
| 131050 | Recipient chose to stop receiving marketing messages from your business | Treat as an opt-out; do not retry |
| 132001 | Template does not exist in that language or is not approved | Check template name, language code and approval status |
| 131042 | Payment method problem | Fix billing on the WhatsApp Business Account |
| 131056 | Too many messages to the same recipient in a short time | Space out messages to that user |

Codes and wording change, so check Meta's error code page when you see an unfamiliar one.

### Common SMS failures

- **Invalid or badly formatted numbers.** Normalise to international format (for example +971 or +966) before upload.
- **Absent subscriber.** The phone is off or out of coverage; the operator may retry for a period before expiring the message.
- **Unregistered or blocked sender ID.** Some countries, including the UAE and Saudi Arabia, require registered sender names; unregistered traffic can be blocked.
- **Content or time-window filtering.** Promotional traffic may be filtered by local rules on content or sending hours; confirm current rules with your provider and the national regulator.

### Common email failures

- **Hard bounces** from non-existent addresses or domains: remove them immediately.
- **Soft bounces** from full mailboxes or temporary deferrals: retry, then suppress repeat offenders.
- **Authentication failures:** Gmail requires bulk senders to set up SPF, DKIM and DMARC; missing records lead to rejection or spam placement.
- **Spam complaints:** Gmail asks bulk senders to keep reported spam rates below 0.30% and recommends staying under 0.10%.

## How should you report campaign performance correctly?

Report a funnel with one base per stage, and say which statuses each channel can and cannot measure. The single most common error is dividing reads or clicks by messages sent instead of messages delivered, which mixes list quality with content quality.

### A reporting procedure that survives scrutiny

1. **Wait for statuses to settle.** Receipts arrive over minutes or hours; set a fixed cut-off (for example 24 or 72 hours) and state it.
2. **Count unique recipients and messages separately.** One recipient may receive several messages in a flow.
3. **Normalise statuses.** Count a read message as delivered too, since a read status can arrive without a delivered one.
4. **Compute rates on the right base:** delivery rate = delivered / sent; read rate = read / delivered; click rate = clicks / delivered.
5. **Break failures down by reason code** and by channel, not as a single "failed" number.
6. **Separate opt-outs from failures.** A 131050 on WhatsApp or an unsubscribe on email is a consent signal, not a technical error.
7. **Tie engagement to outcomes** such as orders, bookings or payments where you can track them.
8. **Export the raw report** (CSV) so finance and analysts can verify the numbers.

### Sample report layout

| Metric | Definition | Base |
|---|---|---|
| Submitted | Messages accepted for sending | Audience after suppression |
| Delivered | Delivered plus read | Submitted |
| Read / opened | Read receipts or estimated opens | Delivered |
| Clicked or replied | Button taps, link clicks, replies | Delivered |
| Failed (by reason) | Grouped by error code | Submitted |
| Opted out | STOP, unsubscribe, marketing stop | Delivered |

## Worked example: a Riyadh pharmacy chain's WhatsApp campaign

"Nakheel Pharmacy", a synthetic chain in Riyadh, sends a WhatsApp marketing template to a list of consented customers. After a 24-hour cut-off, the delivery report shows a share of messages delivered, a smaller share read, and a group of failures.

Grouping failures by code tells a clearer story. Most are 131026, meaning those numbers are not reachable on WhatsApp; the team routes them to an SMS version. A smaller group returns 131049, so the team checks targeting and does not retry the same template within 24 hours. A handful return 131050, and those numbers are moved to marketing suppression. One batch fails with 132001 because the Arabic template variant used the wrong language code, which is fixed before the next send.

The final report shows delivery rate, read rate on delivered, button clicks on delivered, and pharmacy visits redeemed from a coupon code. It notes that read rate excludes users with read receipts off.

## Common mistakes and honest limits

- **Treating sent as success.** Sent only means dispatched.
- **Comparing WhatsApp read rates with email open rates.** They measure different things with different blind spots.
- **Retrying everything.** Retrying opt-outs or unreachable numbers wastes spend and can harm quality signals.
- **Ignoring time zones and cut-offs.** Reports pulled at different times will not match.
- **Expecting perfect data.** Receipts can be delayed or missing; operator receipts vary by network; email opens are estimates. Say so in the report.

## How OmniChannels.ai helps

OmniChannels.ai provides delivery reports for [campaigns](/platform/campaigns/) on WhatsApp, SMS, email and Telegram, with a summary view, an advanced view, filters and CSV export so analysts can verify every number. Campaign tools include Excel or CSV upload, preview, scheduling and duplicate filtering, which reduces avoidable failures before sending. WhatsApp templates show approval status before launch, and the platform supports Arabic and English. Powered by BroadNet Technologies' SMS operator connectivity. To review your current reporting, [book a demo](/demo/).