AI & TECHNOLOGY / EVIDENCE INTO PRACTICE
AI Voice Scams: Verify the Request, Not Just the Voice
Prepare a family and workplace verification routine for urgent calls. Learn why a familiar voice or a secret word cannot be your only identity check.
General education. Examples and tools do not guarantee outcomes. Read the disclaimer.
A familiar voice is not sufficient authorisation. Verify an urgent request through a saved, independent contact before transferring money or revealing information.
In this guide
You hear someone you know. They sound frightened, hurried and unable to explain much. The request is concrete: send money now. The dangerous moment is when recognising the voice feels like verifying the entire story.
The FTC explains that scammers can use voice cloning to imitate a loved one from an audio sample. Its advice is to call the person using a number you know, or reach someone else who can help verify the situation. [FTC: Scammers use AI to enhance family emergency schemes]
You do not need to become an expert at detecting synthetic audio. A safer process asks whether the request is independently confirmed, whether the recipient is correct and whether the proposed action makes sense.
Recognising a person does not authorise every request
Fictional example: a caller sounding like your sibling says a phone has been borrowed after an accident. They ask for $900 to a new payment recipient and say there is no time to call anyone else. The voice, the alleged event and the recipient are three separate claims.
Even if the voice were genuine, you would still need to understand the payment. Even if the emergency were genuine, you would still need to verify where the money is going. Separating the claims prevents one convincing detail from carrying the whole transaction.
A strange accent or metallic sound might make you suspicious, but a clean recording does not establish authenticity. Audio quality changes with devices, connections and surroundings. Do not make a financial decision depend on whether you can hear an artefact.
Agree the callback routine before anyone is frightened
Choose the people you would contact independently in an emergency and keep their numbers accessible. Tell them in advance that you may end an urgent incoming call and call back through a saved number. Make this a normal household procedure rather than a personal accusation.
If the person cannot answer, try another trusted contact who may know where they are. An unanswered call is not proof of a scam, but it is also not confirmation of the story. If you believe someone may be in immediate danger, use the appropriate local emergency route instead of treating payment as the only response.
This routine is our practical application of the FTC’s independent-contact principle. It reduces reliance on the incoming caller but is not a guarantee against every form of impersonation or account compromise.
A family word can help, but it is not a master key
A private word may provide another check if your household chooses to use one. Keep it out of public posts and avoid details easily learned from social profiles. Treat disclosure or compromise as a reason to replace it.
Do not let a correct word override an unexpected destination, unusual payment method or refusal to allow a callback. The purpose is to add evidence, not create a shortcut that turns any request into an approved one.
For a family drill, invent a harmless request involving no money and practise ending the call, selecting the saved contact and confirming the request. Keep the exercise brief and consensual. You are testing the process, not trying to frighten someone with an impersonation.
At work, verify a payment change through a separate route
Our suggested workplace rule is that an urgent voice request should not by itself change a supplier’s bank details or bypass existing payment approval. Use the organisation’s established verification and dual-approval procedures where applicable.
Imagine a known supplier asking for a new account immediately before an invoice is due. The relevant question is not simply “does this sound like the supplier?” It is “who is authorised to change these details, and how do we confirm that change outside this incoming call?” Record the verification so the next colleague does not have to infer it.
If a transfer happened, capture facts quickly
Contact the payment provider through its official route and explain that you suspect impersonation. Ask what can be stopped or reversed, preserve the transaction reference and keep a timeline. The FTC recommends acting promptly after a suspected scam; it does not promise that every payment can be recovered. [FTC: What To Do if You Were Scammed]
Our channel Short discusses a reported large loss. This companion does not rely on that case’s amount or allegations; it teaches the verification method that a reader can use without having to prove how a particular recording was made.
Put the rule where it will be seen: “A familiar voice can start a conversation. It cannot, by itself, approve a payment.” Then test whether your saved contacts and household expectations make that rule possible to follow.
Sources and further reading
Sources checked on 6 October 2026. Links support the nearby factual claims; worked examples and checklists are our educational illustrations.
- FTC: Scammers use AI to enhance family emergency schemes
Cloned voices can impersonate family members; independently call the person or another contact.
- FTC: What To Do if You Were Scammed
Promptly contact the payment provider and ask whether a transfer can be reversed; recovery is not guaranteed.
Prepared with AI assistance for the Mika vs Guru publishing team. This is not a claim of professional accreditation or independent peer review. How we research, label examples and handle corrections.