You asked a service to text you a code. Something went wrong — the code arrived too late, you mistyped it, the app rejected it, or no SMS came at all. Now you want another code on the same number.
TL;DR: It depends on the state your order is in right now. Resend requests another SMS through the number provider for that activation, and it only becomes enabled once an SMS has already been recorded on that order. If nothing has arrived, Resend stays visible but disabled. Once an order has finished, Reactivate is the route back to that number within SMSCode, on an eligible completed order, and it is a new paid order rather than an undo.
The confusing part is that the answer is not a property of the number. It is a property of the order, and the two most useful controls become enabled under opposite conditions.
Resend talks to the number provider, not to the app you are signing up for
When you press Resend, SMSCode sends a request to the provider that rented you the number, against that activation. It does not contact Google, WhatsApp, Telegram or whichever service you are registering with, and it cannot make that service compose a new message.
Two separate things therefore have to go right, and they belong to different parties:
- The destination service has to send something. That is triggered from inside that service’s own screen — its own “resend code” or “call me instead” option — and it is governed by that service’s rules.
- The provider has to deliver it to your rented number. That is the part Resend addresses.
Resend is only available at all once a prior SMS has been recorded on the order, and then only while the rental is live and unexpired and its cooldown has cleared. If nothing has been recorded yet, Resend stays disabled and the send has to be triggered from the destination service’s own screen instead. Where verification codes actually go covers how to tell when a service has sent a code somewhere other than SMS.
Resend and Cancel are never enabled at the same time
On a running order, both controls are shown. Which one is enabled depends on the conditions below; they are never enabled together. When the order ends, this action bar is no longer shown.
Resend becomes enabled only once an SMS has been recorded on the order. When that is the reason it is disabled, the button says so on hover: “Available after the first SMS.”
Cancel is enabled only while no SMS has been recorded, and only after a short opening period at the start of the order. Once a message is recorded, Cancel is disabled.
So:
- No SMS recorded yet → Cancel may be enabled; Resend is disabled.
- An SMS recorded → Resend may be enabled; Cancel is disabled.
On a running order, a disabled Resend can reflect no recorded SMS or an uncleared cooldown. Expiry or a terminal state also prevents resending; the action bar is hidden when the order ends.
If no SMS has arrived, work through this before spending again
There is no way to tell from the order record why a message has not appeared. The order shows eligibility and delivery, not the destination service’s reasoning. So rather than guess, work the sequence:
- Check where the service actually sent the code. Many services deliver to an in-app screen, an email, or a voice call instead of SMS — sometimes without saying so clearly. A code sent to a channel your rented number cannot receive will never appear on the order, no matter how long you wait.
- Trigger the send from the destination service’s own screen, if you have not yet. Nothing on the SMSCode side can originate that request.
- Give the current order its remaining time. The order page shows how long it has left. Waiting inside that window costs nothing.
- Check what your order actually offers right now. If Cancel is enabled and you have decided to stop, it is there. If it is not enabled, cancelling is not the available path and forcing a new order is a separate purchase, not a retry.
- If the result of any action is unclear, check the order state and your balance before pressing anything a second time.
The order record shows eligibility and delivery. It does not record why a destination service did or did not send, so it cannot tell you whether a different number or country would behave differently.
Four clocks, owned by two parties
People talk about “the timer” as if there is one. There are at least four, and they expire independently.
| Clock | Owned by | What it limits |
|---|---|---|
| Code validity | The destination service | How long the code you received still works |
| Retry cooldown | The destination service | How soon that service will issue another code |
| Resend cooldown | SMSCode | How soon the Resend button becomes enabled again |
| Rental window | SMSCode | How long your order holds the number |
Two are ours and two are not. The destination service’s two differ by service, country and sometimes account, and are not ours to state. For ours, act on what the order page displays: the point at which Resend becomes available again, and how much time the order itself has left.
This is why “wait an hour and try again” can fail: if a destination service asks you to wait longer than your order has left, that wait does not fit inside the order. The order’s own remaining time, shown on its page, is what governs — not a general rule of thumb.
What to do from your current state
| Your situation | What is enabled | What to do |
|---|---|---|
| Order running, no SMS yet | Cancel may be enabled; Resend disabled | Work the sequence above before buying again |
| Order running, an SMS arrived | Resend, once its cooldown clears | Re-enter the code you already have first; it may still be valid |
| Order running, SMS arrived, cooldown not clear | Resend visible, inactive | Act on the time the page shows |
| Order completed | Reactivate, if the order qualifies | A new paid order — see below |
| Order expired or canceled | Neither | A new order does not reserve or guarantee the previous number |
| Order completed, Reactivate absent | Neither | Support cannot reserve or force the same number either |
Reactivate is a new paid order, not an undo
When an order has finished, Reactivate may appear on its detail page. The name suggests restoration; it is not one.
Reactivate creates a new paid order for the same number, and the cost is shown before you confirm. It currently appears only on a completed order from one of our providers, so it will not be on every finished order. The documentation describes the action and its confirmation step.
The button appearing means your order is the right kind of order. Whether the number can still be supplied is checked at the moment you act, and that check can come back negative.
If a Reactivate attempt does not produce a working order, do not immediately press it again. A request can fail for more than one reason — the number may be genuinely unavailable, or the request may have failed in transit — and the outcomes are not the same. Check the order list and your balance first. If what happened is unclear, open a support ticket with the order ID rather than repeating the attempt blind; a ticket can have the record attached to it, and a blind repeat cannot.
Two situations worth walking through
Illustrative scenarios, not reports of real accounts.
Someone mistypes a code. A message arrives, the last digit is wrong, the service rejects it. The code itself may well still be inside its validity window, so the first thing to try is re-entering the code already visible on the order page. If it has genuinely expired, the order is eligible to request another only while the rental is live and unexpired and the cooldown has cleared — and a request is not a delivery: the destination service still has to originate a new SMS, and arrival is not guaranteed.
Someone sees nothing after several minutes. Resend is disabled, and pressing it is not the move. The sequence above applies: confirm the service actually sent to SMS at all, trigger the send from its screen, let the order’s remaining time run, and check what the order offers before buying another one.
An old message is not an answer to a new challenge
Two things get conflated here, and both cause real frustration.
A stored message is a record, not a live code. The SMS stays readable on the order page. But the code inside it was minted in response to one specific challenge. If the destination service has since issued a new challenge — because you pressed its resend, restarted the flow, or came back later — the older code may no longer match the current challenge. Some flows invalidate earlier codes when they issue a newer one, and others do not; what governs is the challenge the destination service is currently presenting. Being able to read an older message does not make its code the answer to it.
A delivered code is not acceptance. Receiving a code means a message reached the number. It says nothing about whether the destination service will accept the registration or keep the account afterwards; that decision is entirely theirs. The same distinction matters when a number arrives carrying an existing association, covered in a number that shows someone else’s WhatsApp.
What happens to the charge
The boundary is whether an SMS was delivered, not whether a code was successfully detected inside it.
An order that is canceled or expires with no SMS received returns its charge to your SMSCode balance automatically. If an SMS did arrive, the order counts as delivered even when no code could be parsed out of it. The FAQ states this directly: when a message arrives without a detected code, the content is still shown and the order is treated as delivered.
A worked example of where that matters: a service sends a confirmation sentence containing a word rather than a six-digit number. The message arrives and is readable on the order, but no code is detected in it. The order counts as delivered, because something did arrive.
The practical consequence: expect the charge to return when the message never came, not when the code was hard to read. If you believe an order’s charge is wrong, open a support ticket — order, payment and refund cases are handled there, because they need the order record attached.
Do not let a rented number become an account’s only way back in
A temporary number is rented for a window. It is not yours afterwards and it may be reassigned to someone else later. Whether that suits a one-time sign-up depends on the platform’s own rules and on what recovery you will need later. It is a problem if the number becomes the only route back into an account you care about.
Before you rely on a rented number for anything lasting, check what recovery methods the service itself offers, because they vary:
- Add a recovery email you control, where the service supports one, and confirm it works.
- Save the service’s own backup or recovery codes if it issues them — for many services these are the actual recovery path.
- Where the service offers an authenticator app, set it up. Note that an authenticator is a sign-in factor, not automatically a recovery method; whether it helps you regain access depends on that service’s rules.
- If the account matters long term, move its verification to a number you keep.
Receiving a code on a rented number today does not make that number a safe long-term anchor for the account.
Limitations of this guide
- The order record shows eligibility and delivery. It does not establish why a destination service did or did not send a message, and this guide does not speculate about that.
- Clocks owned by destination services change without notice. Nothing here is a promise about how long any external code or cooldown lasts.
- Whether a specific number can be re-obtained through Reactivate is checked live and cannot be predicted in advance.
- Interface labels and available actions can change. The order detail page and the documentation are authoritative; this guide describes them.
- Nothing here guarantees that a code will arrive, that a registration will be accepted, or that a number can be re-obtained.
FAQ
Why is Resend greyed out when I have not received anything?
On a running order, Resend becomes enabled only once an SMS has been recorded; when that is the reason it is disabled, its hover text says “Available after the first SMS”. An uncleared cooldown or an ended order also prevents resending, and the action bar is not shown after the order ends. To get a first message, trigger the send from the destination service’s own screen.
Does Resend make Google or WhatsApp send me a new code?
No. Resend is a request to the provider that rented you the number. Only the destination service can originate a new code, from its own screen.
Can I keep pressing Resend until something arrives?
No. Our resend cooldown limits how often it can be used, and the destination service enforces its own retry rules separately. The order page shows when Resend becomes available again.
The code arrived but the app says it expired. Can I get another?
Only if the rental is still live and unexpired and the cooldown has cleared; a recorded SMS makes the order eligible to request. Eligibility is not delivery — the destination service still originates the new message and arrival is not guaranteed. If the order has ended, you need a new order.
My Reactivate attempt did not produce a working order. What now?
Check your order list and balance before doing anything else, since a failed attempt and an unclear one are not the same thing. If the outcome is ambiguous, open a support ticket with the order ID rather than pressing Reactivate again.
My order expired without any SMS. Do I get the money back?
Yes — an order canceled or expired with no SMS received returns its charge to your balance automatically. If a message did arrive, even one with no detectable code in it, the order counts as delivered.
Can support send me another code manually?
Support cannot originate a code — that comes from the destination service — and cannot guarantee access to a particular number. What a ticket can do is investigate an order and the result of an action on it, which is why the order ID is the useful thing to include.