{"id":11237,"date":"2026-05-28T12:18:19","date_gmt":"2026-05-28T06:48:19","guid":{"rendered":"https:\/\/www.techrounder.com\/blog\/?p=11237"},"modified":"2026-05-28T12:18:39","modified_gmt":"2026-05-28T06:48:39","slug":"perplexity-says-this-phone-number-cant-be-used-for-verification-heres-whats-actually-going-on","status":"publish","type":"post","link":"https:\/\/www.techrounder.com\/blog\/perplexity-says-this-phone-number-cant-be-used-for-verification-heres-whats-actually-going-on\/","title":{"rendered":"Perplexity Says This Phone Number Can’t Be Used for Verification – Here’s What’s Actually Going On"},"content":{"rendered":"

If you’ve been staring at the message “This phone number can’t be used for verification. Please try a different number”<\/em> on Perplexity’s login or verification screen, you’re probably frustrated \u2014 and rightfully so. Especially if this is a number you’ve been using for years, on every platform, without a single issue.<\/p>\n

Let’s break down what’s actually happening, why it happens to completely normal, legitimate phone numbers, and what you can do about it \u2014 including a few real-world situations where people have run into the exact same wall.<\/p>\n

First, Let’s Set the Record Straight: It’s (Almost Certainly) Not Your Fault<\/h2>\n

This is the most important thing to understand before you spiral into thinking your number is banned or something is wrong with your account. In most cases, this error has nothing to do with anything you did. It’s not a security flag on your Perplexity account. It’s not your phone carrier blocking anything. And it’s definitely not a sign that your number is broken.<\/p>\n

What’s actually happening is that Perplexity \u2014 like most modern platforms \u2014 doesn’t handle SMS verification in-house. They outsource it to a third-party service. Companies like Twilio, Sinch, Vonage,<\/strong> or similar providers handle the actual sending of OTP codes. These services maintain their own internal databases of phone numbers they consider “high-risk” and will quietly refuse to send messages to them.<\/p>\n

The problem? These databases are far from perfect. False positives happen all the time.<\/p>\n

Why Perfectly Normal Numbers Get Flagged<\/h2>\n

There are a few common reasons a legitimate number ends up on one of these block lists:<\/p>\n

1. Regional or Carrier-Based Filtering<\/h3>\n

Certain countries and certain mobile carriers are disproportionately represented in spam or fraud patterns \u2014 not because the users are bad actors, but because bad actors in those regions used similar number ranges. SMS verification services sometimes apply broad regional filters as a lazy risk-reduction measure. Indian numbers, especially from smaller operators or specific number series, are known to get caught in these filters regularly.<\/p>\n

Real example:<\/strong> A developer from Bengaluru reported on a Reddit thread that his Airtel number worked fine on Uber, Amazon, and WhatsApp, but was flagged as “undeliverable” when he tried to verify on a US-based SaaS platform. The platform’s support team confirmed it was a Twilio-side filter on his number prefix, not anything specific to his account.<\/p>\n

2. VoIP Misclassification<\/h3>\n

Some carrier numbers \u2014 particularly from newer telecom players or numbers ported between carriers \u2014 can be misidentified as VoIP (Voice over Internet Protocol) numbers. VoIP numbers are often used by spammers and fraudsters, so many SMS services block them by default. If your number was ported, or if your carrier uses certain infrastructure, it might get misclassified.<\/p>\n

Real example:<\/strong> A UK user who had ported her number from EE to a smaller MVNO found that her number was suddenly rejected by three different platforms for SMS verification. None of them gave her a clear explanation. The culprit was her number being re-registered in a VoIP-adjacent number block after the port.<\/p>\n

3. Shared Block Lists Across Platforms<\/h3>\n

These SMS vendors share risk data. If a number was associated with abuse on one platform \u2014 even if it wasn’t your number at the time, or even if the previous user of the number was the problem \u2014 that flag can follow the number across different services and platforms. Phone numbers get recycled by carriers all the time. Someone before you might have burned it.<\/p>\n

Real example:<\/strong> A freelancer in Lagos got a new SIM card, only to find that within days, the number was being rejected by several platforms for verification. After some digging, he found out the number had been deactivated by his carrier and reissued to him. The previous owner had apparently used it in a fraudulent account somewhere, and the block had never been lifted.<\/p>\n

4. No OTP \u2192 Then Suddenly This Error<\/h3>\n

This is a pattern many people experience \u2014 including possibly you. First, the OTP just doesn’t arrive. You try a few times. Then suddenly, you start seeing the “can’t be used for verification” error. What happened?<\/p>\n

Most likely, the SMS service flagged your number after repeated failed delivery attempts. It interpreted the failed sends as a signal that the number is inactive or problematic, and escalated the block. So ironically, trying too many times can make things worse.<\/p>\n

The Revolut Metal + Perplexity Pro Angle Makes This More Urgent<\/h2>\n

Here’s a wrinkle that makes this situation particularly unfair: if you’re accessing Perplexity Pro through a bundled subscription \u2014 like the one that comes with Revolut Metal \u2014 you’re paying for this indirectly whether you want to think of it that way or not.<\/p>\n

Revolut Metal isn’t cheap. It’s a premium plan that bundles several services together, and Perplexity Pro is one of the selling points. If a verification bug is locking you out of that service, you’re effectively not getting what you’re paying for.<\/p>\n

This matters because it changes who you should be contacting and how you should frame the problem.<\/p>\n

What You Should Actually Do (Step by Step)<\/h2>\n

Step 1: Push Harder on Perplexity Support<\/h3>\n

If you’ve already submitted a support ticket and received an automated response, don’t just wait. Reply to the thread \u2014 even if it looks like a bot replied \u2014 and be very specific. Don’t just say “I can’t verify my number.” Say something like:<\/p>\n

\n

“My phone number is being rejected with the error ‘This phone number can’t be used for verification.’ I have been using this number for over 20 years and it works on all other platforms. My account is linked to a Revolut Metal subscription which includes Perplexity Pro. I need my number whitelisted or an alternative verification method provided, as I have no other number to use.”<\/p>\n<\/blockquote>\n

The more specific you are, the faster a real human escalates it. Vague tickets get slow responses. Specific tickets with subscription context get treated differently.<\/p>\n

Step 2: Contact Revolut Support Too<\/h3>\n

This might feel counterintuitive \u2014 Revolut didn’t cause the bug. But here’s the thing: Revolut has a business partnership with Perplexity. They’re sending customers Perplexity’s way as part of their Metal benefits. If those customers can’t access the product, it reflects on Revolut too.<\/p>\n

Contact Revolut support and frame it exactly like this: “One of my Metal plan benefits \u2014 Perplexity Pro \u2014 is inaccessible to me due to a phone verification error. This has been going on for two weeks. Can you escalate this to your Perplexity partnership contact?”<\/em><\/p>\n

Revolut has dedicated partnership channels that regular users don’t. A complaint routed through them can sometimes get resolved faster than going through Perplexity’s public support queue.<\/p>\n

Step 3: Try Activating Through the Revolut App Flow<\/h3>\n

Some bundled subscription benefits can be activated through the partner’s app integration \u2014 directly from inside the Revolut app \u2014 rather than going through Perplexity’s own login and verification flow. This sometimes bypasses the phone verification step entirely because authentication is handled via Revolut’s OAuth rather than Perplexity’s SMS system.<\/p>\n

Check your Revolut app under Benefits<\/strong> or Explore<\/strong> and see if there’s an activation link for Perplexity. If there is, try accessing it fresh from there.<\/p>\n

Step 4: Ask Explicitly for Email-Only Verification<\/h3>\n

When you write to Perplexity support, specifically ask whether they can offer an alternative verification method \u2014 such as a magic link sent to your email, or manually verifying your account on their end given the circumstances. Some platforms do this as an exception for users who are clearly legitimate and have a documented issue with SMS.<\/p>\n

Step 5: Check What Kind of Number You Have<\/h3>\n

It might be worth knowing whether your number is on a network that’s commonly misclassified. If you’re on BSNL, a smaller regional operator, or a number that was ported from one carrier to another, mention this explicitly to Perplexity support. It gives their technical team a starting point to investigate the block on the SMS vendor’s side.<\/p>\n

What You Should NOT Do<\/h2>\n
    \n
  • Don’t keep trying the same number repeatedly<\/strong> \u2014 extra failed attempts may deepen the block, not fix it.<\/li>\n
  • Don’t use a friend or family member’s number<\/strong> \u2014 you shouldn’t have to, and it could cause complications for them later.<\/li>\n
  • Don’t assume waiting will fix it<\/strong> \u2014 these blocks don’t expire on their own. Someone has to actively whitelist the number or adjust the verification flow.<\/li>\n
  • Don’t jump to buying a new SIM<\/strong> \u2014 a new number might face the same regional filter if it’s in the same operator block.<\/li>\n<\/ul>\n

    A Note on How Common This Actually Is<\/h2>\n

    This problem is more widespread than most people realise, because it tends to happen silently and the error messages are deliberately vague. Platforms don’t want to explain their fraud-filtering logic publicly, so users are left confused.<\/p>\n

    It’s happened with Google accounts, WhatsApp verifications, Discord signups, and a long list of SaaS tools \u2014 often to people in South Asia, Southeast Asia, parts of Africa, and Eastern Europe where number recycling and certain carrier types are more common. It’s a systemic flaw in how SMS-based verification is implemented globally, and individual users end up bearing the burden of it.<\/p>\n

    The fix almost always comes from the platform’s side \u2014 either by whitelisting the number manually, switching SMS providers, or offering alternative verification. You can’t solve this from your end. What you can<\/em> do is make sure the right people know about it and feel enough pressure to actually do something.<\/p>\n

    Final Thought<\/h2>\n

    If you’ve been using a phone number for two decades without a single issue anywhere, and suddenly one platform won’t accept it \u2014 the problem is the platform’s verification system, not your number. Stay firm in your support communications, loop in Revolut as a second pressure point, and ask specifically for a manual resolution. You’re entitled to the service you’re paying for, and this is a solvable problem \u2014 it just needs the right person on their end to look at it.<\/p>\n

    Hopefully this gets resolved quickly. And if you’ve been through something similar and found a fix that worked, it’s worth leaving it in the comments \u2014 you’d be helping more people than you think.<\/p>\n","protected":false},"excerpt":{"rendered":"If you’ve been staring at the message “This phone number can’t be used for verification. Please try a…","protected":false},"author":2,"featured_media":11238,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_display_header_overlay":false,"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","csco_post_video_location":[],"csco_post_video_location_hash":"","csco_post_video_url":"","csco_post_video_bg_start_time":0,"csco_post_video_bg_end_time":0,"csco_post_video_bg_volume":false,"footnotes":""},"categories":[82],"tags":[],"class_list":["post-11237","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ai","cs-entry","cs-video-wrap"],"_links":{"self":[{"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/posts\/11237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/comments?post=11237"}],"version-history":[{"count":4,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/posts\/11237\/revisions"}],"predecessor-version":[{"id":11242,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/posts\/11237\/revisions\/11242"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/media\/11238"}],"wp:attachment":[{"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/media?parent=11237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/categories?post=11237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.techrounder.com\/blog\/wp-json\/wp\/v2\/tags?post=11237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}