Download Privacy Needle App

Type to search

Guides & How-Tos Scam Exposed

How to verify a suspicious call when a familiar voice can be cloned

Share
Laptop and smartphone with an envelope-shaped alert illustrating phishing risk.

Published

If a call sounds like a relative or your manager and asks for an urgent transfer, end the call and verify the request through a contact route you already trust. You do not need to decide whether the voice was generated by AI before taking that precaution.

The US Federal Trade Commission’s voice-cloning warning describes scammers imitating relatives or employers to make demands more believable. Its advice is to call the person on a known number or reach them through another family member or friend.

That makes a useful starting point for Nigerian families and small businesses too. The verification process should work even when a caller sounds convincing, uses a familiar nickname or knows the amount on a genuine invoice.

A callback process you can practise

  1. Stop the conversation before sending money, sharing a code or changing an account detail.
  2. Find the saved number or an established contact record yourself. Do not use a replacement number supplied during the suspicious call.
  3. Start a separate conversation and ask whether the person made the request.
  4. If you cannot reach them, use another established contact. Leave the transaction pending until verification is complete.

For a family, agree who else can check an emergency claim. For a business, decide who covers for the usual approver when that person is travelling or unreachable. Write down the fallback before an urgent request arrives.

Separate identity from payment approval

A manager’s real voice is still insufficient evidence that a new bank account belongs to a supplier. Use the established supplier record and the normal approval process. An urgent call should not quietly replace the checks that apply to an ordinary payment.

Consider a hypothetical office request: a voice note says an invoice is overdue and directs an assistant to a new account. The assistant should verify both the instruction and the changed payment details through established channels. Our explanation of business email compromise covers the related risk of a convincing message being used to redirect a payment.

When the caller claims to be your bank

In its January 2026 impersonation advice, the FTC recommends contacting the bank through its official app or a number on a card or statement. It warns against finding a contact through a paid search result, sharing verification codes or granting remote access. Knowing your name or address does not establish the caller’s identity.

If you have already acted

Contact your bank promptly through an established channel if money or banking details were involved. Preserve the number, messages, payment reference and time of the request. For a work account, tell the person responsible for security so they can review the affected access. Avoid continuing the conversation with someone offering to recover the money for a fee.

Can I rely on a secret family word?

A private phrase can be an additional check, but it should not replace an independent callback. A phrase can be shared or exposed. Practise the callback process with relatives, alongside account-security help that respects their privacy, so a real emergency does not require inventing a process under pressure.

Featured image: AI-generated conceptual illustration.

Watch Our Latest Video
Stay ahead with expert insights on privacy, cybersecurity, artificial intelligence, data protection and compliance.
Privacy Needle AI | AI DPO Assistant & NDPA Compliance Software
Published: November 2, 2026
Daily Privacy News
Cybersecurity Updates
Data Protection Tips
GDPR & NDPA Explained
Tags:
Kendrick James - Certified Data Protection Officer

Kendrick James is a Certified Data Protection Officer with over seven years of hands-on experience supporting businesses with privacy compliance, audit reporting, data protection governance, and risk management. His expertise covers data protection law, compliance audits, breach prevention, privacy policies, data subject rights, and responsible data processing. As a contributor to Privacy Needle, Kendrick provides clear, practical, and trustworthy analysis on privacy, cybersecurity, AI governance, and digital compliance. His articles are written to help business leaders, compliance officers, founders, technology teams, and individuals understand complex privacy issues and make better decisions about personal data protection.

  • 1

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.