The confirm button stays locked
The countdown seems never to end.
The 60-second delay before each send is counted on the server, not in your browser. That is what makes it reliable, and it also explains the cases where it looks stuck: the browser shows a counter, but the server decides.
The causes, from most to least common
- 1
The delay has not elapsed server-side yet
The display may have run a second ahead of the server. The button unlocks as soon as the server considers the delay over, never before.
- 2
The page was reloaded
Reloading speeds nothing up and can void the current authorisation. The counter then restarts from zero on a new request.
- 3
The authorisation expired
A confirmation left open too long eventually expires. You then have to start again from the form.
- 4
Cookies are blocked
The authorisation is carried by a signed cookie. If your browser refuses the site's cookies, the server cannot recognise your request.
What to do
- 1
Wait a few more seconds
Leave the page open without reloading: the button unlocks on its own at the end of the real delay.
- 2
Do not reload the page
It is the most common reflex and the most counterproductive: it cancels the wait already elapsed.
- 3
Start again from the form if the authorisation expired
Begin from the home page rather than reusing a tab left open.
- 4
Allow the site's cookies
The cookie used only carries the sending authorisation; without it, confirmation cannot complete.
Frequently asked questions
Why does this 60-second delay exist?+
It limits automated bulk sending and gives you time to reread the number and the message before they go out.
Can the wait be shortened?+
No. The delay is verified by the server, which makes it independent of anything happening in the browser.
Envoyez votre SMS gratuitement
Service 100% gratuit et sans inscription. Envoyez vos SMS vers la France en quelques secondes.
Envoyer un SMS