Sent, Delivered, and Read: What Text Message Status Actually Means on Android

You send a text.

A moment later, the messaging app says:

Sent.

Does that mean the other person's phone received it?

Not necessarily.

What if it says:

Delivered.

Does that mean they opened it?

Still no.

And if you never see a delivery confirmation at all, does that mean you were blocked?

Definitely not something you can safely conclude.

On Android, words like sending, sent, delivered, and read describe different stages of the messaging process.

The exact information available also depends on whether the message is using SMS, MMS, or RCS.

The simplest way to think about it is:

Those stages are not interchangeable.

And standard SMS does not provide all of them.

"Sent" does not mean "delivered"

For a standard SMS message, sent means the phone's sending process completed successfully.

That is useful information.

It tells you the message did not immediately fail because of something like an unavailable radio, lack of service, or another local sending error.

But it does not prove that the recipient's phone received the message.

The destination phone could be:

• turned off
• outside coverage
• temporarily unreachable
• affected by a carrier problem

The message might also encounter a problem somewhere farther along the delivery path.

So it is better to interpret sent as:

The send step succeeded.

Not:

The other person definitely has the message.

Android's SMS APIs make this distinction directly: sending success and delivery confirmation are separate events.

"Delivered" is a separate confirmation

Standard SMS can support something called a delivery report or delivery receipt.

When requested and supported, the mobile network can return a status indicating that the message reached the destination side of the SMS delivery path.

That is what allows some SMS apps to show a delivered state.

But there is an important catch:

SMS delivery reports are not universal.

Whether you receive one can depend on:

• the messaging app
• whether the app requested a delivery report
• your carrier
• carrier configuration
• the destination network
• other network conditions

Some carriers or services simply do not provide SMS delivery reports.

For example, Google Fi's current documentation explicitly states that SMS delivery reports are not supported.

So if one Android user sees Delivered after sending an SMS and another never does, that does not automatically mean something is wrong.

Their carriers may simply provide different information.

Delivered still does not mean read

This is probably the most important distinction.

A delivery report is about the messaging system.

It is not proof of what the human recipient did afterward.

A message can be delivered while the recipient:

• has not opened the conversation
• has not looked at their phone
• has notifications disabled
• has the conversation muted
• ignores the message entirely

So:

Delivered does not mean read.

It does not mean:

They saw it and are ignoring me.

It means the messaging system returned a delivery confirmation.

Those are very different claims.

Standard SMS does not have a true read receipt

Traditional SMS does not provide the same kind of read-receipt system that modern internet messaging services do.

An SMS delivery report can tell the sender that the message reached the destination side of the network.

It cannot reliably tell the sender when the recipient opened or read the text.

So for normal SMS:

Sent and Delivered can exist.

A true Read status generally does not.

That is one of the major differences between traditional SMS and RCS.

RCS adds a richer status system

RCS can provide much more detailed messaging status.

In Google Messages, current RCS conversations can display:

• a timer while the message is being sent
• one checkmark when it is sent
• two checkmarks when it is delivered
• filled two checkmarks when it is read

Google explains those indicators here:

Google's RCS status indicator guidance

Those indicators apply to RCS chats.

They do not appear the same way for ordinary SMS or MMS.

That distinction matters because a conversation in Google Messages might use RCS today and fall back to SMS/MMS later depending on participant capabilities, network availability, or messaging settings.

The status information available can change with the messaging system being used.

RCS read receipts can also be turned off

Even RCS does not guarantee that you will always see a Read status.

Users can control whether they send read receipts.

In Google Messages, this is part of the RCS chat settings.

Google documents the setting here:

Google's RCS read receipt settings guidance

So if an RCS message shows Delivered but never changes to Read, there are several possible explanations.

The person may not have opened it.

They may have read receipts disabled.

The conversation may no longer be using RCS.

Or there may be another connectivity or messaging-state issue.

Again, a missing status does not give you enough information to confidently infer what the person did.

Even "Read" has limits

A read receipt is stronger evidence than a delivery receipt.

But it still should not be interpreted more broadly than the system actually reports.

Google Messages describes the state as read, but its public documentation does not define every possible UI detail behind that event.

And even when a message is marked as read, that does not prove the person:

• carefully read every word
• understood the message
• intends to reply
• saw every attachment
• is deliberately ignoring you

A messaging status can tell you something about the software state.

It cannot tell you what somebody is thinking.

What about MMS?

MMS has its own delivery process.

When you send a picture, video, group message, or other MMS content, the message may first need to be uploaded to the carrier's MMS service.

That creates more stages where something can go wrong.

For example:

• the attachment may be too large
• mobile data may be unavailable
• carrier MMS configuration may be incorrect
• the carrier may accept the upload but the recipient may not retrieve it immediately
• the MMS may expire before retrieval

MMS standards can support delivery-report behavior, but support and presentation vary considerably between carriers, devices, and messaging apps.

So just like SMS, you should not assume every Android phone will display identical MMS status information.

If you are dealing specifically with group MMS problems, a separate guide explains why Android group messaging can behave differently:

Why Group Texts Get Complicated on Android: MMS, Mass Texts, and RCS

Long SMS messages can make status more complicated

A long text message may look like one bubble in your messaging app while being transmitted as several SMS segments underneath.

Android can track sending and delivery for those individual segments.

The messaging app can then present those lower-level results as one simpler status for the conversation.

That means the clean status you see in the interface may represent several pieces of work underneath.

This is another reason not to treat every visible status label as a perfect description of everything happening across the network.

