If a call, voicemail, or voice message sounds like someone you know and asks for money, secrecy, a login code, a link, a new app, or urgent action, pause before responding. The voice is not enough proof.
Verify through a channel the caller does not control: a saved number, existing family chat, workplace directory, official website, account app, statement number, or another trusted person.
What happened
You only heard the call or message
Do first
Do not reply through the caller's number or link.
Check next
Verify through a saved contact or trusted person.
What happened
You are still on the call
Do first
Hang up or say you will call back.
Check next
Do not stay on while paying, clicking, or opening accounts.
What happened
They claimed an emergency
Do first
Contact the person directly or ask someone nearby to check.
Check next
Treat secrecy as a warning sign.
What happened
They threatened harm or kidnapping
Do first
Try to reach the person while another trusted person helps.
Check next
Contact local emergency services if the threat is credible and immediate.
What happened
They asked for money
Do first
Verify before paying.
Check next
Watch for wire, gift card, crypto, payment app, courier, or cash pickup pressure.
What happened
You sent money
Do first
Contact the payment provider immediately.
Check next
Save receipts, transaction IDs, wallet addresses, messages, and call details.
What happened
You shared a code, password, or link
Do first
Secure the affected account from a trusted device.
Check next
Review recovery details, sessions, forwarding rules, and recent logins.
What happened
You clicked a link or moved apps
Do first
Stop using that link or app until verified.
Check next
Treat entered passwords, codes, or payment details as exposed.
| What happened | Do first | Check next |
|---|---|---|
| You only heard the call or message | Do not reply through the caller's number or link. | Verify through a saved contact or trusted person. |
| You are still on the call | Hang up or say you will call back. | Do not stay on while paying, clicking, or opening accounts. |
| They claimed an emergency | Contact the person directly or ask someone nearby to check. | Treat secrecy as a warning sign. |
| They threatened harm or kidnapping | Try to reach the person while another trusted person helps. | Contact local emergency services if the threat is credible and immediate. |
| They asked for money | Verify before paying. | Watch for wire, gift card, crypto, payment app, courier, or cash pickup pressure. |
| You sent money | Contact the payment provider immediately. | Save receipts, transaction IDs, wallet addresses, messages, and call details. |
| You shared a code, password, or link | Secure the affected account from a trusted device. | Review recovery details, sessions, forwarding rules, and recent logins. |
| You clicked a link or moved apps | Stop using that link or app until verified. | Treat entered passwords, codes, or payment details as exposed. |
If more than one row applies, start with money, codes, accounts, identity documents, or credible safety threats.
Verify outside the voice
Do not judge the call by whether the voice sounds real. A fake voice may sound choppy, but it may also sound smooth. The stronger clues are the request: urgency, secrecy, payment, codes, links, new apps, or pressure to stay on the line.
Use the normal channel for the situation. Family emergency: saved number or another trusted family member. Boss request: workplace approval process. Bank or agency call: official app, website, statement, or government site. Online relationship or celebrity message: treat money, crypto, and account requests as the real risk.
If the call claimed an emergency or threat
Family emergency and grandparent scams work by making verification feel disloyal. If the caller says a child, parent, partner, friend, or grandchild was arrested, injured, stranded, robbed, hospitalized, or in a crash, stop the caller's timeline. Contact the person directly or ask someone near them to check.
For a kidnapping, ransom, or harm threat, try to reach the person directly while another trusted person helps. If there is a credible immediate threat, contact local emergency services. Save the number, threat wording, payment demand, and any voice, photo, or video evidence.
If money was requested or sent
Contact the provider connected to the payment. Recovery depends on method, timing, and provider rules, so do not let the caller direct the recovery.
- Card: call the issuer from the card or statement. Ask about disputes, replacement, recurring charges, and monitoring.
- Wire, ACH, bank transfer, Zelle, or payment app: contact the bank or app through official support and ask what can be stopped, reviewed, or documented.
- Gift card: keep the card and receipt, then contact the issuer quickly.
- Crypto: save wallet addresses, transaction hashes, platform names, screenshots, and chat history. Be cautious with recovery promises.
- Cash pickup, courier, gold, or local delivery: preserve pickup details and contact local law enforcement if there is an in-person element or threat.
If the payment moved through Zelle, use Zelle scams and what changes after payment. If the caller asked for crypto, the main risk may overlap with crypto scam recovery and wallet risk.
If codes, links, accounts, or personal information were involved
A voice scam can become an account or identity problem when the caller gets more than attention. Passwords, one-time codes, bank details, card numbers, Social Security numbers, ID images, workplace files, and remote-access sessions all change the response.
Secure the exposed account or information
Start with the account, payment method, or document the caller actually touched.
Password or login link
Change the password from the real site or app. Sign out other sessions and review recovery details.
One-time code
Check which account generated the code. It may have approved a login, password reset, account change, or payment.
Card or bank details
Contact the bank or card issuer through official support and ask what should be blocked, replaced, monitored, or disputed.
SSN, ID, passport, or tax document
Use IdentityTheft.gov for a recovery plan if sensitive identity information was exposed or misused.
Remote access or screen sharing
Disconnect the session, remove the tool, and use a trusted device for important account changes.
Work account or company payment
Escalate internally. A voice request involving payroll, vendor payment, finance systems, or managed devices can affect more than one person.
Do not give another code to someone who says they need it to cancel the scam, verify your identity, or recover money.
For exposed personal information, use what to do when a scammer has your information. For device, app, browser, or account changes after a link or remote-access session, use phone and account access checks. If the main issue was a suspicious link, email, or text, the phishing or smishing page may be the better next step.
What to save before deleting or blocking
Save enough to explain what happened without posting private information publicly. Evidence helps when you report the scam, contact a payment provider, explain the incident to family or work, or file with an official agency.
Save the useful details
Keep private information out of public posts, but preserve the details that show what happened.
Call and voice evidence
Voicemail, voice memo, call recording if lawfully available, call log, caller ID, phone numbers, dates, times, and callback instructions.
The story and request
Who they claimed to be, what emergency they described, what they asked you to do, and whether they demanded secrecy.
Messages and links
Texts, DMs, emails, URLs, QR codes, usernames, profile links, and any request to move to another app.
Payment details
Receipts, transaction IDs, wire details, payment app handles, wallet addresses, gift card numbers and receipts, and bank or card case numbers.
Account and device evidence
Login alerts, password reset emails, recovery changes, new apps, remote-access tool names, and screenshots of suspicious account activity.
Threat or safety evidence
Exact threat wording, ransom demand, proof-of-life media, pickup instructions, delivery addresses, and any local contact details.
Do not post full card numbers, SSNs, passwords, private account screenshots, gift card PINs, or ID images in public forums.
Where to report or get help
Use the official path that matches what happened. Reporting does not guarantee recovery, but it creates a record and gives agencies details they can use to track patterns.
- FTC ReportFraud: consumer AI voice scams, family emergency scams, impersonation, and payment pressure.
- FBI IC3: internet-enabled fraud, links, account access, crypto, business payment requests, or significant financial losses.
- FCC Consumer Complaints Center or DoNotCall.gov: unwanted robocalls, spoofed calls, and AI-generated robocall complaints.
- Payment provider: bank, card issuer, payment app, wire company, gift card issuer, crypto platform, or transfer service if money moved.
- IdentityTheft.gov: SSN, ID documents, tax records, or other sensitive identity exposure.
- Work, school, or organization: payroll, vendors, managed accounts, student systems, or company devices.
- Local emergency services: credible immediate threat, in-person pickup, ransom demand, or local safety risk.
Set rules before the next call
The best defense is low-tech and agreed on before an emergency. People under pressure should not have to invent a verification system during a scary call.
- Set a family code word that is not shared by text, email, or public posts.
- Require urgent money requests to be verified through a saved number or second trusted person.
- Tell older relatives and teens that a familiar voice is not proof when money, secrecy, codes, or links are involved.
- For businesses, require callback verification and two-person approval for urgent payments, vendor changes, payroll changes, gift cards, and wires.
- Review public audio exposure for children, older adults, executives, creators, and employees with payment authority.
- Keep multi-factor authentication on and never share codes by phone, text, email, or messaging app.
What official data does and does not prove
Official public data usually does not isolate voice-cloning losses by itself. Broad claims about AI voice losses can overstate what the data proves.
The FBI's 2025 IC3 Annual Report listed 22,364 complaints with an AI-related descriptor and $893,346,472 in adjusted losses tied to those AI-related complaints. That does not mean AI voice cloning alone caused those losses. The safer interpretation is narrower: AI is appearing across reported fraud types, and voice cloning can make old scams harder to verify.
FAQ
Can AI really clone someone's voice?
Yes. The FTC warns that scammers can use a short voice clip to make a call or message sound like a family member, friend, executive, or other known person.
Can I tell if a voice is AI by listening?
Not reliably. Odd pauses or strange wording can be clues, but a smooth voice can still be fake. Verify the request outside the call instead of judging the audio.
Should I call the number back?
Do not use redial or a number the caller gave you. Use a saved number, official website, statement number, workplace directory, or another trusted contact.
What if I sent money because it sounded like my child or parent?
Contact the payment provider immediately through official support. Ask what can be blocked, recalled, disputed, frozen, replaced, or documented. Save the call details, messages, receipts, transaction IDs, and any wallet or payment information.
What if the caller threatened to hurt someone?
Try to contact the person directly while another trusted person helps. If there is a credible immediate threat, contact local emergency services. Save the phone number, threat wording, payment demand, and any voice, photo, or video evidence.
Is a family code word enough?
It helps, but it should not be the only control. Use it with trusted callbacks, second-person verification, and a rule that no urgent payment happens from an unverified call.
Sources checked
Sources checked May 27, 2026. Use the official source that matches your situation; reporting pages and provider rules can change.
- FTC AI family emergency scam guidance
Voice cloning from short audio clips, family emergency setup, trusted callback verification, hard-to-reverse payment methods, and FTC reporting.
- FTC fake emergency scams
Urgency, secrecy, authority-figure pressure, safe verification questions, calling a known number, and contacting another trusted person.
- FTC what to do if you were scammed
Payment-provider contact, information exposure, remote access, account checks, and ReportFraud reporting after a scam.
- FTC gift card scam guidance
Gift card evidence, issuer contact, and FTC reporting after gift card payment.
- FTC ReportFraud
Consumer fraud reports, including impersonation and payment scams.
- FTC robocall guidance
Caller ID spoofing, robocall reporting, hanging up, and DoNotCall.gov guidance.
- FCC AI-generated robocall ruling announcement
The February 8, 2024 FCC ruling that AI-generated voices in robocalls are artificial voices under the TCPA.
- FCC Consumer Complaints Center
Consumer complaints for unwanted calls, robocalls, and text issues.
- FBI IC3 AI-generated vishing warning
AI-generated voice messages, vishing, impersonation of known contacts, independent verification, avoiding links, and code-word guidance.
- FBI IC3 2025 Annual Report
AI-related complaint and loss data, plus the limitation that AI-related is a descriptor across fraud types, not voice cloning alone.
- FTC voice cloning analysis
Limits of voice-cloning detection, upstream prevention, authentication, and enforcement or industry controls.
- IdentityTheft.gov
Identity theft recovery planning when SSNs, IDs, tax files, or identity misuse are involved.