Protocol
Verify the request outside the message that created the urgency
The message should not be allowed to supply its own verification desk.
Before you use it
- Use when
- An unexpected message asks you to log in, pay or change sensitive information.
Keep this limit in mind
- Good spelling, a logo or a familiar sender name is not sufficient authentication. For workplace messages, use the established reporting process.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
The message should not be allowed to supply its own verification desk.
Steps
- Pause the requested action and avoid using the message's link, attachment or supplied callback number.
- Open a known legitimate service route or contact the organization through independently established details.
An example
A bank-branded text asks for immediate account confirmation. Opening the bank's known app is a different verification path from following the text's link.
Check your result
Did your verification rely on information independent of the suspicious request?
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingVerify the request outside the message that created the urgency
Evidence and sources
A suspicious message should be verified through a known independent contact route rather than its supplied link or number.
Claim basis: guidance. Claim limit: A polished message or familiar sender name does not establish authenticity. Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Recognizing phishing; independent contact; responding to a suspicious message"]. Agent release review: Agent checked the exact card fields and its claim, source, locator, example, check and stated boundary. This bounded projection preserves the source pack’s screened evidence scope and does not claim independent scientific or human editorial review.
How To Recognize and Avoid Phishing Scams · Responding to suspicious messages
All sources (1)
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-13