We send a text message to someone, the delivery receipt appears, and we think that the message has been read. Except that the person on the other end may have blocked our number for weeks. The problem is that the delivery receipt does not prove that the SMS has been seen. It only indicates that the network has transmitted the message to the recipient’s phone, not that a human has opened it.
To understand this discrepancy, we need to look at what happens on the network side, the phone side, and the application side. These three levels do not filter messages in the same way, and the information sent back to the sender changes completely depending on the case.
You may also like : How to Rent a Car Easily and Affordably for Your Travels
Local blocking on Android and iPhone: the SMS still arrives
When we block a number directly in the settings of an Android phone or an iPhone, the blocking is managed by the phone’s operating system. The mobile network, on the other hand, does not know that a block is active. It does its job normally: delivering the SMS to the device.
In practice, the message is indeed delivered to the phone. It is then that the system intervenes: on Samsung, the SMS lands in a “Blocked SMS” folder accessible in the Messages app settings. On iPhone, it is silently redirected without notification.
Related reading : Discover the new platform for unusual news and trends you can't miss
From the sender’s side, the network has successfully delivered the message. If the option for delivery receipt of a blocked SMS is activated, we therefore receive the delivery confirmation. Nothing distinguishes this confirmation from that of an SMS normally received by someone who has not blocked anyone.
This is a point that generates a lot of confusion: we interpret the receipt as proof of reading when it only means “the network has deposited the message on the phone”.
Operator filtering and anti-spam: when the SMS never reaches the phone
The scenario changes radically when the blocking is not local but operated by the operator or a network filter. Services like Orange Phone or the filters integrated into Google Messages can intercept an SMS before it physically reaches the device.
In this case, the message is blocked on the server side, not on the phone side. The direct consequence: the network cannot confirm delivery to the mobile since delivery did not occur. The sender then receives no delivery receipt, or receives a failure status depending on the configurations.
This type of filtering has developed in recent years with the fight against SMS spam. Operators categorize certain messages as unwanted and block them upstream. The sender’s number does not need to have been manually blocked by the recipient for this filtering to apply.
- Local blocking (phone OS): the SMS is delivered, the receipt is generated, but the recipient does not see the message in their main inbox.
- Operator blocking (network filtering): the SMS is not delivered to the phone, no reliable receipt is sent back to the sender.
- Application blocking (WhatsApp, Telegram, Signal): each application has its own notification rules, independent of the SMS network.
RCS and read receipt: a real difference from classic SMS
The RCS (Rich Communication Services) protocol, which is gradually replacing SMS on Android via Google Messages, introduces a distinction that traditional SMS does not allow: the “read” status in addition to the “delivered” status.
With RCS, when a message is delivered to the phone, the sender sees a first checkmark. When the recipient actually opens the conversation, a second confirmation appears. If the number is blocked locally, the message may be delivered (first checkmark) but never opened (no second checkmark).
For an attentive sender, a message that is consistently “delivered” but never “read” over several successive sends can be an indication of blocking. This is not absolute proof (the person may simply not open their messages), but it is information that classic SMS does not provide at all.
Feedback on this point varies according to versions of Google Messages and the recipient’s privacy settings, which can disable read receipts in their settings.
Professional SMS and delivery status: what businesses see
Professional SMS sending platforms (like RCS Business Messaging or solutions offered by Nexcalia and Conexteo) have more detailed dashboards than what an individual sees on their phone.
These tools distinguish several statuses:
- “Sent”: the message has left the platform to the network.
- “Delivered to device”: the network confirms delivery to the recipient’s phone.
- “Read”: the recipient has opened the message (available only in RCS, not in classic SMS).
- “Failed”: the network was unable to deliver the message, which may indicate operator filtering or an invalid number.
A professional can distinguish blocking from simple non-reading thanks to this granularity. An individual, with a classic SMS, does not have this information. The standard SMS delivery receipt is binary: delivered or not delivered, without additional context.
How to interpret the absence of a delivery receipt
If we send an SMS and no delivery receipt arrives, several causes are possible. The recipient’s phone is off, out of network, or full. An operator filter intercepted the message. The number is invalid.
The absence of a receipt does not automatically mean a block. Conversely, receiving a receipt does not mean that the recipient has seen the message. These two shortcuts are the most widespread, and both are false.
The only reliable way to know if we are blocked remains indirect: try calling (systematically redirected to voicemail after one ring), try from another number, or observe behavior on other communication channels. No technical indicator on the SMS side allows for confirming a block with certainty when it is managed locally by the recipient’s phone.
The next time a delivery receipt appears after an unanswered SMS, we now know what it really means: the network has done its job, nothing more.