Treat a familiar-sounding voice as a prompt to verify, not as proof. The FTC warns that scammers can imitate a familiar voice with voice-cloning technology alongside urgent requests, so pause, do not act on the call itself, and confirm the story through an independently known contact route you already trust. A secret word or an audio detector is not reliable proof, and no single check guarantees identity.
Find public social profile clues with our TraceSeek app.
What the official warning actually says
The FTC cautions that scammers can use voice-cloning technology to imitate someone you know and combine it with an urgent request. The supported lesson is narrow but strong: the sound of a voice during an urgent call is not enough to confirm who is speaking. That does not mean every warm, familiar call is a fake, and it does not mean you can reliably sort real from cloned audio by ear. It means a familiar-sounding voice plus urgency is the moment to slow down and check the story rather than the moment to act. [FTC: Fake emergencies and voice cloning]
Why a detector or secret word is not a guarantee
Audio-analysis tools and shared code words can feel comforting, but the published guidance does not present them as proof of identity. A code word can be guessed, reused, overheard or simply unknown to an honest person calling from a new number, and no detector is described here as confirming a real voice. Build your plan around a route to the person that you chose before the call, not around a phrase or a piece of software. If a check feels uncertain, that uncertainty is a reason to keep verifying, not a reason to skip confirmation. [FTC: Fake emergencies and voice cloning]
Use a route you already trust
The FTC's core advice fits dating-call situations well: verify the supposed person's story through an independently known contact route instead of relying on the sound of the call. In practice that means a number, account or channel you already had before this conversation, not one supplied during the urgent call. Do not let a caller redirect you to a new contact method as proof. Separate what you observed (a voice that sounded familiar, a sense of panic, a request for urgency) from what you know (whether that person truly needs help right now), and only then decide. [FTC: Fake emergencies and voice cloning]
- End or pause the call and reach the person through a number or account you already had.
- Consider asking someone you trust to talk the decision through with you.
- Write down what was requested and how the caller said it should be handled.
A short worksheet for the moment
Use this as editorial advice, not a platform test. The point is to keep observation, its limit and your next step visibly separate so urgency does not blur them. A brief table can be filled in quietly, even while you tell the caller you need a moment.
| observation | limit | next step |
|---|---|---|
| The voice sounded like someone I know. | Similarity is not proof of identity. | Pause and verify via a route you already trust. |
| The caller insisted it was urgent. | Urgency is pressure, not evidence of need. | Do not act during the call; confirm first. |
| The caller gave a new number or account. | A contact supplied by the caller is not independent. | Use your own existing contact route instead. |
| Someone offered a secret word as proof. | It is not described as a guarantee. | Still confirm through your trusted route. |
Keep the plan ready for later
Decide now, calmly, what you will do if a dating call turns into an urgent request, so the decision is not made under pressure. Choose your trusted verification route in advance, and tell a friend what your plan is. This guide is general education, not a platform procedure or legal advice. A familiar voice is never proof of identity or intent, and an unclear check is a reason to keep verifying, not to proceed. [FTC: Fake emergencies and voice cloning]
- Keep a simple record of the call, the request and any details shared.
- Revisit your plan with someone you trust before the next urgent call.
- If you are unsure, stay on the side of verifying rather than acting.
A couple more questions
If I recognize the voice, isn't that enough to confirm who is calling?
No. The FTC warns that voice-cloning technology can imitate a familiar voice, so recognition by sound does not confirm identity. Verify the story through an independently known contact route you already trust.
Would a secret word or an audio detector settle it?
Not as a guarantee. The published guidance does not present either as proof of identity, and no detector is described here as confirming a real voice. Use your own pre-existing contact route instead.
Is a secret word useless, then?
It may add a little friction, but it is not proof. A code word can be guessed, reused or overheard, and an honest caller may not know it. Treat it as one small check, not a substitute for reaching the person through a route you already know.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.