A senior voice calls with an urgent request. What do you say if it might be fake?

You know the pressure even if you have never faced a fake voice. A senior person calls. The request sounds urgent. The tone says this is not the time to slow things down. Your job, in that moment, is not only to understand the request. It is to answer in a way that protects the company without making you sound difficult, suspicious or rude.

That is why new deepfake-call data matters for people who get judged when they speak. Gartner, a business and technology insights company, surveyed 297 senior cybersecurity leaders in March-May 2026 about social engineering incidents involving deepfakes. The question this raises for everyday employees is simple: what do you actually say when the voice on the call sounds important? We will get to the exact sentence. First, why it may be hard to say out loud.

The risky moment is not always the technology

Deepfake stories often focus on detection. Can you hear the glitch? Does the face move strangely? Does the timing feel off? That makes sense, but it leaves out the most human part of the call: hierarchy. Many employees have been trained, formally or not, to be responsive when a senior person asks for something.

A request can feel more believable when it arrives with the right name, the right context and the right urgency. Gartner said AI is increasing the volume, personalization and credibility of social engineering while reducing the reliability of familiar detection cues. In plain English: the old clues may not be enough, and the conversation may feel normal until the employee has to push back.

That pressure is familiar outside cybersecurity too. It is the same feeling that shows up in job interviews, performance reviews and client calls: your brain may know the safer answer, while your voice hesitates because the other person has status. The more urgent the request sounds, the more awkward it can feel to slow the exchange down.

Why practicing the sentence matters

In AmberWillo practice data, the median confidence score moved from 6.4 out of 10 on a person's first completed session to 6.8 by session 10. That is not a promise that practice prevents mistakes. It is a small, practical clue about speaking under pressure: saying things out loud can feel different from knowing them silently.

That difference matters on calls. Many workplace scripts are easy on paper and uncomfortable in real time. Try saying, in a normal voice, that you cannot act yet. Try saying it to someone more senior. Try saying it when the request sounds urgent. The words may be short, but the social move is not.

This is the open loop in the Gartner finding. The safest response may not depend on sounding calm enough to spot a fake voice. It may depend on whether an employee has a sentence ready before the call happens.

The number behind the sentence

Here is the finding Gartner reported: 41% of chief information security officers said they had at least one social engineering incident involving a deepfake during an employee audio call in the previous 12 months. Another 36% reported one during a video call.

That is why the employee's line matters. Gartner's release says organizations should train employees and approvers to pause, verify and report high-risk requests across e-mail, voice, video, collaboration tools or an AI application. Put into a sentence an employee can actually say, the line is: “I need to verify this and call you back.”

It may sound simple. It may also feel socially expensive. That is the point. The sentence works only if a person can say it when a voice sounds senior, urgent and possibly annoyed.

What this means for you

If your workplace handles money, access, accounts, approvals or private data, treat the sentence as a speaking skill, not just a security rule. You do not have to accuse anyone. You do not have to diagnose a fake. You need a neutral way to slow the request down.

Practice the line out loud. Silent agreement with a policy is not the same as saying it to a senior voice.
Keep the tone boring. Calm and procedural is better than dramatic.
Use a separate channel. If a request arrives by voice or video, confirm through a route your organization already trusts.
Report the moment. A suspicious call is not a personal failure. It is useful information for the people protecting the organization.