Why does Google say this phone number can't be used for verification?

It's rarely about the number itself. The two biggest drivers are how many accounts have already been created from your current network recently, and whether the number is VOIP/virtual rather than a real carrier-issued mobile number. Switching to a cleaner connection and a real mobile number fixes the large majority of cases.

Can I create a Gmail account without a phone number at all?

Google sometimes allows it depending on the signup's risk score, but it's not something you can reliably force — it isn't a setting you toggle. If you specifically want to avoid phone verification, Proton Mail is a more predictable path to a working inbox.

I retried the same number five times and it still fails — what am I doing wrong?

Nothing new, which is the problem: repeating the identical attempt feeds the same risk signal back in rather than correcting anything. Stop, change either the network or the number (ideally both), and don't attempt again for at least a few hours.

Is a VOIP number ever going to work for Gmail verification?

Sometimes, but it's inconsistent and depends on the specific provider and how heavily that number range has already been used for signups. A real mobile number clears far more reliably; treat VOIP as a fallback, not a first choice.

My new account got suspended within days of creating it. Why?

Heavy or unusual activity immediately after account creation is one of the clearest automation signals Google watches for. Let a new account sit and get used normally — a few genuine emails sent and received — before wiring it into other signups or high-volume use.

I just want an inbox to sign up for ChatGPT or Claude. Do I even need Gmail specifically?

No. Any mainstream provider works for that purpose, and Proton Mail in particular is accepted just as widely. The inbox is only step one — the part that actually stops most people at that stage is paying with a card the platform's checkout will accept, which is a separate problem from which email provider you pick.

EmailUpdated 2026-10

Gmail Phone Verification Not Working? How to Create a Clean Google Account (2026)

"This phone number can't be used for verification" on a new Gmail signup usually isn't about your number at all. Here's what actually trips the check, the fixes that work, and what to try if you're already stuck.

TL;DR: When Google rejects your phone number or refuses to finish creating the account, it's almost never the number itself — it's a signup-risk score. The three things that actually move that score: ① how many accounts have already been created from the same network exit recently (this is the biggest single factor); ② whether the number is a VOIP or virtual line rather than a real mobile number (Google filters these hard, and a real one clears in seconds); ③ switching networks mid-signup, which looks like automation even when it isn't. Fix in order: use one stable connection for the whole signup, use a real mobile number if you can borrow or buy one, and don't create a second account from the same place right after the first. If you're already stuck after a few tries, stop retrying — repeated failures raise the same score you're trying to clear — and either wait it out on a different day, or use Proton Mail instead, which is accepted just as widely for signing up to AI tools and other global SaaS. Getting the inbox is only step one, too: most people who hit this wall are trying to register for ChatGPT or Claude, and the harder problem — a card those platforms will actually accept — is still ahead.

1. "Can't be used for verification" is a risk score, not a number check

Google doesn't maintain a simple blocklist of phone numbers. What's actually running is a signup-risk model, and the phone-verification step is where it shows its answer. That's why the same number can work for one person and fail for another, and why retrying the identical number rarely helps — you're not correcting an error, you're feeding the same signal back in. The number itself is one input among several; the network you're signing up from and the pattern of the signup matter at least as much.

2. The single biggest factor: how many accounts came from your network exit

If several Google accounts have already been created recently from the same IP or network exit, the next signup starts with a strike against it before you type anything. This is common on shared connections — office networks, hostel wifi, a VPN endpoint other people also use — where you have no way of knowing how many other signups already happened there. If you don't control the network, you can't fully control this variable, which is exactly why switching to a connection you know is clean (a home line, a mobile hotspot on your own SIM) fixes signups that otherwise fail for no visible reason. This is also why advice like "just use a different browser" or "clear your cookies" rarely helps on its own — those change fingerprints the model may glance at, but they don't touch the one signal doing most of the work, which lives at the network level rather than the device level.

3. Why a real mobile number clears faster than a virtual one

