Does Google Voice Work for SMS Verification?
You have a Google Voice number, it's free, and it receives texts perfectly well from your friends. So when a signup form asks for a phone number, it's the obvious thing to type — and then either nothing arrives, or the form refuses it outright.
The short answer to does Google Voice work for SMS verification: sometimes, unpredictably, and less often every year. Some major platforms now block it by name in their published documentation. Others accept it silently and then never deliver the code. This article separates the four distinct ways it fails, shows which platforms have said so officially, and explains what the reliable alternative actually is.
Why Google Voice fails SMS verification: it's classified as non-fixed VoIP
Google Voice isn't a mobile carrier. It's a VoIP service — your number lives on Google's servers and forwards to whatever device you've linked. That distinction is invisible to you and completely visible to any website that cares to look.
How visible? Twilio's Lookup API — the tool a very large share of the internet uses to screen phone numbers — has a category called nonFixedVoip, and its official documentation defines it as "a virtual phone number obtained online without requiring a physical device." The example it gives, in the docs themselves, is Google Voice. Google Voice is not an edge case that slips through the classifier; it is the textbook illustration of the category the classifier exists to catch.
That check costs about eight-tenths of a cent and returns in milliseconds, before any code is generated. If you want the full mechanism — which databases get queried and why the result is so consistent — see how websites detect VoIP numbers. The background on the underlying distinction is in VoIP vs non-VoIP numbers.
The four separate ways Google Voice fails
People tend to lump these together as "it didn't work." They're different problems with different tells, and only one of them is really about VoIP detection.
- You can't get the number in the first place. Setting up Google Voice requires an existing phone that can receive a text — Google's own setup guide says to "make sure that your phone is on and can get texts," because it sends a code to verify you. If you're outside the US and don't already have a US mobile number, this is a wall before you start. Personal Google Voice is US-only; the paid Workspace tiers are the only route abroad.
- The form rejects the number instantly. This is the line-type check. No code is sent, the refusal is immediate, and no amount of retrying changes it — the classification is a property of how the number is provisioned, not a setting you can flip.
- The form accepts it and the code never arrives. This is the short-code problem, and it's the one most people misdiagnose. Verification codes usually come from 5- or 6-digit short codes, and short-code delivery to Google Voice has been unreliable for years. Google's own support forums are full of threads with titles like "Unable to Receive Any Short Code SMS (Bank, Walmart, Instacart, etc.)". Your friends' texts arrive fine because those come from ordinary 10-digit numbers over a different delivery path.
- It works — and then you lose the account months later. Google reclaims Voice numbers that go unused. Users routinely report emails reading "Your Google Voice number will expire in 30 days." If that number is the recovery method on an account you care about, losing it can mean losing the account. This is the failure mode nobody plans for, and it's the strongest practical argument against using Google Voice for anything you need long-term.
Which platforms accept Google Voice
Below is where things actually stand. "Blocked (documented)" means the platform's own published help pages say so — not a forum rumour.
| Platform | Status | What's actually going on |
|---|---|---|
| ChatGPT / OpenAI | Blocked (documented) | OpenAI's help centre has an article specifically about this. Its wording: "We do not support use of landlines, VoIP, Google Voice, or premium numbers at this time." Google Voice is named outright. |
| Discord | Blocked (documented) | Discord's phone-errors article instructs users to "make sure the phone number is not associated with a landline or VOIP device, and that the number you are trying to use is associated with a mobile device." |
| A new Google Account | Blocked (documented) | Google refuses its own product. The error is explicit: "This phone number can't be used to verify a new account because it's managed by Google." |
| Telegram | Blocked in practice | Widely reported to reject VoIP ranges. Typically no error — the code simply never sends. |
| PayPal and most financial services | Blocked in practice | Financial platforms screen hardest, and many also send from short codes, so you can hit failure modes 2 and 3 at once. |
| Inconsistent | Sometimes registers, sometimes doesn't. Not something to rely on for an account that matters. | |
| Banks, retailers, delivery apps | Usually fails at delivery | Almost all use short codes. The form often accepts the number and the code never lands — the most confusing failure of the set. |
| Ordinary person-to-person texting | Works fine | This is what Google Voice is built for, and it does it well. |
Note the pattern in that table: the blocks aren't random. They cluster on platforms with real fraud exposure — AI services, financial accounts, messaging apps. Google Voice remains genuinely good at being a second number for calls and texts with people. It's specifically the verification job it's bad at.
Things that don't help
A few fixes circulate constantly and are worth ruling out before you spend an evening on them.
- Picking a different area code. A Google Voice number with a 212 or 415 prefix is still Google Voice. Platforms read the line type and carrier, not the geography.
- Enabling call forwarding to a real mobile. The forwarding destination doesn't change what the number is. The lookup runs against the Voice number you typed.
- Requesting a voice call instead of a text. Occasionally useful — some services will read the code aloud, and that path avoids the short-code problem entirely. But platforms that block VoIP at the line-type check block it for calls too, so this only helps with failure mode 3.
- Porting the number to a mobile carrier. Porting is possible in principle, but the number's provider history follows it in the portability records, and you've now paid money and waited days for something that may still screen badly.
- Upgrading to Google Workspace Voice. Starter is $10 per user per month, Standard $20, Premier $30. It's a real business phone system and worth the money for that purpose — but it's still VoIP, and it will still be classified as VoIP.
What to use instead
If your goal is a legitimate signup while keeping your personal number private — which is a completely reasonable thing to want — the requirement is a number that is actually carrier-backed rather than one that hopes to pass as such. That means a real mobile line, on a real network, that returns mobile when the platform runs its lookup. Nothing is being disguised; there's simply nothing to catch.
That's the whole idea behind a non-VoIP number. It sidesteps all four failure modes at once: it exists without needing another number to bootstrap it, it passes the line-type check on its merits, it receives short codes like any phone, and it doesn't quietly expire out from under an account you rely on.
Free public receive-SMS sites are worth avoiding too, and for a different reason: they're shared, so the number is already registered on every major platform and carries whatever abuse history the last hundred users left on it. You inherit that score.
Frequently asked questions
Can I use Google Voice for two-factor authentication on an account I already have?
Technically often yes, but think hard about it. Google Voice reclaims unused numbers, and short-code delivery is unreliable — so the day you actually need that code to get back into your account is precisely the day the weakness shows up. Use an authenticator app for 2FA where the option exists.
Why do my friends' texts arrive but verification codes don't?
Different delivery paths. Person-to-person texts come from standard 10-digit numbers. Verification codes overwhelmingly come from 5- and 6-digit short codes, and short-code routing to Google Voice has been patchy for years. Both can be true at once.
Is there a way to check whether a number will be rejected before I try?
Yes — free carrier-lookup tools run the same query a signup form does. Enter the number in E.164 format (+15551234567) and read the line type field. If it says non-fixed VoIP, expect trouble. More detail in why phone numbers get rejected for verification.
Is Google Voice getting worse for this over time?
Yes, directionally. Cheap, accurate line-type screening has become standard infrastructure rather than a specialist tool, so platforms that once didn't check now do. Anything you read from a few years ago describing Google Voice as a dependable verification number is out of date.
The short version
Google Voice works for SMS verification on a shrinking list of sites and fails on most of the ones people actually need. It's classified as non-fixed VoIP — Twilio's documentation literally uses it as the example — and OpenAI, Discord and Google itself all reject it in writing. On top of that sits a separate short-code delivery problem and a real risk of the number being reclaimed. As a free second line for talking to people, it's a fine product. As a verification number, it's a coin flip that keeps getting worse odds.