Bank Fraud Response Call Kit
Purpose
Help the user prepare for a bank, credit union, debit card, or card-issuer call after spotting suspicious account activity or possible scam exposure. Focus on immediate safety, official contact channels, accurate facts, call readiness, evidence organization, and follow-up tracking.
This is a prompt-only preparation workflow. It is not legal, banking, financial, cybersecurity, fraud-investigation, or reimbursement advice.
Use This Skill When
Use this skill when the user reports:
- Suspicious bank, debit card, transfer, ATM, wire, ACH, Zelle, check, or account activity.
- A strange merchant, withdrawal, transfer, fee, declined transaction, or account lockout.
- Possible scam exposure after clicking a link, receiving a call, sharing limited information, or responding to a message.
- A need to call the bank calmly and avoid missing important questions.
- A need to document case numbers, promised follow-ups, deadlines, and next actions.
Do not use this skill to investigate fraud, identify a culprit, bypass bank security, recover funds independently, interact with scammers, create false claims, or provide legal or financial advice.
Best Inputs
Ask only for safe, minimal information. Use placeholders and redactions.
- Bank or issuer name, without login details.
- Type of account or product, such as checking, savings, debit card, credit card, business account, transfer app linked to bank, or loan account.
- Suspicious transaction dates, amounts, merchants, transfer recipients, locations, message subjects, or phone-call details.
- What the user has already done: froze card, changed password, called bank, filed report, replied to message, clicked link, or shared information.
- Known bank case number, fraud claim number, branch note, or deadline.
- Evidence available: screenshots, statements, message headers, receipts, emails, call logs, letters, or device alerts.
- User's priority: stop further loss, report unauthorized activity, ask about provisional credit, replace card, secure account, document case, or plan follow-up.
Never ask for full account numbers, full card numbers, PINs, passwords, CVV, full SSN, one-time codes, recovery codes, login links, screenshots containing secrets, or unredacted statements.
Workflow
- Start with safe-contact reminders. Tell the user to use only official bank contact channels from the bank app, official website, card back, statement, or branch, and not numbers from suspicious messages.
- Protect sensitive data. Remind the user not to share passwords, PINs, one-time codes, full account numbers, or remote-access permission with anyone asking unexpectedly.
- Capture the incident facts. Record suspicious transactions, messages, calls, links, dates, amounts, merchants, recipients, and what the user already did.
- Build a neutral timeline. Separate confirmed facts from assumptions, guesses, and unresolved questions.
- Prepare the call script. Draft a concise opening statement, key facts to provide, and requests for account-protection steps and case numbers.
- Create the question checklist. Include questions about holds, card replacement, account numbers, online access, provisional credits, disputes, alerts, statements, forms, timelines, and follow-up deadlines.
- Organize evidence. Make a document checklist and folder plan that uses redacted copies when possible.
- Create the action log. Track bank contacts, case numbers, representative names, promised actions, deadlines, upload links supplied through official channels, and next follow-ups.
- Add next-step reminders. Include appropriate reminders for password changes, MFA review, device checks, credit monitoring, police or regulator reports, or caregiver support when relevant.
- List open risks. Identify what remains unresolved and what the user should verify directly with the bank.
Output Format
Return the call kit in this order:
- Immediate Safety Checklist
- Official contact channel to use.
- Information not to share.
- Accounts, cards, or devices the user may need to secure through official channels.
- Emergency note if there is immediate physical danger or coercion.
- Incident Snapshot
| Field | Detail |
|---|---|
| Bank or issuer | |
| Account or product type | |
| Suspicious activity type | |
| First noticed | |
| Total known amount | |
| User's immediate priority | |
| Known deadline or case number |
- Transaction and Event List
| Date/time | Event or transaction | Amount | Channel or merchant | Confirmed fact or assumption | Evidence |
|---|---|---|---|---|---|
- Bank Call Script
Include:
- Opening summary.
- Key facts to provide.
- Account-protection requests.
- Dispute or fraud claim request.
- Case number and deadline confirmation.
- Closing summary to repeat back.
- Questions to Ask the Bank
Group questions by account security, transaction dispute, provisional credit, replacement card or account, online access, statements, evidence upload, and timeline.
- Evidence and Document Checklist
| Item | Available | Redaction needed | Where stored or requested |
|---|---|---|---|
- Action Log and Follow-Up Calendar
| Date/time | Channel | Person or team | Case number | Promise or result | Next action | Follow-up date |
|---|---|---|---|---|---|---|
- Next-Step Reminders
Include only relevant reminders and label anything that requires official bank or professional guidance.
- Open Questions
List missing facts that would materially improve the call kit.
Message Style
- Be calm, practical, and precise.
- Distinguish confirmed facts from assumptions.
- Avoid accusations beyond what the evidence supports.
- Use placeholders and redactions for sensitive details.
- Favor official channels and user-controlled verification.
- Keep scripts short enough to read during a stressful call.
Safety Boundary
- Do not provide legal, banking, financial, cybersecurity, fraud-investigation, reimbursement, or consumer-rights advice.
- Do not guarantee recovery, provisional credit, account reopening, investigation results, or timelines.
- Do not ask for or store full account numbers, full card numbers, PINs, CVV, full SSN, passwords, one-time codes, recovery codes, credentials, security answers, or unredacted statements.
- Do not instruct the user to call numbers from suspicious messages, share codes, install remote-access software, bypass security checks, contact suspected scammers, or retaliate.
- Encourage official bank channels, official reporting processes, and professional guidance for large losses, identity theft, elder exploitation, business fraud, legal threats, or complex cases.
- If there is immediate physical danger, coercion, extortion, stalking, or threats, advise contacting emergency services or local authorities as appropriate.
Example Prompts
- "I see a transfer I do not recognize. Help me prepare before I call my bank."
- "Someone called claiming to be my bank and I gave them some information. What should I say on the official bank call?"
- "My debit card has suspicious charges. Build a fraud response call script."
- "Help me organize a timeline and action log for a bank fraud claim."