Google's verification system treats VOIP numbers, virtual lines, and numbers from SMS-relay services as materially higher risk than a real carrier-issued mobile number, and it says so indirectly through higher decline and non-delivery rates rather than an explicit warning. If you have any real mobile number available — your own, a second SIM, a trusted friend's for one code — using it is the highest-leverage single change you can make. A relay or virtual number might work; a real one usually just works, on the first try.

4. Registering cleanly, step by step

Pick one stable connection before you start and don't change it until the account exists. Go to accounts.google.com, choose Create account, and fill in the form completely and accurately — inconsistent or obviously fake-looking details add their own small risk signal. When asked for a phone number, use the most "real" one available to you. Enter the code as soon as it arrives rather than letting the session sit idle. Do the whole thing in one sitting: opening the flow, stepping away, and returning later (possibly from a different network, if you're on mobile data that reassigns an address) is itself a pattern the risk model notices.

5. If you already got flagged or suspended

Don't retry the same number and network combination immediately — that repeats the exact pattern that got flagged. Google does have an appeals flow for suspended accounts (search "Google account recovery" and follow the prompts, providing the phone number and device details used at signup), and it does restore some accounts, but it isn't fast or guaranteed. The more reliable move if you're on a deadline is to start fresh on a genuinely different connection and number rather than waiting on an appeal for an account you need today. Either way, treat this as a signal to slow down on the next attempt, not to retry faster — the accounts that eventually succeed are usually the ones created a day or two later, not the ones created five minutes after a rejection.

6. If you'd rather not fight it: Proton Mail

If Gmail keeps rejecting you or you'd simply rather not deal with phone verification at all, Proton Mail is a fully workable substitute for the actual goal most people have here — an inbox to register other services with. It's accepted just as widely as Gmail by ChatGPT, Claude, and the large majority of global SaaS signups, it can run alongside an existing Gmail account rather than replacing it, and its own signup is generally lighter-touch on phone verification. Switching to it isn't a downgrade for this use case; for a lot of people it's simply less friction.

7. The email was step one — payment is the wall most people hit next

Getting a working inbox feels like the hard part, but for most people signing up specifically to use ChatGPT, Claude, or Midjourney, it's actually the easy part. Those platforms bill through card networks that check the issuing country of the card (the BIN), not where you're physically located or what currency you have — a card issued in a country their checkout doesn't accept gets declined regardless of the balance on it. That's a separate, unrelated system from the email/phone check you just cleared, and it trips up more people than the Gmail step does. It's worth knowing this before you spend an evening on the inbox: solving verification and then immediately hitting a checkout decline on the same day is common enough that it's worth planning for both steps up front rather than treating the email as the finish line.

8. Getting past the payment wall once your inbox is sorted

Two practical routes once you have your account and hit a payment wall. If you want to keep paying the platform directly on its own checkout page, you need a card whose issuing country it accepts — a US-issued virtual Visa is the common fix, and services like cocodot issue one for a flat $9.9 funded from a balance you can top up locally, no US bank account required. If you mainly want the underlying model working in your own code or in a tool like Claude Code rather than a subscription in a browser tab, an OpenAI-compatible relay you can fund directly skips the card question entirely — you change a base_url instead of solving a payment problem. Either way, that's a separate decision from the one this page is about; solve the inbox first, and come back to the card question once you actually need it. Whichever route you eventually take, test it with a small amount before committing anything larger — a $5 or $10 first attempt tells you whether the specific merchant accepts the card long before a full month's subscription is on the line.

What you're seeing → what it actually means → what fixes it

What you see	Real cause	Fix
"This phone number can't be used for verification"	Number is VOIP/virtual, or already tied to too many accounts	Use a real mobile number you haven't used for signups before
Verification code never arrives	Some carriers/VOIP routes get silently deprioritized	Try a different real mobile number rather than resending
"We couldn't create your account" after filling in everything	Too many signups already seen from this network exit	Switch to a different, less-shared connection; space out attempts by a day
Asked to verify identity mid-signup	Network or region changed partway through	Restart on one connection and finish in a single sitting
New account works fine, then gets suspended within days	Heavy activity right after creation reads as automated	Use the account normally for a few days before wiring it into anything else
Nothing above works	—	Use Proton Mail — it's accepted just as widely for AI tool and SaaS signups