An unexpected message can look familiar before you have read a word. It might use a recognizable business name, a copied profile picture or a logo you have seen before. Those visual details are easy to notice, but they are not enough to establish who is speaking to you.
A useful response begins with a pause. Rather than deciding immediately whether a message is real, ask what it wants you to do and how you could check the request through a separate route. That small change gives you a practical next step.
Look at the request, not only the appearance
The US Federal Trade Commission describes phishing messages that invent account problems, unexpected invoices or a need to confirm personal details. Their goal is often to get you to open a link or attachment, or provide information. The story may change, so a checklist based only on spelling mistakes or old scam examples will miss some messages.
Pay attention when a message asks you to sign in, download something or provide private details that you were not expecting to share. An ordinary-looking design does not remove the need to check the action being requested. Read the FTC’s phishing guide.
Urgency is a reason to slow down
A countdown, threat of immediate account closure or instruction to keep a conversation secret can make independent checking feel inconvenient. Treat that pressure as a reason to stop. The FTC recommends resisting demands to act immediately and discussing a worrying request with someone you trust.
For example, imagine a message says that a problem must be fixed before the end of the hour. You can write down the claim in your own words, close the message, and choose a separate way to check it. You do not have to continue a conversation simply because it has already started. See the FTC’s advice on avoiding scams.
Verify through an independent route
The UK National Crime Agency advises using contact details from an organization’s official website rather than the number or address in a doubtful message. A saved contact or a website address you already know can also help you avoid relying on the sender’s instructions.
When you ask for verification, describe the request without forwarding unnecessary personal information. You can ask whether that organization sent a message of that type. Keep passwords and security codes out of the conversation. Read the NCA’s cybercrime guidance.
Keep a simple checking routine
- Pause before opening an unexpected link or attachment.
- Describe what the message is asking you to do.
- Choose a contact route independently of the message.
- Ask someone you trust for a second view if you feel pressured.
- Use the reporting or blocking tools available in your messaging service.
If you have already replied, avoid rushing into a second request that promises to fix the first one. Return to a verified contact channel and explain what happened. Keep a record of the message, but do not include passwords or codes in screenshots you share. The aim is to regain a clear view of the situation before taking another action.
Pause before the message chooses your next action for you.
