Skip to content
ScamClarity

Platform Safety Update

Android fake call detection targets spoofed calls from your contacts

Google says Android fake call detection can warn Phone by Google users about some spoofed contact calls. The feature may help with AI voice impersonation scams, but it only works under specific conditions.

By ScamClarity Editorial Team

Published Jun 3, 2026Updated Jun 3, 2026

Google announced on June 2, 2026 that Android is rolling out fake call detection in Phone by Google. The feature is aimed at a specific scam pattern: a caller appears to be one of your saved contacts and may use an AI-cloned voice or urgent story to get money, codes, credentials, or personal information.

If Android shows a fake-call warning, do not try to settle the question while the caller is on the line. Hang up, then verify through a number, app, or person you already trust before sending money, sharing a code, logging in, or giving information.

The announcement does not mean every Android user is covered, and it does not mean Android can judge whether a familiar voice is real. Google says the feature is rolling out globally this month starting with Pixel devices, and it only works when specific Phone by Google, Google Messages, RCS, and device requirements are met.

What Google confirmed

  • Source: Google Security Blog, published June 2, 2026.
  • Feature: fake call detection in Phone by Google.
  • Scam pattern: a spoofed call from a saved contact, possibly paired with AI voice cloning or a deepfake impersonation story.
  • Rollout: globally in Phone by Google this month, starting with Pixel devices.
  • Requirements Google names: Android 12 or later, Phone by Google, Contacts, Google Messages, RCS capability in Google Messages, and both the contact and recipient using Phone by Google.
  • First safe step: if the warning appears, hang up and verify through a separate trusted channel.
  • Source limits: Google did not publish a detection rate, false-positive rate, fraud-loss reduction number, or claim that the feature catches every scam call.

How the Android warning checks a contact call

Google describes fake call detection as a silent device-to-device confirmation check. When a saved contact calls and both of you are using Phone by Google, the caller's device can send a real-time confirmation signal through end-to-end encrypted RCS. If that signal is missing, your phone can check with the contact's actual device. If the real device says it is not making a call, Android can show a warning that someone may be pretending to call from that contact's number.

That means the warning is about the call source under Google's stated requirements. It is not a voice test, and it does not prove whether a caller's story is true. A scammer can still try another route, such as an unknown number, a business impersonation call, a follow-up text, a fake link, or a request that happens outside this contact-call pattern.

Google says fake call detection is on by default and can be disabled in Phone by Google settings.

Who may not be covered

The safest reading is narrow: this is a useful warning for some spoofed contact calls, not a universal scam-call shield.

  • Your phone may not be covered if it is below Android 12 or the feature has not reached your device yet.
  • The check may not work if Phone by Google is not installed or is not the default phone app.
  • The check depends on Google Messages with RCS capability.
  • Google says both the contact and call recipient must use Phone by Google.
  • The announcement focuses on spoofed contact calls. It does not say fake call detection covers every unknown number, robocall, government impersonation call, bank impersonation call, or scam that begins outside a saved-contact call.

These limits do not make the feature unsafe. They mean the basic safety rule should not depend on seeing a warning first.

Do not confuse it with Android Scam Detection

Google's Phone Help pages separate fake call detection from Scam Detection. Fake call detection is part of caller ID and spam protection and is aimed at callers hiding their identity or impersonating a contact. Google says it is on by default under the required setup.

Scam Detection is a different Phone by Google feature. Google says it works on eligible Pixel devices and countries, is off by default, and analyzes calls as they happen. Google also says Scam Detection is not 100 percent accurate. For readers, the practical point is the same: a phone warning can help, but it is not permission to skip independent verification.

Why a spoofed contact call can feel believable

The believable part is the combination of a familiar caller ID, a voice or story that sounds personal, and pressure to act before you can check. The FTC says scammers can use fake emergencies to push people into sending money, and its phone-scam guidance warns that caller ID can be spoofed so that any name or number appears on the screen.

The request matters more than the voice. Treat the call as unverified if someone who sounds familiar asks for any of these during an urgent call:

  • money by payment app, wire transfer, gift card, cryptocurrency, or another hard-to-reverse method
  • a one-time code, account password, reset link, or login approval
  • secrecy, especially a claim that you should not tell another family member, coworker, bank, or support team
  • remote access, a downloaded app, or instructions to change account settings
  • a link that moves the conversation into a login page, payment page, or form

Verify through a separate path before acting

