Learn the concept.
Urgent + secret? Verify first. A familiar face, voice, or job title can make an unexpected request feel convincing. Start with what the person wants you to do, then check through a separate route you trust.
Look at the request
A convincing introduction does not establish permission to use your account or spend your money. Notice requests for passwords, login codes, remote access, or gift-card numbers. A “boss” who wants an urgent, secret favor and photos of gift-card numbers is using a familiar scam pattern. The card number and personal identification number, or PIN, can let someone spend the balance without holding the card.
A familiar voice is not an identity check
Artificial intelligence, or AI, can imitate a voice or create a convincing video of someone. This is often called a deepfake. Ordinary impersonation can also work without AI. You do not need to prove how a suspicious call was made before pausing it. A smooth video or familiar voice does not independently confirm a money request.
Read what the code is for
Account login and recovery codes can help someone get into your account. Keep them private. A delivery handoff code serves a different purpose; read the message instead of assuming every code does the same job.
Verify through a separate route
End the exchange and contact the person yourself using a saved number, your organization’s directory, or a known support portal. Do not use a new number supplied by the requester. Asking “is this really you?” in the same chat lets the same unverified person answer. If your boss cannot be reached, hold the payment and follow your workplace’s approval process. A verified contact still does not need your password.
Use agreed safeguards, not a new secret from the caller
A family code word means a phrase agreed in advance, not a one-time account login code. It can add a check, but it can also be exposed; keep independent verification. For a fictional workplace like the one in our video, requiring two authorized people to approve a payment adds another check. Follow your employer’s actual process rather than accepting a caller’s request to skip it.
Act if a secret was shared
Open the real service yourself to secure a compromised account, change its password, and review signed-in devices. Report work requests through your usual support process. If you sent gift-card numbers, contact the card issuer promptly using its official contact information, keep the card and receipt, and ask whether the funds can be recovered. Recovery is not guaranteed. You can report scams at ReportFraud.ftc.gov.
Field example11 / A
Put it in context
In the Day 22 Short, a call that appears to be the boss asks Sam for gift cards and secrecy. Sam calls a number she already trusts and learns the boss never made the request. In the Day 12 Short, a pizza delivery disguise, an IT badge, and a fake Leo ask for account secrets instead. Both stories teach the same habit: pause the request, then verify it somewhere the requester does not control.
From a convincing call to an independent check
Follow the sequence, or move one step at a time.
Reduced motion is on. Use Next step to explore without animation.
Read all 4 steps
- The “boss” calls
A familiar-sounding caller wants gift-card numbers and secrecy. That does not establish who is calling.
- Pause the request
End the call without buying cards or sending numbers. You do not need to prove how the call was made.
- Choose your own route
Find your boss’s contact in the company directory you already use, not a number supplied in the request.
- Verify and report
In our fictional scenario, the real boss confirms they never asked. Report the suspicious request and keep the normal approval process.
Look past the face. Check the request.
Three clues in the fictional Day 22 boss call.
- 01“Do it now”
Urgency pressures you to skip a check.
- 02“Keep it secret”
Secrecy cuts out trusted colleagues and normal approvals.
- 03“Send the card numbers”
The numbers can transfer the value, even if you keep the card.
Read the visualIf the video looks flawless, is the money request verified?
No. Confirm the request through a separate trusted contact and follow the usual approval process.
Make a decision.
Use what you just learned. A correct answer lets you save this lesson to your progress.
Take this with you.
Pause when a request is rushed or secret. Verify unexpected money requests through a contact you already trust. Keep passwords, account login codes, and gift-card numbers private from an unverified requester.
Next lesson: The raise is automaticSam’s familiar-looking chat asks for a sign-in code. Choose what Leo does next.
Try the login-code chat challengeGo deeper with passwords and multifactor authentication or caller ID and phone scams.
See it in a Short.
Optional video companions from MyCyberTutor. Your lesson progress stays here. Explore the Shorts library