

Sophie
18 de octubre de 2026 · 11 min de lectura
You send a text to someone whose phone is switched off, in airplane mode, in a tunnel or out of coverage. The message goes out, no error appears… and it lands three hours later, sometimes the next day, sometimes never. This isn't random: an undeliverable text is stored and retried by your carrier's message centre for a window known as the validity period. Once that window closes, the message is destroyed without anyone telling you.
Updated 18 October 2026.
What happens to a text sent to a switched-off phone?
It's held in the SMSC (Short Message Service Centre) of either the sender's or the recipient's carrier, which attempts delivery at regular intervals until the handset reconnects to the network. As soon as the device powers back on or regains signal, the message arrives, often within seconds. If it doesn't reconnect before the validity period expires, the text is deleted.
This behaviour has been at the heart of the SMS service since the GSM standard: SMS is what's known as a store and forward service, unlike a call, which requires both parties to be reachable at the same moment. That's precisely why a text gets through where a call fails, and it's also why you can never know, at the moment of sending, whether the recipient is reachable.
In practice, the chain looks like this:
- Your phone hands the text over to your carrier's SMSC.
- The SMSC queries the recipient's network (via its HLR/HSS, the subscriber directory) to find out where the line is.
- If the network replies "absent subscriber" (phone off, out of coverage, airplane mode), the SMSC puts the message in a queue.
- The recipient's network flags the line as "to be notified"; the next time the handset reconnects, it alerts the SMSC, which resends the message.
- In parallel, the SMSC retries on its own according to a schedule set by the carrier (a few minutes, then longer intervals).

How long does a text stay in the queue?
Anywhere from a few hours to several days, depending on the validity-period value sent with the message and on the rules of the SMSC holding it. The GSM/3GPP standard allows this duration to be expressed from 5 minutes up to 63 weeks, but no consumer carrier keeps a text that long: the values actually applied in industry practice range from 24 hours to a few days.
Two parameters are layered on top of each other, and that's the source of most of the confusion:
| Parameter | Who sets it | Effect |
|---|---|---|
| Requested validity period | The messaging app / the sender | Maximum desired storage time |
| SMSC retention period | The carrier | The real ceiling: if it's shorter, it wins |
| Retry schedule | The carrier | How often delivery is reattempted while queued |
In other words: even if your phone asks for "keep it 7 days", an SMSC configured for 48 hours will destroy it after 48 hours. The reverse is also true: requesting a validity of 1 hour makes the message expire very quickly, even though the carrier could have held it longer.
On Android, this setting was long visible in messaging apps under labels such as "validity period" or "SMS validity". It has disappeared from Google Messages, which leaves the value up to the network. On iPhone, iOS has never exposed this setting. In practice, for a consumer in 2026, the storage duration is therefore decided by the carrier, not by you.
Why does the window shrink as soon as you text abroad?
Because an international text doesn't pass through a single SMSC but through a chain of intermediaries, and each link applies its own retention period — the shortest one always prevails.
A text sent from France to a Movistar mobile in Spain, Telcel in Mexico or Orange Maroc typically goes through your carrier, then through one or more wholesale carriers specialising in routing SMS between networks, then through the destination carrier. If the intermediary carrier only holds messages for a few hours, your text won't wait around for the handset to power on the next day: it will be dropped along the way, with no failure notification reaching you.
It's the same mechanism that makes delivery receipts unreliable internationally, a topic covered in detail in our article on international SMS delivery receipts: on international routes, status information travels poorly, and the absence of an error message never means "delivered".
Three common international scenarios:
- Recipient roaming: the line is attached to a visited network. The text has to be routed to that network; if the roaming handset is off, queuing happens at the recipient's home carrier, with the usual retries. It often works well, but with more latency.
- Badly formatted number: the message never enters a queue at all — it's rejected or sent to a different subscriber. We cover this in detail in our guide to international number formatting.
- Intermediary spam filtering: some networks block international texts coming from unusual sources. The message vanishes silently, exactly as if it had expired.
Airplane mode, "phone switched off", out of coverage: are they the same?
As far as the network is concerned, yes, in most cases: all three situations produce the same "subscriber unreachable" state. But there are nuances that change the outcome.
- Phone switched off: the line detaches cleanly from the network. The network knows it's absent and notes that it will have to alert the SMSC on its return. This is the most reliable scenario: the text lands as soon as the phone powers on.
- Airplane mode: same logic, clean detachment. However, if the device stays in airplane mode with Wi-Fi on, RCS messaging or internet apps can still receive, while texts remain queued. Hence the feeling that "WhatsApp gets through but texts don't".
- Out of coverage / tunnel / basement: the detachment isn't clean. The network may consider the line still present for a while, attempt a delivery that fails, then fall back to queuing. The result: more erratic delays and, sometimes, a message that arrives long after signal returns.
- SIM card removed or line cancelled: here the network responds differently. A cancelled line generally causes delivery to fail immediately, with no queuing.
For journeys where you know you'll lose coverage — overnight trains, hiking, rural areas — the useful habit isn't to keep hitting send but to keep the device powered: a compact power bank stops the phone from shutting down for lack of charge, which is exactly the situation where queued texts end up expiring before reconnection. In a vehicle, a dual-USB car charger serves the same purpose.

