// FAQ
Why a countdown before sending?
This short delay isn't sluggishness: it's a safeguard.
A 60-second delay precedes the confirmation. It prevents accidental sends and curbs automated or abusive uses of the service.
A brief countdown separates confirmation from the message actually leaving. It regulates the pace of sending and makes automated use of the service considerably harder.
The answer in detail
Without a delay, a script could fire off hundreds of messages in seconds — an open door to spam and harassment. The countdown enforces a human pace and makes those bursts impractical.
For a legitimate send, the impact is minimal: a few seconds' wait, just enough time to reread your message. It's a deliberate trade-off between smoothness and protecting the ecosystem.
This mechanism adds to other anti-abuse limits. The goal is constant: keep the service free and open without turning it into a tool for mass nuisance.
Real-world examples
›Reread before it goes
The countdown gives you time to fix a typo or a number before the message leaves.
›Blocking bots
An automated send running in a loop hits this delay and can't flood the gateway.
Key takeaway
A short delay that curbs automation and abuse, without getting in the way of a normal send.
Related questions
All questions// Anonymous SMS · Hidden number · To France
Envoyez votre message, gardez l'anonymat
Votre numéro reste masqué, aucune inscription, aucune trace. Rédigez, confirmez, et votre SMS part de façon totalement anonyme.
Envoyer un SMS anonyme