P
AI for Collections Specialist

Claude Project: Build an Automated Compliance Letter Writing System

Claude

For Collections Specialists

Tools: Claude Pro | Time to build: 1–2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for drafting — see Level 3 guide: "Build a Claude FDCPA Compliance Knowledge Base"

What This Builds

A Claude Project that produces complete, FDCPA-compliant collection letters in under 90 seconds — by combining your agency's approved templates, client-specific rules, and account context into a single request. Instead of pulling up a template, manually editing 8 fields, and reviewing for compliance each time, you describe the scenario in 3 lines and get a ready-to-review letter. Over time, the system learns your most common scenarios and gets faster.

Prerequisites

  • Claude Pro ({{tool:Claude.plan}} at {{tool:Claude.price}})
  • FDCPA Compliance Knowledge Base project already set up (Level 3 guide)
  • Your agency's approved letter templates in text format (remove consumer PHI from any real examples)
  • A list of your top 10 letter types (first notice, dispute ack, C&D ack, settlement offer, broken-PTP, legal referral, etc.)

The Concept

Your existing Compliance Base project answers questions. This system goes further — it generates fully formatted production-ready letters by combining: (1) your templates as structural models, (2) your compliance rules as guardrails, and (3) the specific account details you provide in each request. It's the difference between a reference library and an active writing assistant.

Build It Step by Step

Part 1: Create Your Letter Template Library

Before building the project, document your 10 most common letter types. For each:

  • Letter name (e.g., "First Written Notice")
  • Required FDCPA elements (e.g., §809(a) validation notice)
  • Format (business letter, one page)
  • Any client-specific variations (e.g., "Client A prefers no settlement language in first notice")
  • One de-identified example of a good past letter

Create a document:

Copy and paste this
LETTER TEMPLATE LIBRARY — [Agency Name]

1. FIRST WRITTEN NOTICE
   Required: §809(a) validation notice, mini-Miranda, account number placeholder
   Client variations: [note any]
   Tone: Formal, informative
   [Paste de-identified example]

2. DISPUTE ACKNOWLEDGMENT (Written)
   Required: §809(b) verification notice, collection suspension statement
   [Paste de-identified example]

3. CEASE-AND-DESIST ACKNOWLEDGMENT
   Required: FDCPA exceptions noted (legal action, confirm no further contact)
   [Paste de-identified example]

4. SETTLEMENT OFFER
   Required: Clear offer amount, expiration date, payment instructions
   Variation: Check settlement authority before sending
   [Paste de-identified example]

5. BROKEN PTP FOLLOW-UP
   Required: Non-threatening, no new legal threats unless authorized
   [Paste example]

[Continue for all 10 letter types]

Part 2: Build the Letter System Project

  1. In Claude, click Projects → + New Project
  2. Name it: "Letter System — [Agency Name]"
  3. Upload your Letter Template Library document
  4. Also upload your state calling hours and key FDCPA rules from your Compliance Base

In Project Instructions, paste:

Copy and paste this
You are a collection letter writing system for [Agency Name].

When I give you a letter request, produce a complete, formatted letter using the templates in this project as models. Follow these rules:
1. Use the structure and required elements from the corresponding template
2. Adapt language to the specific account context I provide
3. Always check: is every required FDCPA element present for this letter type?
4. Format as a business letter with [ACCOUNT NUMBER], [CONSUMER NAME], [ADDRESS], [DATE] as placeholders
5. Never invent account details I didn't provide
6. Flag any unusual request that doesn't match standard FDCPA practice
7. At the end of each letter, add a one-line compliance checklist: ✓ or ✗ for each required element

Output format:
--- LETTER START ---
[formatted letter]
--- LETTER END ---

COMPLIANCE CHECK:
- [Required element 1]: ✓/✗
- [Required element 2]: ✓/✗

Part 3: Create Your Letter Request Template

Save this as a sticky note or desktop shortcut — you'll use it every time:

Copy and paste this
LETTER REQUEST:
Type: [First Notice / Dispute Ack / Settlement / C&D Ack / Broken PTP / Legal Referral / other]
Balance: $[amount]
Account age: [months since last payment]
Consumer situation: [any known context — unemployment, hardship, dispute reason, etc.]
Client instructions: [any special client requirements]
Prior contact: [brief history — last contact, what happened]
Special note: [anything that affects letter content]

Part 4: Test With 5 Real Accounts

Run 5 different letter types through the system:

Test 1 — First Notice:

Copy and paste this
LETTER REQUEST:
Type: First Written Notice
Balance: $1,850
Account age: 4 months since last payment
Consumer situation: No prior contact, new account
Client instructions: Standard
Special note: None

Review: Does it include the §809(a) validation notice? Is the compliance check accurate?

Test 2 — Dispute Acknowledgment:

Copy and paste this
LETTER REQUEST:
Type: Dispute Acknowledgment
Balance: $3,200
Consumer situation: Consumer disputed in writing, claims debt not theirs
Special note: First dispute, no prior account history with disputes

Review: Does it include §809(b) notice? Does it confirm collection suspension?

Continue for settlement, broken PTP, and C&D acknowledgment types.

Real Example: The Friday Letter Batch

Setup: It's Friday afternoon. You have 12 letters to send before end of day.

Old workflow: Pull each template, edit 8+ fields, manually verify compliance elements, review. 12 letters × 15 minutes = 3 hours.

New workflow:

  1. Open Letter System project
  2. For each account, paste the 7-line letter request form
  3. Review the output and compliance check (2 min per letter)
  4. Copy, paste final details (real name, address), print or email
  5. 12 letters × 4 minutes = 48 minutes

Time saved: ~2 hours, every Friday. Quality improvement: Compliance checklist means no element missed, even under time pressure.

What to Do When It Breaks

  • Letter doesn't include required elements → Check the compliance checklist at the bottom. If it shows ✗, ask Claude: "Add the missing §809(a) validation notice to this letter."
  • Output doesn't match your template style → Add to your project instructions: "Match the tone and structure of the examples in my uploaded template library exactly — don't improvise structure."
  • PHI accidentally generated → This should not happen with placeholder instructions in place. If it does, add to instructions: "CRITICAL: All consumer names, addresses, SSNs, and account IDs must be [BRACKETED PLACEHOLDERS] only."
  • Wrong letter type used → Always specify the exact letter type in your request form — ambiguity produces wrong templates.

Variations

  • Simpler version: Skip the letter system project and use the Compliance Base with a detailed prompt for each letter. Slower but requires less setup.
  • Extended version: Add a client roster to the project (client A, B, C and their specific requirements) so client-specific letter variations are generated automatically.

What to Do Next

  • This week: Build the template library document (the hardest part) and test with 5 letter types
  • This month: Track time spent on letters vs. before — the ROI on this project pays back within the first week
  • Advanced: Connect to Google Sheets via a script to generate account summary inputs automatically from your CMS export

Advanced guide for collections specialist professionals. These techniques use more sophisticated AI features that may require paid subscriptions.