SMS Delivery Reports on Android: How to Turn Them On and Read Them
An SMS delivery report is a notification from the mobile network confirming that a text message reached the recipient's handset. It is generated by the carrier, not the messaging app, and it confirms delivery only, not that the message was opened or read.
That definition matters because most confusion around delivery reports comes from expecting them to behave like the blue ticks in a chat app. They do not. A delivery report is a network-level receipt, and whether you see one depends as much on your carrier and your SIM as on the phone in your hand. This guide covers how to switch delivery reports on in Google Messages and other Android apps, why the toggle sometimes disappears, what iPhone users can and cannot see, and how businesses sending messages at scale should read delivery data without overtrusting it.
Table of Contents
- What Is an SMS Delivery Report?
- How to Turn On SMS Delivery Reports in Google Messages
- Turning Delivery Reports On in Other Android Messaging Apps
- Why Your SMS Delivery Report Never Arrives
- Delivery Reports on iPhone: What iOS Actually Shows
- How Businesses Get Reliable SMS Delivery Confirmation at Scale
- Frequently Asked Questions
- What to Check Before You Trust an SMS Delivery Report
What Is an SMS Delivery Report?
A network notification that your message reached the recipient's handset, not that they opened it
When you send a text, it travels from your phone to your carrier's SMSC (Short Message Service Centre), then to the recipient's carrier, then to their handset. A delivery report is the confirmation that comes back along that chain. It tells you the message arrived at the handset. It does not tell you the person read it, and it does not tell you they understood it. It is a technical receipt, not a social one.
This distinction is the single most important thing to grasp. A delivery report can arrive while the recipient's phone is face-down on a table, locked, and ignored. It still counts as delivered.
How it differs from a read receipt and from the 'Sent' tick in chat apps
Chat apps like WhatsApp or Telegram show two kinds of status: one tick for sent, two ticks for delivered, and often a blue colour for read. Those statuses are generated by the app's own servers, not by the mobile network. SMS delivery reports work differently. They are generated by the carrier's SMSC and sent back to your phone as a special network message. There is no standard SMS read receipt at all. If you need to know whether someone read a text, SMS cannot tell you that, and no app can add that capability on top of the network.
Why the report comes from the carrier and not from the messaging app itself
The messaging app is just a window. It sends your text to the SMSC and displays whatever the network sends back. This is why the delivery report toggle in Google Messages can be switched on and still produce nothing: the app has asked the network for a receipt, but the network may not support or send one. The app cannot manufacture a delivery report out of thin air. It can only show you what the carrier provides.
How to Turn On SMS Delivery Reports in Google Messages
Open Settings inside the app, then Messages settings, then Advanced or Text messages depending on version
Google Messages has moved this setting around across versions. The reliable path is to open the app, tap your profile picture or the three-dot menu, choose Messages settings, then look for Advanced or Text messages. In some builds the option sits under Delivery reports directly; in others it is nested under Text messages. If you do not see it at first, scroll. Google has a habit of burying it one level deeper with each redesign.
Toggle 'Delivery reports' or 'Get SMS delivery reports' on
Once you find the toggle, switch it on. The label may read Delivery reports or Get SMS delivery reports. Either way, it is a simple on/off switch. There is no confirmation screen and no test message. The change is immediate, but you will only notice it the next time you send a text and the network chooses to send a receipt back.
What changes on screen after a message is sent once the toggle is active
With the toggle on, a successfully delivered message typically shows a small checkmark or a short status line beneath the message bubble. The exact appearance depends on your phone manufacturer and Android version. On some devices you get a subtle tick; on others you get a text label like Delivered. If nothing appears, that does not necessarily mean the message failed. It may mean the carrier did not send a receipt, which is common on some networks and on some prepaid plans.
Turning Delivery Reports On in Other Android Messaging Apps
Samsung Messages: Settings, More settings, Text messages, Delivery reports
Samsung's stock messaging app follows a similar logic but a different path. Open the app, tap the three-dot menu, go to Settings, then More settings, then Text messages, and look for Delivery reports. Switch it on. Samsung phones sold through different carriers sometimes hide or rename this option, so if you cannot find it, check whether your carrier has its own messaging app that has taken over the default SMS role.
Xiaomi and Redmi: the option sits in the stock Messaging app settings and can move after a system update
On Xiaomi and Redmi phones, the delivery report toggle lives in the stock Messaging app's settings, usually under Advanced or More settings. The catch is that Xiaomi reorganises its settings menus frequently with MIUI and HyperOS updates. An option that was under one heading last year may be under another this year. If you recently updated and the toggle vanished, look through the advanced settings again before assuming it was removed.
If the toggle is missing entirely: check the app's default SMS role and your SIM's carrier support
A missing toggle usually means one of two things. First, the app you are looking at may not be the default SMS app. Android only lets the default messaging app handle SMS fully, and some apps hide delivery report settings when they are not the default. Set the app as default in Android settings and check again. Second, your carrier may not support delivery reports at all. In that case the toggle may exist but do nothing, or the app may hide it because the network has told the phone the feature is unavailable.
Why Your SMS Delivery Report Never Arrives
SMS delivery reports are a carrier-level feature, so whether the toggle works depends on your network as much as your phone. That single fact explains most of the frustration people have with this setting.
Your carrier may not support delivery reports on your plan or in your region
Not every Nigerian network, and not every plan on those networks, sends delivery reports. Some carriers enable them by default, some require a short code to activate them, and some simply do not offer them on certain prepaid products. If the toggle is on and you never see a report, the first call is to your carrier's customer service, not to Google.
The report can be silently dropped when the recipient is roaming or on a different network
Delivery reports travel between carriers. When the recipient is roaming, or when the message crosses from one network to another, the receipt can be lost in the handoff. The message may still arrive perfectly. You just never get the confirmation. This is a routing issue, not a failure of your phone.
Dual SIM phones sometimes send reports to the wrong SIM slot
On dual SIM Android phones, the delivery report for a message sent from SIM 1 can occasionally arrive on SIM 2, or fail to display because the phone is not sure which slot to attribute it to. If you use two SIMs, try sending from the other slot to see whether reports appear. Some phones also have a per-SIM delivery report setting that you need to enable separately.
A report means the handset received it, not that the person read it
This bears repeating because it is the most common misunderstanding. A delivery report confirms the handset received the message; it says nothing about whether the recipient read it. If you need proof of reading, SMS is the wrong channel. Use a phone call or an app-based channel that supports read receipts.
Delivery Reports on iPhone: What iOS Actually Shows
SMS delivery reports are a carrier feature, and iOS does not expose a per-message report toggle
iOS does not have a setting labelled SMS delivery reports. Apple has never implemented a per-message toggle for SMS because the feature depends on carrier support, and Apple does not want to show a setting that would silently fail on networks that do not provide receipts. On an iPhone, you get delivery information for iMessage, not for SMS.
iMessage shows 'Delivered' but that is a different channel from SMS
When you send an iMessage to another Apple device, you see Delivered under the message. That status comes from Apple's servers, not from the mobile network. It is not an SMS delivery report. If the message falls back to SMS because the recipient is not on iMessage, the Delivered label does not appear, and you have no network-level confirmation at all.
What to check in Settings, Messages if a message fails outright
If an SMS fails outright on iPhone, you may see Not Delivered under the message. That is not a delivery report in the Android sense; it is an error state. Check Settings > Messages to confirm SMS is enabled, and check that your carrier settings are up to date. If messages consistently fail, the issue is usually the carrier account or the signal, not the phone.
How Businesses Get Reliable SMS Delivery Confirmation at Scale
Carrier receipts are not proof of delivery: aggregators use direct-to-carrier routes and adaptive routing to improve accuracy
When a business sends thousands of messages, carrier receipts become statistical rather than individual. A receipt that says delivered means the carrier's system recorded a handset acknowledgement, but carriers sometimes report delivery when the message has not actually reached the person. Reputable bulk SMS providers use direct-to-carrier connections to reduce the number of hops, and some use adaptive routing that watches for patterns of false positives and reroutes traffic accordingly. This is why two providers can show different delivery rates for the same list.
What to ask a bulk SMS provider: receipt support, route transparency and fallback behaviour
Before committing to a provider, ask three questions. Does the platform return delivery receipts for every message, or only for some routes? Can you see which route a message took, or is the routing hidden? And what happens when a receipt never arrives: does the platform retry, mark it as unknown, or silently count it as delivered? A provider that answers these clearly is worth more than one that promises a high percentage without explaining how it measures it.
Why a delivery report from a gateway can lag minutes behind the actual handset event
Gateway delivery reports are not instant. The message may reach the handset in seconds, but the receipt has to travel back through the carrier's systems, through the aggregator, and into your dashboard. A lag of a few minutes is normal. A lag of hours usually means the carrier is batching receipts or the route is congested. Do not panic-refund a campaign because the dashboard has not updated within sixty seconds.
Checking sender ID registration and DND status with Nigerian carriers before blaming the report
In Nigeria, sender ID registration and Do Not Disturb (DND) status with carriers affect whether bulk SMS messages are delivered at all, regardless of what the report shows. If your sender ID is not registered with the carriers, messages may be blocked or altered before they ever reach a handset, and no delivery report will appear because there was nothing to report. Similarly, messages sent to numbers on DND may be filtered by the carrier. Before you blame the reporting system, confirm that your sender ID is approved and that your recipient list respects DND rules. This is the kind of thing Sendam is built for: sender ID approval is shown as a live tracker, and delivery reports explain failures in plain language instead of just saying failed, so you can tell the difference between a routing problem and a registration problem.
Frequently Asked Questions
What is an SMS delivery report?
An SMS delivery report is a notification from the mobile network confirming that a text message reached the recipient's handset. It is generated by the carrier, not the messaging app, and it confirms delivery only, not that the message was opened or read.
Why is the delivery report option missing from my messaging app?
The option can be missing because the app is not set as the default SMS app, because your carrier does not support delivery reports, or because a software update moved the setting. Check the app's default status first, then check with your carrier.
Does an SMS delivery report mean the message was read?
No. A delivery report confirms only that the handset received the message. It says nothing about whether the recipient opened, read, or understood it. There is no standard SMS read receipt.
Can I get SMS delivery reports on an iPhone?
iOS does not offer a per-message SMS delivery report toggle. Delivery information is available for iMessage, which is a different channel. For SMS, you may see Not Delivered if a message fails, but you will not get a positive delivery confirmation from the network.
Why did my delivery report arrive hours after I sent the message?
Delivery reports can lag because the receipt has to travel back through the carrier's systems and the aggregator. A delay of minutes is normal. A delay of hours usually means the carrier is batching receipts or the route is congested.
Do bulk SMS gateways provide the same delivery reports as my phone?
Bulk SMS gateways provide delivery reports at scale, but they are not identical to the reports on your phone. Gateway reports come from the aggregator's connection to the carrier and can include route information and failure reasons. They are more useful for business analysis but still confirm delivery, not reading.
What to Check Before You Trust an SMS Delivery Report
Start with the basics: confirm the toggle is on in your messaging app, confirm the app is the default SMS handler, and confirm your carrier actually supports delivery reports. If the reports still do not appear, the issue is almost certainly on the network side, not your phone. For business senders, the checklist is different: verify your sender ID registration, respect DND status, and choose a provider that explains its delivery reports in plain language rather than hiding behind a percentage. If you are sending in Nigeria and want to see how that looks in practice, you can create a Sendam account and check the delivery reporting on a small test campaign before scaling up.