Dunning emails that actually recover revenue

6 min read · Copy you can steal, and the psychology behind each message

"Dunning" is the industry's ugly word for a simple thing: emailing customers whose payment failed and asking them to update their card. Done badly, it's nagging. Done well, it reads like good customer service — and it recovers 30-40% of failed revenue. Here's the 3-email sequence that works, and why each message is shaped the way it is.

The golden rules first

• Assume goodwill. The customer didn't stiff you; their card expired. Every email should read like you're doing them a favor, because you are — you're saving their account.
• One link, above the fold. Every email has exactly one job: get the click to the card-update page. Don't bury it under feature announcements.
• Short beats thorough. Nobody reads a 400-word billing email. Say what happened, say how to fix it, get out.
• Space them out. Day 1, day 4, day 7 is the standard cadence. Daily emails train people to ignore you; monthly emails let accounts die quietly.

Email 1 (Day 1): The friendly heads-up

Tone: casual, helpful, zero pressure. Most customers who will ever update their card do it after this email — it catches everyone who just needs a nudge.

Subject: Quick heads-up: your payment didn't go through

Hi {{first_name}}, just a quick heads-up — we tried to charge {{amount}} and the payment didn't go through. Usually just an expired card, nothing to worry about. Update it here (30 seconds): {{update_card_url}}

Why it works: it normalizes the situation ("usually just an expired card"), minimizes effort ("30 seconds"), and asks for exactly one thing.

Email 2 (Day 4): The firmer nudge

Tone: direct, slightly urgent, still warm. This one converts the procrastinators — people who meant to do it and forgot.

Subject: Your subscription is at risk — update your card

Hi {{first_name}}, we still haven't been able to process your {{amount}} payment, and your subscription will be paused soon. Update your card here: {{update_card_url}}. Reply to this email if you're having trouble — a human reads every reply.

Why it works: it names a consequence (paused subscription) without threats, and the "human reads every reply" line catches edge cases — wrong email on file, company card issues, people who actually want to cancel.

Email 3 (Day 7): The final notice

Tone: plain, factual, respectful. This is the last touch before cancellation. Keep it short and give the graceful exit.

Subject: Final notice: keep your account active

Hi {{first_name}}, final notice — we've tried to collect {{amount}} three times. Your subscription cancels tomorrow unless your card is updated: {{update_card_url}}. If you meant to cancel, no hard feelings.

Why it works: the deadline is real and specific ("tomorrow"), and offering the graceful exit paradoxically saves accounts — some people update the card precisely because you didn't guilt them.

What the data says

Across dunning tools, email #1 typically drives 50-60% of all recoveries, #2 drives 25-30%, and #3 picks up the remaining 10-15%. That distribution is why you don't skip straight to the final notice — you'd leave most of the money on the table and annoy everyone in the process.

Personalize the variables that matter — first name, amount, a direct card-update link — and keep the "from" name a human or your company, never "noreply." Replies to dunning emails are disproportionately from customers with real billing problems your automation can't solve.