What Google’s New RCS Call Verification Actually Does
Google’s new RCS call verification is an Android feature that silently confirms the identity of incoming callers over an encrypted channel so that spoofed numbers and AI-generated voice scams are blocked or flagged before you pick up, giving smartphone users proactive protection instead of relying only on spam filtering after a call starts. Unlike traditional phone security, this system works app-to-app rather than through carriers. When a call comes in from someone in your contacts, Google Dialer, Messages, and Contacts coordinate to check that the other device responding on that number is the real one. If an attacker spoofs the caller ID or uses a deepfake voice, they are unlikely to pass the encrypted check. The result is a tighter link between phone numbers and real devices, tailored for today’s AI scam landscape.
How RCS-Based Caller Authentication Works Under the Hood
The system builds on RCS, the richer messaging standard Google already uses in Messages. When you receive a call from a saved contact, your phone initiates a quiet RCS conversation with the caller’s device in the background. Over this encrypted link, it sends a confirmation signal: in effect, “Is this phone really the one behind this number?” Only the genuine device, signed into the correct Google apps, can respond correctly. Android Authority explains that “even if someone’s able to spoof the incoming number, or maybe even use an AI tool to fake the caller’s voice, they wouldn’t be able to successfully respond to that encrypted RCS authentication step.” This is different from network-level tools like STIR/SHAKEN, because it runs between users’ phones, which could make adoption faster and more flexible.
From Spam Filtering to Proactive AI Scam Protection
Traditional spam call blocking depends on pattern matching and reputation lists, which are often reactive and easy for new scammers to dodge. Google’s RCS call verification marks a shift toward active Android call authentication, where the phone tries to prove who is on the other end before you answer. That matters in an era of deepfake and AI voice scams, where attackers can imitate loved ones, banks, or employers. By tying calls to a successful encrypted response, Google Dialer security no longer cares only about the number on screen, but whether a trusted device is behind it. This does not replace spam call blocking tools, but it adds a new layer that is harder to bypass with AI. Over time, wider adoption could make impersonation far less effective for scammers.
Requirements, Availability, and What Android Users Need to Do
For now, the feature focuses on people-to-people calls between Android users. Both parties must be running Google’s Phone (Dialer) app, plus Google Messages and Contacts, to enable the encrypted RCS confirmation. Availability starts on Pixel devices, but Google plans to extend it to other phones running Android 12 and later, narrowing the gap between advanced and basic call protection. There is no carrier integration required, which should help it spread faster than older network-only systems. Once enabled, the experience is mostly automatic: calls from verified contacts can be allowed through confidently, while suspicious calls may be blocked or treated with more caution. For Android users, the practical takeaway is simple: using Google’s communication apps on a recent device gives you stronger AI scam protection without changing how you place everyday calls.