For most users, the useful rule is simply:

A very long SMS can involve multiple transmitted parts even though the app shows it as one message.

No delivery report does not mean the message failed

This is another common misunderstanding.

You might send an SMS and see:

Sent

but never:

Delivered.

That does not automatically mean the message failed.

The carrier may not support delivery reports.

The report may not have been requested.

The destination network may not return one.

The report may be delayed.

Or the messaging app may not expose it in the interface.

Google Fi provides a particularly clear example: its documentation says SMS delivery reports are not supported.

So the absence of Delivered is not itself proof that the recipient never got the message.

No delivery report does not mean you were blocked either

Search the web for phrases like:

How do I know if someone blocked my texts?

and you will find plenty of confident answers based on delivery indicators.

Most are far more certain than the technology justifies.

There is no universal Android SMS rule where:

This exact status means you were blocked.

Different carriers, devices, apps, and filtering systems can behave differently.

A missing delivery report can happen because of ordinary network behavior.

A recipient may be offline.

The carrier may not provide delivery reports.

A message might reach the phone and then be placed into a spam or blocked view.

Or the message might encounter another delivery problem entirely.

Many of those situations can look similar from the sender's side.

So:

SMS delivery status is not a reliable way to determine whether somebody blocked you.

If a website claims otherwise without very specific carrier and platform evidence, treat the claim cautiously.

Spam filtering can happen after network delivery

Another reason delivery status can be misleading is filtering.

A carrier or phone may successfully receive a message before a messaging app decides how to display it.

For example, an app could classify the message as suspected spam and place it somewhere other than the main inbox.

From the network's perspective, the message may still have reached the device.

That demonstrates why delivered should not be interpreted as:

The recipient definitely saw this in their normal inbox.

Delivery and presentation are separate steps.

Why different Android phones show different statuses

There is no single Android-wide UI for message status.

Android provides the underlying messaging capabilities, but individual apps decide how to present them.

Carriers can also determine which delivery-report features are available.

That means two people using Android might see very different interfaces:

One app might show:

Sent

Another might show:

Sent
Delivered

An RCS conversation might instead show checkmarks.

And another carrier might provide no SMS delivery confirmation at all.

Those differences do not necessarily mean one app is broken.

They may reflect different protocol and carrier capabilities.

If a message is stuck on "Sending"

A message that never reaches Sent is a different problem from one that is sent but lacks a delivery report.

If a message remains stuck on sending, start with the basics:

Check your mobile connection

SMS requires cellular service.

If the phone has no signal or is temporarily disconnected from the network, sending may be delayed or fail.

Check Airplane mode

Make sure Airplane mode is not blocking cellular service.

Toggling connectivity or restarting the phone can sometimes restore a stuck connection.

Confirm your default SMS app

Android expects one app to operate as the default SMS handler.

If you recently changed messaging apps, confirm that the app you intend to use is actually set as the default.

Check the recipient number

For international contacts especially, make sure the number is complete and includes the appropriate country code.

Determine whether the conversation is SMS, MMS, or RCS

A failing MMS attachment may have a completely different cause from a failing SMS.

An RCS conversation may also behave differently when RCS connectivity is unavailable.

Knowing which system is actually sending the message makes troubleshooting much easier.

If SMS works but MMS does not

If ordinary text messages send successfully but:

• photos fail
• videos fail
• group messages fail

then the problem may be MMS-specific.

Things worth checking include:

• mobile data availability
• attachment size
• carrier MMS support
• group messaging settings
• carrier account restrictions

MMS relies on more than the basic SMS path, so successful SMS does not guarantee successful MMS.

If RCS checkmarks suddenly disappear

If you normally see RCS delivery/read indicators and suddenly do not, first confirm whether the conversation is still using RCS.

RCS availability can depend on:

• both participants being RCS-capable
• data connectivity
• the current group membership
• RCS registration and settings

If the conversation falls back to SMS/MMS, the RCS checkmark status system no longer applies.

That does not necessarily mean the message failed.

It may simply be using a different transport.

You usually should not turn RCS off just to investigate a status icon

Disabling RCS is sometimes appropriate when troubleshooting specific registration or message-routing problems.

But it should not be the first response every time a status indicator changes.

Google provides specific guidance for situations where users have switched phones or messaging apps and messages are not arriving correctly.

Turning RCS off can also affect existing RCS conversations and groups.

So it is better to first determine whether the problem is actually related to RCS before changing that setting.

What ZenSMS can show

ZenSMS supports standard SMS and MMS rather than RCS.

When your carrier provides delivery reports, ZenSMS can show message states such as:

• sent
• delivered
• failed

The important part is:

when your carrier provides delivery reports.

ZenSMS cannot manufacture a carrier delivery confirmation that the network never provides.

And standard SMS does not provide a true human read receipt.

So a message being marked Delivered in ZenSMS should be understood the same way as any SMS delivery report:

the messaging system provided a delivery confirmation.

It does not mean the person opened or read the message.

The simplest rule: do not give a status more meaning than it has

Message status is useful.

It can tell you whether sending succeeded.

It can sometimes tell you whether the network returned a delivery confirmation.

With RCS, it can sometimes tell you whether a message was marked as read.

But those are different levels of information.

The easiest way to remember them is:

Sent means the send step succeeded.

Delivered means a delivery confirmation was received when supported.

Read requires a messaging system with read receipts, such as eligible RCS conversations.

And perhaps most importantly:

A status indicator can tell you something about the messaging system. It usually cannot tell you what the person on the other end actually did.