Stop
Do not send money, codes, files, or credentials during the call.
Scam response
The safest response is procedural: stop the requested action, preserve the message, verify through a known channel, and use detection as supporting evidence.
Check a saved voice message
If a call uses a familiar voice to demand money, credentials, secrecy, or urgent action, hang up and call the person or organization using a number you already trust. Save the voicemail or message for a separate AI voice check.
AI voice scams often borrow a trusted identity: a relative in trouble, an executive approving a transfer, a bank agent requesting a code, or a public official promoting an investment. The voice may sound convincing because the attacker only needs a short script. Focus on what the caller wants and whether the request bypasses normal safeguards.
Pressure is a major warning. Requests for secrecy, immediate payment, gift cards, cryptocurrency, remote access, one-time codes, or a new account destination should trigger a stop. These patterns remain dangerous even if the caller is a real human or the detector later returns likely human.
Do not argue about whether the voice is AI. End the call without sharing information, then use a known number from your contacts, official website, bank card, or company directory. Avoid redialing a number shown in the suspicious message because caller ID and message details can be manipulated.
For family scenarios, agree in advance on a callback process or family verification phrase, but remember that static personal facts can leak. For workplace requests, require the existing payment, procurement, password-reset, or executive-approval workflow. A familiar voice should never replace required authorization.
Preserve the original recording and select 10 to 30 seconds where the suspected speaker talks clearly. Test the request rather than hold music or another voice. A likely AI signal supports escalation, while an unclear or likely human result still leaves the identity and fraud questions open.
If the message contains several speakers or heavy noise, do not force a conclusion. Obtain another sample from the same source if it is safe, compare the speech with trusted public recordings, and document why the request was unusual. Never send money simply because a score appears low risk.
Contact the impersonated person, employer, financial institution, or platform through official channels. If credentials or codes were disclosed, change access immediately from a trusted device and notify the relevant provider. Keep call logs, voicemail files, transaction details, and screenshots in their original form.
Use precise language when reporting: describe the voice as suspected synthetic or cloned unless identity and generation are independently established. A detector result can help explain why you paused the transaction, but banks, platforms, employers, and investigators will also need source and account evidence.
Do not send money, codes, files, or credentials during the call.
Use a saved or official number, never one supplied by the caller.
Screen a clean saved sample without treating the result as proof.
Notify the impersonated person and affected institution quickly.
Voice cloning capabilities vary, but attackers may collect speech from social media, videos, voicemail, or breached data. Treat unusual requests as risky regardless of how the voice was obtained.
A trusted callback or established approval process is stronger. Personal facts and static questions may be discoverable or leaked.
Continue verification. The call may use replayed audio, edited human speech, or a real person conducting fraud.
Keep the original audio or voicemail, phone number, timestamp, account details, requested action, and any related messages or transaction records.