Using AI in accounts
How to use Claude to write payment reminders that don't sound like a robot
Most people's first AI-written reminder reads exactly like an AI wrote it — three exclamation marks, "I hope this email finds you well," and a tone so polite it's easy to ignore. Here's how to get Claude to actually sound like you, and where it should stop.
Give Claude your actual past messages as examples, tell it the specific invoice and days overdue, and ask for three drafts at three tones — not one "perfect" message. Read every draft before it goes anywhere. Never wire Claude directly to your WhatsApp or email.
Why the obvious way fails
Type "write a polite payment reminder for an overdue invoice" into Claude and you'll get something technically correct and completely useless: generic, over-formal, and identical to what every other business using the same prompt gets. Customers who've seen a hundred templated reminders can tell in one line. The fix isn't a cleverer one-line prompt — it's giving Claude enough real context to write something specific.
The prompt that actually works
Give it four things every time, not one:
- The actual details — customer name, invoice number, amount, due date, days overdue. "An overdue invoice" produces a generic message; "₹84,500, invoice #INV-2291, due 12 July, now 38 days overdue" produces a specific one.
- The relationship — is this a long-standing customer who's never been late before, or someone who's been chased three times already? The tone should be completely different, and Claude has no way to know unless you say.
- Two or three of your own past messages — paste in whatever you'd normally write by hand, even a rough WhatsApp message. Claude will match your actual voice far better than any tone instruction like "be friendly but firm."
- What happens next if this doesn't work — so the draft can end with something concrete rather than trailing off vaguely.
"Draft a WhatsApp message to Ramesh at Verma Traders. Invoice #INV-2291 for ₹84,500 was due 12 July, it's now 38 days overdue, this is the first time we've had to chase them and they've always paid on time before. Here's how I usually write to customers I know well: [paste 2-3 real past messages]. Keep it under 3 lines. Give me two versions — one direct, one a bit softer."
The three tones, and when to actually use them
| Tone | When | What to tell Claude |
|---|---|---|
| Gentle | First reminder, good payment history | "Assume this is probably an oversight, not avoidance — no threats, no urgency language." |
| Firm | Second reminder, or a customer who's been late before | "State the amount and date plainly. One sentence on what happens if it's not resolved this week." |
| Final | Third reminder, before you escalate | "State this is the final reminder before [legal notice / stopping supply / whatever is actually true]. Don't soften it, but don't be aggressive either." |
What Claude is genuinely good at here
- Adjusting length for the channel. A WhatsApp reminder that reads well needs to be under two or three lines; an email can carry more context. Ask for both from the same brief rather than writing twice.
- Translating tone, not just words. Ask it to keep the same directness in Hindi or another language rather than a literal translation — a literal translation of an English "firm" reminder often reads as rude in Hindi, and vice versa.
- Catching a message that's about to backfire. Paste a draft you've written and ask "does anything here sound accusatory or could be read as a threat?" before you send it to a customer who's also a friend of your biggest client.
Where to stop — and why this matters more than it sounds
Don't connect Claude directly to your WhatsApp Business API or email to send messages automatically. Three reasons, not one:
- A wrong amount in an automated message is a real liability. If Claude hallucinates a figure, or you fed it stale data, an auto-sent message with the wrong number is now in writing, sent to a customer, with your business's name on it.
- Escalation should be a human decision. Whether Kumar Traders gets a "final notice" today or next week is a judgement call about the relationship, not something to hand to a model that doesn't know Kumar personally chased you down at a wedding to apologise last time.
- A draft is reversible. A sent message isn't. Every serious workflow here should have a human read-and-send step — the model drafts, you decide.
This is also why we built Collection Plan the way we did: the ranked call list and escalation ladder are deterministic — no AI in the numbers — and every message still goes through a real "Open WhatsApp" tap, never an auto-send. If you want the drafting help this guide describes plus the actual list of who to chase and when, that's the other half of the job — see using Claude for daily reporting next, or jump straight to the prompt list in Claude prompts for chasing overdue invoices.
Upload your Tally outstanding report and Collection Plan tells you who to call, who to message, and who to leave alone — with the reminder wording editable in your own words, not a template. No signup for the free health check.
Run a free health checkNext: The full Claude collections playbook · Claude for daily finance reporting · 25 Claude prompts for accounts teams · Reminder message formats