Use a path the caller did not provide. That matters even when the number looks right or the voice sounds familiar.

  • Family or friend: hang up, call or message through a number or account you already know is theirs, or ask another trusted person to check if the caller demanded secrecy.
  • Employer or coworker: verify in a company chat, employee directory, known work number, or another internal channel before approving a payment, payroll change, file transfer, or account change.
  • Bank, company, or agency: use the official app, the number on a card or statement, or the official website typed directly into the browser. Do not use a callback number the caller gives you.
  • Emergency story: contact the person directly or contact local emergency services yourself. Do not send money while the caller is still controlling the conversation.
  • Follow-up text or link: go direct instead of using the link. A spoofed call can be used to make a later message feel trustworthy.

Before sending money, sharing a code, or giving information

Run these checks while you are off the call, not while the caller is still applying pressure.

  • Confirm the person separately

    Use a number, account, app, or contact method you already trust. Do not rely on the name shown on caller ID.

  • Check the requested action

    Money, codes, passwords, remote access, payment changes, and secrecy are higher-risk requests even when the caller sounds familiar.

  • Use the real provider path

    For banks, employers, agencies, and companies, go through the official app, website, card, statement, or internal directory.

  • Preserve the details

    Save the call time, displayed number, caller story, payment instructions, links, and screenshots of any warning if you can do that safely.

A real emergency does not require you to stay on a suspicious call while sending money, sharing a code, or installing software.

What to do if this matches a call you received

Start with what happened, not the name shown on caller ID.

Match the response to what happened

Situation

You only saw the Google announcement

First action

Check whether your device uses Phone by Google and meets Google's stated requirements. Do not assume every scam call will be flagged.

Where ScamClarity fits

AI voice scam background

Situation

You received a suspicious call but did not act

First action

Do not call back using a number the caller provided. Verify separately, then block or report the number if it was suspicious.

Where ScamClarity fits

Phone scam and AI voice warning signs

Situation

Android showed a fake-call warning

First action

Hang up. Contact the person or organization through a trusted route before sending anything or changing any account.

Where ScamClarity fits

Verification before payment or codes

Situation

You shared a code, password, or login approval

First action

Change the affected password, review sessions and account activity, and secure any account that used the same password.

Where ScamClarity fits

If a scammer has your information

Situation

You sent money

First action

Contact the bank, card issuer, payment app, wire service, gift card company, or crypto platform first. Ask what can still be blocked, reversed, disputed, or documented.

Where ScamClarity fits

Payment scam next steps

Situation

You downloaded an app or gave remote access

First action

Disconnect from the caller, stop using the exposed account for sensitive actions, and check the phone, browser, and accounts for changes.

Where ScamClarity fits

Phone and account change checks

Situation

You already reported the call

First action

Keep records and watch for follow-up recovery scams. A second caller offering guaranteed recovery for a fee is another warning sign.

Where ScamClarity fits

Reporting and recovery context

Use the first action that fits the furthest point the call reached.

Where to report a scam call

Reporting does not guarantee a refund, takedown, arrest, or personal response. It can still help agencies, carriers, platforms, and fraud teams connect repeated phone numbers, stories, payment paths, and impersonation patterns.

  • Phone by Google: Google says you can block or report a spam call from the Phone app's recent-call view.
  • FTC ReportFraud.gov: use this if you lost money, shared information, or have useful details about the caller, company, or scammer.
  • DoNotCall.gov: the FTC points readers there when they did not lose money and only want to report a call.
  • FCC Consumer Complaints Center: use the FCC path for unwanted calls, unwanted texts, spoofing concerns, or problems where your own number is being spoofed or mislabeled.
  • IdentityTheft.gov: use this if sensitive identity information, such as a Social Security number, may have been misused.

Related ScamClarity guidance

Use the more specific page when the call led to a payment, exposed information, a suspicious link, a device concern, or a family-safety conversation.

A familiar voice asked for money, codes, or secrecy

Use this when the main concern is AI voice cloning, a deepfake-sounding call, or a caller who sounded like someone you know.

AI voice scam calls and voice cloning

The call led to a link, login page, or account prompt

Use this when the call moved into a suspicious link, password entry, reset page, one-time code, or fake login.

Clicked a phishing link

Personal information, credentials, or financial details were shared

Use this when a scammer may have your phone number, email, password, code, card, bank details, Social Security number, ID, or documents.

If a scammer has your information

Your phone, browser, app, or account changed after the call

Use this when the caller got remote access, asked you to install something, or you noticed new sign-ins, alerts, settings changes, or device behavior.

Phone or account change checks

Money moved during or after the call

Use this when the call led to a payment app, card, bank transfer, wire, gift card, crypto transfer, refund claim, or fake payment proof.

Payment scam next steps

A family member may need a simpler call-checking rule

Use this for family conversations about urgent calls, gift card requests, tech support warnings, and pressure to keep a request secret.

Scam safety for seniors and families

Sources checked June 3, 2026

Sources were used for the Google platform update, feature requirements, Android feature distinction, phone-scam verification steps, and official reporting paths.