What happens when Google Voice takes your number back

What counts as using the number

Google's help page lists the activities that keep a Voice number attached to your account. There are three of them, and they are all things you do outward (Google):

• “Make a call”
• “Send a text message with your Voice number”
• “Listen to your voicemail”

Receiving a text is not on that list. Neither is receiving a call. Keep a Voice number only so codes can arrive on it, and by Google's own description the number is idle. How much traffic reaches it makes no difference.

The part Google does not publish

The obvious next question is how long you have. Google's page does not answer it. It describes the warning you get: a notice that “your Voice number will be removed from your account”, carrying “the reclaim date, which is the date the number will be removed”. It names no period of inactivity anywhere.

Where the 90-day figure comes from

The figure does circulate, and it has a traceable origin. In Google's own Voice Community, a volunteer badged Diamond Product Expert answered someone who had just lost a number they had used for ten years. That answer states the rule Google's help page leaves out (Google Voice Community, 17 June 2025):

• Bluescat, Diamond Product Expert

  “You must do this at least once in a rolling three month (90 day) period.”

  https://support.google.com/voice/thread/351418232/

• Bluescat, Diamond Product Expert

  “Passively receiving no-answer calls, or receiving text messages, doesn't prove active use; a dead person's number could still be receiving junk calls or texts.”

  https://support.google.com/voice/thread/351418232/

The same answer defines active use as one outbound call, one sent text, or answering an inbound call “for at least several minutes”, and describes three emails: a first warning after 60 days of inactivity, a second three weeks later, and expiry at 90 days. That is the clearest account of the timer anyone has published.

Getting it back

There is a recovery window, and it starts at the reclaim date rather than at the warning:

1. 01Google sends the notice, naming the reclaim date.
2. 02On the reclaim date the number leaves your account.
3. 03“After the reclaim date, you have 45 days when you can get your Voice number back.”
4. 04“Voice numbers must be added back within 45 days.” After that Google's page stops describing anything.

One detail decides how bad the first week is. Google says that “After your number is reclaimed, your messages are still in your Voice account, but you can't get calls or texts” (Google). Your history survives. Delivery does not. So you can still read the codes that arrived last month, and no new code will ever reach you again. Nothing in your account looks broken, which is why people usually find out from a login screen rather than from Google.

Google's page does not say what becomes of the number after those 45 days. We cannot tell you whether it returns to a pool for someone else. Anyone stating that confidently is filling the gap themselves.

The day it's gone: what to do, in order

The number is reclaimed and the 45 days have started. The order matters more than the speed, because the wrong order is how people end up locked out of the account they were trying to protect.

1. 01Try to add the number back first, before touching anything else. It is the only step with a deadline on it. If it works, nothing else on this list is needed.
2. 02Write down every account that texts that number. Bank, brokerage, email, tax login, marketplace seller account, the delivery app you forgot about. You will not remember them all; work through your password manager rather than your memory.
3. 03Start with the accounts you can still get into. While a session is still valid on your laptop, change the phone number from inside the account. This is the window that closes on its own when a session expires.
4. 04Do the ones with a second factor that isn't a phone next. An authenticator app, a passkey, a security key or printed backup codes will get you in without the number. For a Google account itself, Google publishes both backup codes and recovery options.
5. 05Leave the circular ones for last, and expect them to take days. Those are the accounts that will only let you change the number after texting a code to the number you no longer have. They need support, identity documents and patience.
6. 06Replace the number before you re-point anything. Moving ten accounts to a second number you also do not control just moves the problem. Decide what the number is going to be first.

Moving the number out before it's reclaimed

If the number matters, the durable fix is to stop it being a Google Voice number. Google publishes the route on its porting page: “To port your number out of Google Voice, first you need to unlock the number. Then, let your carrier know you want to port a number to their service. Work with them until the porting process is complete.” (Google)

1. 01Unlock the number. “When you unlock your Google Voice number, it costs $3 USD. But if your number was originally ported in from another carrier, there's no charge.”
2. 02Ask the receiving carrier to port it in. Google's instruction is to work with them until it completes, and not to delete the Voice number meanwhile: “Do not delete the Google Voice number once it's initiated with your gaining carrier.”
3. 03Give them the credentials Google specifies. “If your carrier asks for your account number and PIN, provide your 10-digit Google Voice phone number and the PIN you use to access your Google Voice voicemail.”
4. 04Allow time. “Phone numbers can take up to 48 hours to port.”

Three dollars and an afternoon buys the digits back onto a carrier, where no activity rule applies. That is a better deal than most people realise, and it is worth doing before a reclaim date rather than after one, because the port needs the number to still be yours.

Why this lands hardest on a codes-only number

Two facts compound. Receiving is not activity. And a Voice number is classified as VoIP, so a good share of services refuse it for verification. How line type decides what a service accepts covers the mechanism, Google Voice for verification codes covers that case, and what each service actually publishes is the dated record of who has a rule and who only has a habit.

So the number is both the most likely to be rejected at sign-up and the most likely to go quiet enough to be taken away. Losing it is worse than losing an unused number. Every account still pointing its two-factor at it needs updating. Some of those accounts will send a code to the number you no longer have before they let you change it.

Keeping one alive, if you want to

The rule is satisfiable. Place a short call, send one text, or listen to a voicemail from time to time, and the number stays. Be honest about the deal. You are setting a recurring chore against a date Google has not told you, for a number many services will not accept anyway.

The alternative, stated plainly

A Cleat line is a real US mobile number rather than an internet one. It is yours for as long as you pay for it. There is no activity requirement. If you cancel or a payment fails, the number is held for 30 days before it is released. It receives texts and transcribed calls. It cannot send texts or reach 911. Cleat Line cannot place calls; Cleat Full adds them in the web app.

Be clear about what it is not. It is a new number, not your old one: Cleat cannot port a Google Voice number in, and you do not choose the area code. If the whole point is keeping the digits your family already has, the $3 port-out above is the answer and Cleat is not. If the point is that codes have to arrive somewhere you control, read on.

It costs $24.99 a month. That is the real difference: Google Voice is free, and the reclaim rule is part of what free means. The full comparison puts the two side by side. Keeping a US number when you move abroad weighs the porting options against each other, and what people actually use a US number for is the better read if you are still deciding.