Topic starter
06/11/2026 6:39 pm
TL;DR: Voice cloning has made contact centers a high-value fraud surface, and Daon says synthetic audio can now defeat knowledge-based authentication and human intuition. The security shift is away from what callers know and toward continuous proof of who is speaking, because manual detection no longer keeps pace with AI-generated impersonation.
Editorial analysis by NHI Mgmt Group, based on content published by Daon: “Voice Deepfakes Are Fooling Call Center Agents: Here’s How to Stop Them”.
Key questions
Q: What should teams do first when voice deepfakes are used in contact center fraud?
A: Treat the event as an identity proofing failure and move high-risk callers to stronger controls such as callback to a known number, knowledge-based authentication, or out-of-band verification.
Q: Why do voice deepfakes bypass human call center agents so easily?
A: Voice deepfakes succeed because agents tend to trust familiar speech cues, urgency and context more than a caller’s true identity.
Q: How do passive voice biometrics work in contact centers?
A: Passive voice biometrics analyse a caller’s live speech and compare it with an enrolled voiceprint to estimate whether the voice matches a known identity.
Practitioner guidance
- Replace KBA on high-risk calls Remove security questions from any workflow that can reset credentials, change payees, or release funds, and substitute identity checks that are harder to precompute from breached data.
- Add liveness and synthetic speech checks Deploy controls that can detect replay audio, cloned voices, and machine-generated speech during the live call, not only at enrolment or post-call review.
- Extend verification beyond call start Require continuous authentication or step-up checks on every high-risk branch of the call flow so an attacker cannot clear the front door and change identity mid-session.
Bottom line: Voice cloning has turned contact centers into a practical impersonation channel, especially where recovery and payment workflows still depend on caller knowledge.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Voice deepfakes expose an authentication design flaw, not just a fraud trend. Contact centers were optimised for speed and courtesy long before synthetic speech became accessible at scale. That makes the channel structurally vulnerable wherever the control model depends on memory, caller confidence, or agent intuition. The governance lesson is that identity proofing must move from questions to biometric and session-level evidence, because the old model was never built for machine-generated impersonation.
A few things that frame the scale:
- Veriff's 2026 Identity Fraud Report documented a 300X increase in digitally presented media that was either entirely AI-generated or otherwise altered.
A question worth separating out:
Q: How should organizations verify high-risk caller requests without adding friction?
A: Use risk-based call handling, so routine requests pass with minimal checks while high-risk changes trigger step-up verification such as a one-time passcode, call-back to a registered number, or agent supervisor approval. The control should be tied to caller risk, request type, and account history, not every interaction, to limit friction and fraud.
👉 Read our full editorial: Voice deepfakes are turning contact centers into fraud channels