Illustrated guide to handle an urgent request from an executive
Original trust.you editorial illustration for this guide. Visual cues support the explanation; they are not proof of authenticity.

The short answer: Executive impersonation works because staff are trained to be responsive and discreet. A good control lets an employee verify without appearing obstructive.

Authority should survive an independent callback

The useful move is to separate what the claimant controls from evidence you can obtain independently. Names, logos, caller ID, screenshots and a polished page can all be copied. A saved telephone number, a typed official address, a known colleague or a protected transaction route changes the channel instead of merely inspecting the same claim again.

Risk also depends on consequence. Reading a public page is different from granting remote access, sending an identity document or approving an irreversible payment. As the cost of error rises, require stronger verification and prefer a step you can undo.

Before replying or approving a request, the email authenticity checklist can organise sender, context and consequence checks.

Warning signals to assess together

These clues become useful when they form a pattern. Treat each one as a prompt to verify, not as a verdict by itself.

  • The request bypasses normal approval

    Pair this observation with a separate check: Pause the transaction.

  • Secrecy is framed as loyalty

    Pair this observation with a separate check: Verify through a known channel or second approver.

  • Gift cards, new bank details or credentials are involved

    Pair this observation with a separate check: Report the attempt without replying to the attacker.

Do not use one clue as a verdict: Senior authority increases the need for process; it should not be a reason to waive it.

Verify executive authority through another channel

Keep the verification route separate from any contact detail or instruction supplied in the questionable message.

  • Pause the transaction

    This step tests the related concern: The request bypasses normal approval.

  • Verify through a known channel or second approver

    This step tests the related concern: Secrecy is framed as loyalty.

  • Report the attempt without replying to the attacker

    This step tests the related concern: Gift cards, new bank details or credentials are involved.

Decide what to do after verification

If the independent channel confirms the identity and request, ask whether the proposed method still gives you a record and recourse. Legitimate people and organisations should tolerate a proportionate verification step. Resistance, secrecy or a demand to bypass normal controls is new evidence, not an inconvenience to ignore.

If the evidence remains mixed, reduce exposure: do not send original documents when a redacted copy is enough, do not pay a deposit before verifying authority, and do not approve access broader than the task requires. “Not yet” is a valid decision when the missing fact matters.

The same independent-channel principle is applied in the bank impersonation call guide to a different professional request.

What this verification cannot establish

This guide cannot authenticate a specific person, account, website or transaction. Interfaces and attack methods change, and legitimate situations sometimes contain unusual details. For an active loss, account compromise or safety threat, contact the relevant institution or official reporting service through a verified route.

Official sources and further guidance

These primary sources support the topic and provide current reporting or technical guidance. Availability and procedures can differ by country.

Editorial note

Reviewed by the Trust You Editorial Desk on 2026-10-08. We assess title-to-H1 alignment, independent verification steps, limitations and overlap with existing coverage. Request a correction.