A convincing message can look like a routine invoice, a shared document, or a request from someone you know. Give your team a short process they can use when a message asks them to act.

Five checks for an unexpected message

  1. Look at the full sender address. A familiar display name alone does not establish who sent the message.
  2. Pause when the request creates pressure. Urgency, secrecy, or a threat of losing access deserves a second look.
  3. Verify through a separate channel. Call a known number or use an established contact method before acting on unusual payment or account requests.
  4. Open the service independently. Use a saved bookmark or known website instead of an unexpected sign-in link.
  5. Report the message. Use your approved reporting process so your IT or security team can review it. Avoid opening attachments or replying to investigate.

These checks draw on NIST’s phishing guidance for small businesses.

Make reporting easy before an incident

Write down who employees should contact, how to report outside normal hours, and what information the security team needs. A short practice exercise can reveal whether the process is easy to follow.

A useful team exercise: Ask a colleague where they would report an unexpected request to change a supplier’s payment details. If the answer is unclear, agree on the route and share it with the team.

If someone already clicked

Promptly contact your IT or security team and follow your incident response process. Explain what was opened, whether credentials were entered, and whether a download ran. A quick, factual report helps the team decide the next steps.

Staff guidance works alongside email protection, strong sign-in controls, and monitoring. Each layer addresses a different part of the risk.

Review your email protections

Explore email and web protection, or book a free 30-minute introduction to discuss your priorities. Paid work is scoped and quoted separately.

Back to Security Resources