You are halfway through a client project when a message arrives: “Can you use this new link to sign in? It is urgent.” It appears to come from someone you know, but the request is different from the way you normally work. Meanwhile, you are trying to finish a draft and get out the door.
You do not need to make a security decision at the speed of the message. Pause, keep the request visible, and check it through a route you already trust.
Put the decision somewhere safe
Write a plain reminder: “Check unusual client login request.” Leave out the link, passwords, verification codes and client details. Do not click the link or enter credentials while you are checking. A note is a prompt to verify, not a copy of the suspicious message.
The Australian Government's small business cyber security guidance recommends verifying unusual requests using a trusted channel, such as a known phone number instead of contact details supplied in the message.
Check using a route you already know
For example, Jo receives an unexpected request to update bank details for a project. Jo leaves the requested change alone and calls the client's previously verified number. If the client confirms the request, Jo follows the agreed process and independently checks the details before changing anything. If the client cannot confirm it, Jo follows the organisation's incident process or gets security help.
If you are working solo, the same principle applies. Find the phone number in an existing trusted agreement or through the organisation's independently accessed official site, not in the suspicious message. Do not share a login code to prove who you are.
A two-minute verification note
- Write “verify unusual request” without sensitive details.
- Find an independently trusted contact or open the service through your usual saved address.
- Ask whether the request is real. Keep the change pending until you know.
- If a follow-up is needed, use your usual calendar. A parked thought does not send a notification.
- Once resolved, follow your normal record-keeping process and let the reminder go.
If you already clicked a link, shared a code or made a payment, a reminder alone is not enough. Contact the affected provider or bank promptly using independently verified details and follow its incident guidance.
You can do this on paper or in a note you trust. If seeing the reminder alongside your other thoughts helps, try a fictional example in Mute. The demo does not save changes and is not a password manager or incident response tool.