How can I tell whether my text is queued or lost?
There's no reliable indicator on the sender's side. It's frustrating, but that's the reality of the protocol: SMS was never designed with a "queued" state visible to the sender. Here's what you can still observe.
- Check the message's local status. On both iPhone and Android, a message marked "Sent" only means it has left your phone and been accepted by the SMSC. It says nothing about the recipient.
- Turn on delivery receipts before sending (Android: Google Messages → Settings → Advanced → SMS delivery reports). Receiving one proves delivery; its absence proves nothing.
- Look at which channel is being used. If the conversation is over RCS (a bubble labelled "Chat" or "RCS"), the message isn't a text: it travels over the internet and waits on Google's servers under different rules. If it's never delivered, the app may offer to fall back to SMS.
- Resend once the recipient is back. If the person confirms they've powered on and received nothing after 10 minutes, treat the message as expired or filtered, and resend it.
- Try a second channel. A call, a message via an internet app, or a send from a web interface will tell you whether the problem is the line or the SMS service. Our homepage also lets you send a free text from your browser to test without using up your plan.
Can an expired text reappear later?
No. Once the validity period has elapsed, the message is deleted from the SMSC: it no longer exists anywhere, neither at your carrier nor at the recipient's. No customer service can "re-send" it, and it won't resurface the next time the phone is powered on.
That said, two phenomena create the illusion that it can:
- Burst delivery. When a phone that's been off for a long time powers back on, all still-valid messages arrive within seconds, sometimes in a jumbled order. Sorting relies on the SMSC's timestamp, not on the order in which messages were sent: a text sent earlier may appear later.
- App resynchronisation. With RCS or an internet messaging app, messages are replayed from a server when the device reconnects. It looks like a text emerging out of nowhere, but it isn't one.
If the history matters to you — proof of an appointment, an important exchange — the only reliable approach is to keep it yourself. An SMS backup app exports conversations, and for offline archiving, a USB OTG drive for smartphones lets you move files off the phone without going through a computer.
Which settings help avoid lost texts?
No setting can force a carrier to hold a message longer. But several checks will rule out false problems, where the text never actually left or never landed on the right channel.
- Correct message centre (SMSC) number. An SMSC number wiped after a SIM swap prevents any sending at all. On Android: Settings → Apps → Messages → advanced, or via the manufacturer's diagnostic menu. When in doubt, carrier support can provide the exact value.
- SIM memory and phone storage not full. Full storage can block the reception of new texts: they stay queued on the network side and eventually expire.
- Wi-Fi calling enabled when mobile coverage is poor at home. VoWiFi also lets you send and receive texts over your router. The details are in our guide to Wi-Fi calling.
- 4G/VoLTE network available. With the gradual shutdown of 2G and 3G at French carriers, an older handset without VoLTE support can lose voice and texts in certain areas. The carrier-by-carrier timeline is detailed in our article on the end of 3G in France.
- A charged backup device. In households where one line needs to stay reachable, a simple mobile phone with long battery life acts as a fallback when the main smartphone is flat.

Key takeaways
A text sent to a switched-off phone is neither lost nor blocked: it waits in a message centre, with a lifespan decided by the carriers it passes through. Domestically, that wait comfortably absorbs a night without coverage. Internationally, it can shrink to a few hours, and expiry generates no alert whatsoever for the sender.
Best practice for an important message abroad: keep it short, double-check the number format, and follow up after a few hours rather than waiting for a confirmation that will never come. For billing and coverage questions, the public data from Arcep and the carriers' official pages remain the only up-to-date references; our FAQ gathers the most common questions about sending, receiving and roaming.
Frequently asked questions
Are you charged for a text sent to a switched-off phone?
Yes. Billing is triggered when the message is accepted by the message centre, not on delivery. A text that expires without being delivered is still counted against your plan or billed per message.
How long does a text wait before being deleted?
There's no universal figure. The standard allows up to 63 weeks, but consumer carriers apply far shorter durations, in the region of 24 hours to a few days. On an international send, it's the most restrictive link in the chain that decides.
Why do my texts arrive out of order after a restart?
Because queued messages are delivered in a burst and sorted by the timestamp assigned by the message centre, which doesn't always match the actual order of sending, especially when several carriers are involved.
Can you tell whether the recipient's phone is switched off?
No, not from your messaging app. The network doesn't share a line's attachment status with the sender of a text, for privacy reasons. Only a call gives an indirect clue, and even then it's not very reliable.
Does RCS keep messages longer than SMS?
Often yes, because it relies on internet servers rather than carrier SMSCs. But RCS requires a data connection on both ends: if the recipient only has 2G coverage or no data, the app has to fall back to SMS for the message to get through.

