Gmail Phishing Report and Response Process Audit
Review how my team reports suspicious messages (defensive).
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review our process for suspicious emails in Gmail, as a defensive process review. Steps staff follow: [PROCESS]. Recent reports and outcomes: [REPORTS]. Tools and contacts: [TOOLS_AND_CONTACTS]. First describe the process as you understand it in a numbered list so I can correct you, then analyse it: clarity of the reporting route, speed of response, feedback to reporters (do staff who report get a reply within a day? a silent process discourages reporting), training, handling of people who clicked or entered details, and measurement. Calculate the median time from report to response and the share of reports answered, with arithmetic. Return a table of gaps with Evidence, Effect and Fix, a one-page staff guide, and monthly metrics. Run a drill with an obviously harmless test message approved by IT and time each step. Keep a blame-free tone so people report quickly, and keep all recommendations defensive; do not write phishing content or ways around filters. Mark anything depending on our tools [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.