Someone Clicked. Now What? A Calm 25-Minute Phishing Playbook
Photo: Tim Sheerman-Chase, CC BY 2.0, via Wikimedia Commons
Phishing rarely arrives with a drumroll. More often it turns up as a forwarded email, a slightly panicked message on Teams, or someone saying they think they have done something silly. The worst outcome is not usually the first click. It is the hour of indecision that follows while everyone waits for someone else to take charge.
This playbook is written for the person who happens to be in charge that morning: an office manager, a finance lead, a director, or the one person in the building who is generally good with computers. It is not a technical deep dive. It is a calm sequence for the first 25 minutes.
Minute 0–5: Stop the spread, not the person
Start by lowering the temperature. The person who clicked is now your best witness, not the problem. Ask four simple questions: what did the email ask you to do, did you enter your password, did you open an attachment, and have you sent anything on to anyone else?
Ask them not to forward the email to colleagues. Ask them not to delete it either. If they entered credentials, move straight to the account containment step below. If they opened an attachment, disconnect the device from Wi-Fi or the network cable but leave it powered on. Do not start running antivirus scans or reinstalling anything yet.
If the email came from a customer or supplier account that may also be compromised, note that. The same message may have landed in other inboxes.
Minute 5–10: Preserve the evidence
Before anyone tidies up, keep a copy. In Outlook, use 'Save as' to save the message as an .eml file, or ask whoever administers Microsoft 365 to run a message trace. Take a screenshot of the sender address, subject line, time received, and any links or attachments. Do not click the link again to 'check where it goes'.
Write down the basics in a shared note: who received it, who clicked, what was entered, what device was used, and when. This is not bureaucracy. If money is lost or personal data is involved, a simple timeline will save hours later.
Minute 10–15: Contain the account
If credentials were entered, reset the password from a different, trusted device. Then revoke active sessions so anyone already signed in is pushed out. Re-check the multi-factor authentication (MFA) methods on the account. If a new phone number or authenticator app has appeared, remove it and re-enrol the real user.
Check mailbox rules for forwarding, auto-forwarding, and rules that move messages into obscure folders. Attackers often add a rule to hide replies from the real account owner. Also check sent items, deleted items, and connected apps or third-party consent. In a small firm, this is often a job for whoever holds the Microsoft 365 or Google Workspace admin account, but the manager can still ask for these specific checks.
Minute 15–20: Put payments on hold
If the email involved bank details, invoices, payroll, or a change of supplier account, call the bank using a number you already hold. Do not use contact details from the suspicious email. Put a temporary hold on any payment that matches the story, even if it is embarrassing or inconvenient. A delayed payment is much easier to fix than a fraudulent one.
Warn the small group of people who need to know: finance, the managing director, and anyone else who received the same message. Keep the warning simple. Do not forward the live email with its links. Say what happened, what to do if they receive it, and who to contact.
Minute 20–25: Report and record
In the UK, suspicious emails can be sent to the NCSC's Suspicious Email Reporting Service at [email protected]. If money has been lost, report it to Action Fraud. If personal data may have been accessed or stolen, consider whether the Information Commissioner's Office needs to be told within 72 hours. You do not need to make that decision alone in minute 25, but you do need to note it as an open question.
Record what was done, by whom, and at what time. Note any actions still outstanding: password resets for other recipients, a mailbox rule review, a bank call-back, or a decision about blocking the sender's domain.
What to have ready before next time
A 25-minute response only works if the basics exist before the incident. Name an incident lead and a deputy. Keep a clean device available for password resets. Keep an out-of-band contact list, including the bank and your IT support provider, somewhere other than the affected mailbox. Print this card and put it where the office manager can find it.
Finally, rehearse it once. Not a full security exercise, just a 20-minute walkthrough with the people who would be in the room. The goal is not to make a small firm bulletproof. It is to make the first 25 minutes calm, deliberate, and short.