Handle an account access request without falling for fraud
A safe verification checklist and replies for login, email-change, and account takeover requests.
The prompt
Help me handle an account access or ownership-change request safely.
What they're asking for: [e.g. reset password, change account email, remove 2FA, transfer ownership, share data about an account]
How they contacted us: [from the account email / different email / phone / chat / social]
What I can see on the account: [recent changes, login locations, payment method last 4 digits - do not paste full details]
Our verification policy: [PASTE - or "none written"]
Anything that feels off: [urgency, story changes, pressure, mismatched details]
Give me:
1. A risk rating (low / medium / high) with the specific red flags you see. Common social-engineering signs include urgency, authority claims, requests to bypass process, recent email or phone changes, and contact from a different address.
2. The verification steps I should require for this request, following my policy, and what I must never accept as proof (e.g. information that's publicly findable).
3. A reply asking for verification that doesn't reveal any account details or confirm the account exists.
4. A reply for if they fail or refuse verification.
5. When to escalate to security or trust and safety.
Rules: never share or confirm personal data, ask for passwords, or bypass 2FA because someone is upset. Being slow is better than handing an account to the wrong person.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- PASTE - or "none written"
- urgency, story changes, pressure, mismatched details
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Write an onboarding email sequence for a new customer's usersA 30-day email sequence that gets new users from first login to regular use of the features that matter.
- Calculate how many support agents I need per shiftA staffing estimate by hour or shift from ticket volume, handle time, and service targets, with the math shown.
- Create or rewrite support macros and templatesConsistent, on-tone response templates for common issues across channels.
- Write order, shipping, refund, and delay noticesTransactional messages: confirmations, cancellations, refunds, shipping updates, and delays.