playbooks/retail --skills
Coach the frontline. Fix the hiccups.
44 skills for branch / retail work, a data test, and a prompt check. Fill in the blanks, or add them to Claude.
- 01Pick a skillEach one does one job you already do.
- 02Fill in the blanksCopy the finished prompt into any AI tool.
- 03Or add it to ClaudeDownload it once. It works in chat, Excel, PowerPoint, Word and Outlook.
Learn
Where retail teams can use AiBI immediately.
Draft a coaching script
Turn a scenario into a clear conversation guide with escalation triggers.
Recover a member service issue
Generate a service recovery message that owns the issue and clarifies next steps.
Write a frontline reference card
Condense a dense procedure into a one-page job aid.
Prep for a difficult conversation
Practice talking points before a member call without using customer specifics.
Check every draft before it goes out
- No member-specific data in any prompt
- Coaching language passes the "would I read this aloud?" test
- Escalation path is clear and named
- Reference card fits on a single sheet
- Tone matches the member experience standard
- Practiced once in the sandbox before live use
Test yourself
Green, yellow or red?
Six things you might paste into an AI tool. Sort each one.
Your published fee schedule, to explain an overdraft fee in plain words
A member complaint email with their name and the last four of their account
Last week's branch scorecard export with each banker's name and sales
Your internal funds-availability procedure
A photo of a check a member wants to deposit
A script for greeting members at the door
Skills
Try one free. Unlock the rest.
Branch / Retail skills 10
Everyday skills 20
Excel and PowerPoint 14
RT1 · Outlook · Chat
Reply to a member complaint
A member is upset and you owe them a written reply that is honest about what went wrong.
Download, then upload it in Claude under Customize › Skills. It also works in Claude for Excel, PowerPoint, Word and Outlook.
See the full prompt
ROLE You are a branch manager at a community bank writing a service-recovery reply to a member who has complained. You are honest, specific and calm. CONTEXT The member's complaint (redacted): """ [What the member said (redacted)] """ What actually happened, from our review: """ [What actually happened, from your review] """ What I am authorized to offer: """ [What you are authorized to offer] """ Channel: [How the reply goes out] (if blank, use email) Signed by: [Who signs it] (if blank, end with "[Your name, title]") TASK 1. Read the complaint and name, in one sentence, what the member is actually upset about. It is often the surprise or the knock-on effect, not the original event. 2. Compare the complaint with what happened. Where we made a mistake, own it plainly. Where we followed policy, explain the policy briefly and without blame. 3. State exactly what we will do, using only what is in "what I am authorized to offer". Give each action an owner and, if one is given, a date. 4. State the next step: what the member can do and who to contact. 5. Fit the channel: a phone script is spoken sentences with pauses for the member; a letter has a date line and a formal close. OUTPUT Subject: <plain subject, no "RE: Your complaint"> <reply, 120-220 words> - Opening: acknowledge the specific problem in their terms. - What happened: two or three sentences, facts only. - What we are doing: each action on its own line. - Next step and a direct contact. Notes for you: - <anything in the complaint the reply does not answer, and anything you should confirm before sending> RULES - Do not invent facts, dates, amounts, names or reasons that are not in what I gave you. - Do not promise a refund, a waiver, an early release or a callback unless it is listed in what I am authorized to offer. - Do not blame a named employee. Say "we", not "the teller". - Do not argue with the member's feelings or quote their words back at them sarcastically. - If the complaint alleges discrimination, an unauthorized transaction or an error under Regulation E, say so in the notes and tell me to route it under our complaint and dispute procedures before sending; do not decide the claim in the reply. - No exclamation points. No "we apologize for any inconvenience". IF SOMETHING IS MISSING If "what happened" is blank or contradicts the complaint, ask me what our review found before writing. If what I can offer is blank, ask me what I am authorized to do; do not offer anything. If the complaint contains account numbers or full names, stop and ask me to redact them.
Check before you use it
- Every remedy in the reply is one you are authorized to give.
- The facts match your review, not just the member's account.
- No employee is named or blamed.
- Anything that sounds like a dispute or a discrimination claim has been routed per your complaint procedure.
Never paste: Account numbers, full member names, SSNs, card numbers, or internal investigation notes.
Check a prompt for customer data before you paste it.
Type or paste a prompt you would send to an AI tool. It flags customer details — names, account numbers, SSNs, phone numbers — and rewrites the prompt with placeholders. It runs in your browser; nothing you type leaves this page.
Found 4 customer details
- Customer name
John Smith - Account number
0042871 - Date of birth
04/12/1981 - Phone number
(555) 123-4567
Safer version
write a quick reply to [customer name] — he’s furious we charged him 3 overdraft fees in one day on account [account number]. dob [remove — not needed], cell [remove — not needed]. wants them reversed
A pattern check, not a judgement — it can miss things. A named person still reviews before anything is used.
Build your own next.
The Foundation course: eighteen short builds, each one a working tool.