In short. An anonymous text that "won't send" is almost never a fault with your phone. In the vast majority of cases, it's network-side filtering: the recipient's carrier refuses a message whose sender can't be identified, or the sending gateway rejected your request. And because you're anonymous, you have no reliable delivery confirmation: silence proves nothing.
Information verified on 4 November 2026 on the public pages of Arcep (the French telecoms regulator), the CNIL (the French data protection authority), service-public.fr, Légifrance, cybermalveillance.gouv.fr and the AF2M, as well as the support pages of the French carriers (Orange, SFR, Bouygues Telecom, Free Mobile) and Apple's and Google's documentation. This article provides general information and is no substitute for professional advice.
Why does an anonymous text fail more often than a normal one?
Because it goes through one extra step and arrives without any verifiable identity. A standard text message leaves your SIM card and passes through your own carrier, which knows you and bills you; it is routed with a valid sender number. An anonymous message, on the other hand, goes through a third party (a sending website, a gateway, an app, a secondary number) before it ever reaches the recipient's network.
Each of those layers can refuse the message:
- the gateway itself (quota reached, abuse detected, recipient's country not supported);
- the intermediary aggregator that connects the gateway to the carriers;
- the recipient's carrier, which applies its own anti-abuse rules;
- and finally the recipient's handset, which can filter what it receives.
In other words, a failure isn't necessarily "your" failure. It's often a decision taken three networks away, with no explanation, because the SMS chain was never designed to send a detailed rejection reason back to an anonymous sender.
Worth remembering: in the world of SMS, a message can be accepted by the gateway and discarded further down the line. The "message sent" you see on screen means one thing only: your request was taken.
The 8 real causes of a sending failure
1. The recipient's number is badly formatted
This is the number one cause, and the silliest. Gateways generally expect an international format: +33 followed by the nine digits, with no leading zero. A French 06 12 34 56 78 becomes +33612345678. A zero left in place (+330612…) or misplaced spaces can be enough to get the request rejected — or, worse, to send it somewhere else entirely.
Also check that you're actually targeting a mobile. A geographic landline number starting 01 to 05 won't receive texts in most cases; we covered this point in our article on sending a text from a landline.
2. The sender isn't accepted by the recipient's carrier
A text message carries a "sender" field (the sender ID). It can be a number, a short code, or an alphanumeric name. French carriers increasingly filter this field to fight sender identity spoofing, an effort tracked by Arcep and the AF2M, the French mobile multimedia industry association.
The very concrete consequence: a message whose sender is empty, exotic, or imitating a brand name has statistically far less chance of arriving than a message with a compliant numeric sender. To understand what the recipient sees in place of your number, read who is the sender of an anonymous text.
3. Anti-abuse filtering has kicked in
Carriers and aggregators watch for simple signals: a sudden spike in volume, identical text repeated, the presence of a link, words associated with scams, bursts sent to consecutive numbers. A single message often gets through; ten identical messages in three minutes get blocked.
That's exactly why persistence backfires: the more you resend, the more you look like an unwanted campaign. We went into this in sending a single anonymous text, without pushing.
4. The message is too long or contains unsupported characters
A standard text message holds 160 characters in the GSM alphabet. As soon as one character falls outside that alphabet — an emoji, certain typographic quotation marks, an em dash, accented characters depending on the encoding — the message switches to Unicode and drops to 70 characters per segment. A text that "fitted" becomes a concatenated multi-part message, and a badly reassembled concatenation arrives truncated, or not at all.
A simple character counter avoids nasty surprises: the site offers one on the SMS character counter page. If you often write short, precise texts, a small pocket-size notebook is still surprisingly effective for pinning down the wording before you type it — you cross out, trim, reread.
5. The recipient's phone is unreachable
The network holds the message for a while in its service centre (the SMSC) and retries delivery. If the handset is switched off, out of coverage or out of storage for the whole validity period, the text is simply abandoned. You won't be told. The details of this mechanism are in what if the phone is switched off?
6. The recipient filters unknown senders
iOS offers filtering for unknown senders, Google Messages sorts and silences certain messages, and carrier apps add filters of their own. The message is then properly delivered, but tucked into a tab its recipient never opens. From your side: total silence, indistinguishable from a failure.
7. The gateway has hit a limit, or is no longer running
Free sending services apply quotas (per IP address, per day, per recipient number). Some shut down, switch aggregators, or suspend problem destinations. A service that worked six months ago may no longer serve France today, without announcing it.
8. You didn't send a text message, but an app message
A final, very common trap: you thought you were sending an SMS when your messaging app had switched to RCS or to an encrypted message. In that case, the message requires the recipient to use the same service. If they don't use it, or if their line isn't compatible, the send fails cleanly — and the sender shown is no longer an anonymous number, but an account.
How can I know whether my message arrived, while staying anonymous?
Honestly: you won't know for certain. That's the price of anonymity, and it's a rule to accept before writing, not after.
Three levels of information exist, from the most misleading to the most reliable:
| Indication | What it actually proves | Reliability |
|---|---|---|
| "Message sent" on the site or app | Your request was accepted by the gateway | Low |
| Network delivery report | The message reached the handset, not that it was read | Medium, often unavailable when anonymous |
| A reply from the recipient | The message arrived and was read | High — but requires a return channel |
So the only way to get real confirmation is to set up a reply route that doesn't reveal your number: a return number provided by the service, a secondary number, a dedicated inbox. The process is explained step by step in anonymous texts with replies: how does it work?
And no, read receipts aren't a workaround: they belong to instant messaging, not SMS, and they work both ways. The topic is covered in what the recipient of an anonymous text can see about you.
The checks to run, in order
Before concluding that you're facing an unsolvable technical problem, work through this list. It eliminates most avoidable failures.
- Reformat the number in the international format
+33+ nine digits, no spaces, no leading zero, and read it back digit by digit out loud. - Confirm it's a mobile (06 or 07 in mainland France, dedicated prefixes in the overseas territories).
- Count the characters and remove emojis, curly quotes and em dashes if you want to stay within a single segment.
- Strip out shortened links. They're an almost universal spam marker; a shortened link in an anonymous message is a one-way ticket to the filter.
- Don't send twice within the same minute. If you have to retry, wait, and don't rework the text substantially: a different text sent to the same number looks like a filter-evasion test.
- Check your own connection if you're using a website: an interrupted request can display an error even though the message has already gone out. A reliable USB-C wall charger prevents cut-outs mid-typing, which matters more than it sounds.
- Change method rather than insist: if one gateway refuses, a secondary number on an eSIM takes a completely different routing path. See dual SIM: a secondary number for writing discreetly.
- Reread the substance of the message one last time. A sending failure is sometimes an opportunity. The full list is in the 7 checks before you send.
What you absolutely must not do
Resend over and over
It's the most human reflex, and the most damaging. Technically, repetition triggers the filters. Legally, it changes the nature of what you're doing: article 222-33-2-2 of the French Criminal Code punishes harassing a person through repeated words or behaviour that degrade their living conditions, and repeated malicious calls or messages fall under article 222-16 (Légifrance). Anonymity offers no protection: in certain configurations, recent case law has even treated it as an aggravating circumstance. The framework is detailed in is it legal to send an anonymous text in France?
Switching senders to "get through"
Piling up services, numbers and variations of the text to get past a filter is exactly the behaviour anti-abuse systems are built to detect. And from the recipient's point of view, receiving the same message from four different sources is far more distressing than a single message.
Assuming a failure means "unread"
A send can fail after partial delivery. A message may have arrived and then been deleted. A message can be read on a lock screen without ever being opened — a topic we covered in what the lock screen reveals. Assume that any message whose sending was accepted has potentially been read, including the one whose tone you regret.
Calling to "check"
Making a withheld-number call on the back of an anonymous message that didn't go through turns a message into a persistent approach, and adds a call record at your carrier. If you're on the receiving end of this kind of combination, the stop being contacted page explains the options available.
What if I really need the message to arrive?
Then you have to accept a clear trade-off: delivery reliability and total anonymity are two conflicting goals. The more identifiable and compliant a sender is, the better it is routed. The less it is, the more it gets filtered.
Three reasonable compromises:
- Important message, anonymity desirable but not vital → a real secondary number (eSIM, second line) on a dual-SIM smartphone with eSIM support. Normal routing, identity separated from your main line.
- Important message, anonymity essential → a sending service with a reply route, a single message, plain wording, no links. And accepting the risk of non-delivery.
- Urgent message, someone's safety at stake → no anonymous channel at all. Call the emergency services or use the official schemes: in France, 17 for the police, 114 by text for deaf and hard-of-hearing people, 3018 for online violence, 3919 for violence against women.
For situations where you're on the receiving end — rather than sending — an anti-theft notepad, or simply an elasticated card folder to file dated screenshots, beats a scattered digital folder: the method is described in how to build solid evidence.
Frequently asked questions
My anonymous text says "sent" but doesn't arrive: why?
Because "sent" only means the gateway accepted your request. The rejection often happens further along, at the aggregator or at the recipient's carrier, which filters out unidentifiable senders without returning any reason.
Can you tell whether an anonymous text has been read?
No, not reliably. Read receipts belong to instant messaging apps, not SMS, and they require an identified account at both ends. The only real confirmation is still a reply from the recipient, through a return route that doesn't reveal your number.
Can the recipient block anonymous texts?
Partly. They can turn on unknown-sender filtering on iOS, let Google Messages sort suspicious messages, block a specific number, or ask their carrier about filtering options. What they can't do is block every message without a sender in advance.
Why doesn't #31# work for a text message?
Because the #31# prefix hides the calling number for a voice call only. A text carries its sender number in its headers: no carrier code removes it. For a message, you have to use a different sending channel.
Should I try again later or give up?
If the message is useful and one-off, a second attempt after a decent interval, with identical text and no links, is reasonable. Beyond that, persistence becomes both technically ineffective and legally risky. A message that won't go through is sometimes a message that was better left unsent.
Updated 4 November 2026. Carrier filtering rules, sending-service quotas and mobile system options all change: check the official Arcep and AF2M pages and your carrier's own pages before making any important decision.
