About 20 minutes to set up · claude.ai only

Draft the first pass of a routine customer explanation letter

Today

The same five questions arrive every week: why the escrow payment changed, why the deposit is held until Thursday, what the maturity notice means. One operations manager writes a clear answer. Everyone else forwards a form nobody understands or writes something compliance has to rewrite.

With Claude

You paste the facts and the outcome a person here already decided, and get a plain English letter that uses your figures untouched, never states what a regulation entitles the customer to, and gathers every judgment call in one list for whoever signs it.

The prompt

Paste this into claude.ai and replace anything in brackets.

You are drafting the first pass of a routine written explanation to a customer of a [community bank / credit union / lender]. A qualified person here reviews, corrects, and signs it before it goes anywhere.

De-identify before you paste. No name, no account or card number, no Social Security or taxpayer number, no date of birth, no address. Call the customer [customer] and include only what is needed to explain the situation.

What the customer asked, or what happened: [describe it generically]
The outcome a person here has already decided: [state it plainly]
The figures and dates involved, copied exactly:
[paste them]
Who the reader is: [for example a small business owner, or an older accountholder who banks in the branch]

Absolute rules:
- Copy every figure and date exactly as I gave it. Never calculate, total, round, annualize, or infer a number.
- Never state what a regulation requires, prohibits, or entitles the customer to. If the letter seems to need that, write [REVIEWER: does our disclosure language belong here] instead.
- Add no fact, reason, or next step that is not above. Do not restate or soften the outcome, and do not apologize on the institution's behalf.
- This letter explains something already decided. It does not decide anything, and it does not evaluate credit, eligibility, or creditworthiness. If what I pasted looks like a credit decision, stop and say so.
- Where a judgment only a qualified person can make is needed, write [REVIEWER: the specific question].

Under 300 words, plain English, explaining any banking term the first time it appears in one short clause. Structure it as: what happened, what it means for the customer in practical terms, what happens next and by when, and who to call with a question. Then list every [REVIEWER: ...] item separately so the person signing sees them in one place.

What to skip in banks and financial services firms

  • Customer records and identifiers do not go into a chat window, in any account. That means account and card numbers, full Social Security and taxpayer numbers, dates of birth, online banking credentials, signature cards, core exports, wire instructions, loan files carrying borrower income and asset documents, and credit reports and scores. Two reasons, and they are separate. First, this is nonpublic personal information: Regulation P limits disclosure of it to nonaffiliated third parties and limits reuse, and the security standards your regulator enforces expect a written program and real diligence over any third party that touches customer information, which is exactly what the interagency third party risk guidance the OCC, Federal Reserve, and FDIC issued in June 2023 covers for banks of every size, community banks included. Credit unions get the same questions from NCUA. Second, a consumer report was pulled for a permissible purpose under FCRA, which allows a report to be furnished for listed purposes and no others, and pasting a tri merge into a chat is a use nobody documented. Work at the policy and summary level, paste the language and not the file, and settle the account and vendor question with whoever owns compliance before anything live moves.
  • Nothing that touches a credit decision. Not approving, denying, pricing, risk grading, granting an exception, working out debt to income or a coverage ratio that feeds the decision, and above all not drafting the specific reasons on an adverse action notice. Regulation B requires the statement of reasons to be specific, to indicate the principal reasons, and to relate to and accurately describe the factors actually considered, and CFPB Circular 2022-03 says plainly that a creditor may not use a model when doing so means it cannot give specific and accurate reasons, and that not understanding your own method is not a defense. A paragraph that reads like a reason but was not the reason is a violation with your institution's name on it, with fair lending exposure underneath. Anthropic's Usage Policy points the same way: loan approvals and determining eligibility or creditworthiness are named high risk, and home loans are named again under housing. The decision, the reasons, and the notice belong to your lender, your credit committee, and your written credit policy.
  • Suspicious activity reporting, and anything that would reach a customer as advice. A SAR, and any information that would reveal the existence of a SAR, is confidential under 31 CFR 1020.320(e), and no bank and no director, officer, employee, or agent of a bank may disclose it, so the narrative does not get drafted, polished, or rehearsed in a chat window, and neither does the alert that led to it. Examination reports and examiner correspondence stay out for a related reason: they are your regulator's records, not yours to hand to a third party. On the advisory side, Claude holds no registration and no license. No recommendation, no allocation, no security selection, no suitability or best interest conclusion, and nothing that reads to a client as investment advice. If your firm is a registered investment adviser or a broker dealer, your advertising, review, and recordkeeping obligations attach to whatever goes out, and a chat transcript is not part of your retention system.

Want all 4 workflows for banks and financial services firms in your inbox?

Every prompt on this page plus the rest, so you still have them on Monday. One email, then four short ones on making it stick. Unsubscribe any time.

Or answer four questions and Claude writes three workflows for your specific business rather than the industry generally.

Before you try it

More for banks and financial services firms

Full guide for banks and financial services firms