KoltrixDunning Emails That Recover Failed Payments Without Anger
A five-email dunning sequence for failed SaaS payments: what each message says, when it goes out, and copy rules that recover revenue without upsetting anyone.
On this page(7 sections)
When a subscription payment fails, the customer usually hasn't decided to leave. Their card expired, a bank flagged the charge, or the company card hit its limit. Dunning emails exist to fix that quietly, and the worst thing they can do is make a loyal customer feel accused.
Here's a sequence that recovers payments while keeping the tone right, plus the copy rules that matter more than any template.
How dunning fits with payment retries
Most billing systems retry a failed charge automatically over a period of days or weeks. Retries alone recover some payments, because temporary declines often clear. Emails cover the cases retries can't fix: an expired or cancelled card, a card that needs replacing, or a payment that needs the customer to approve it.
So your dunning emails should line up with your retry schedule. Decide three things first:
- How long is the retry window? For example, 14 or 21 days.
- What happens to the account during the window? Ideally, nothing: full access continues.
- What happens when the window closes? Downgrade, read-only, pause or cancellation.
Write those down. Every email will refer to them.
The sequence
| # | When | Purpose | Tone |
|---|---|---|---|
| 1 | Immediately after the first failure | Inform, assume an innocent cause | Neutral, brief |
| 2 | About 3 days later, if unresolved | Remind, make the fix effortless | Helpful |
| 3 | About a week in | Explain what happens and when | Clear, still friendly |
| 4 | Two to three days before the window closes | Final notice with the exact date | Direct, not threatening |
| 5 | When the window closes | Confirm what changed, how to restore | Calm, door open |
If a payment succeeds at any point, the sequence stops and, ideally, a short confirmation goes out: "Thanks, your payment went through. Nothing else to do."
Email by email
1. First notice
Subject: Your payment for Acme Analytics didn't go through
Hi Sam,
We tried to charge the card ending 4242 for your monthly plan today and the payment was declined. This usually happens when a card expires or a bank blocks a charge.
You can update your payment details here, and it takes about a minute: [Update payment method]
Your account is working as normal, and we'll retry the charge automatically over the next few days.
(Acme Analytics is a hypothetical product.) Notice what's there: the product name, the card's last four digits, a likely innocent explanation, one link, and reassurance that nothing has changed.
2. Reminder
Short and practical. Repeat the link. If you can see the decline reason, use it: "The card on file expired at the end of last month" is more useful than "payment failed." Mention that if someone else handles billing, they can forward the email, and make sure the update link works for a different person, without requiring the original user to log in.
3. What happens next
Now explain the consequence, plainly and with a date:
If we can't collect payment by 21 March, your workspace will switch to read-only. Your data will stay safe and exportable, and you can restore full access any time by updating your card.
This is the email where precision matters most. Only promise what your system actually does.
4. Final notice
Name the date in the subject line ("Action needed by 21 March to keep your workspace active") and keep the body to three or four sentences. Offer a reply path for customers who need an invoice, a different payment method, or a few extra days.
5. Window closed
Confirm what changed, how to restore it, and what happens to data over time. No guilt, no "we're sad to see you go." Many customers who reach this point will fix it within a day of seeing this email, and you want that to feel easy.
Copy rules that matter more than templates
Link straight to the payment update page. Not the login page, not the dashboard. Every extra step loses people. If you can, use a secure link that works without logging in.
Never shame. Avoid "your account is delinquent," "overdue," or "failure to pay." The customer probably doesn't know anything went wrong.
Write in plain text, or close to it. Dunning emails that look like marketing get ignored or filtered. A simple, personal-looking message reads as important.
Send from a replyable address. Billing problems generate questions: "Can I pay by bank transfer?", "Our finance team needs a PO number." A noreply@ sender turns each of those into a churned account. Route replies to someone who can act on them.
Address the right person. The user who signed up may not be the person who pays. Let customers set a billing contact, and send dunning emails to both when one exists.
Mind security. Phishers imitate payment-failure emails. Never ask for card numbers by email, keep sender addresses and branding consistent, and make sure your domain has SPF, DKIM and DMARC in place so imitations are easier for mail providers to catch.
Before you write a single email
Many failed payments can be prevented. Emailing customers before a card expires, while there's still time to update it calmly, is often more effective than any dunning sequence. We cover that in fixing expiring cards before they fail.
Measuring recovery
Track per month:
- Failed payments, split by decline reason where available.
- Payments recovered by automatic retries without any customer action.
- Payments recovered after each email, attributed to the most recent email before the update.
- Accounts that reached the end of the window, and how many came back afterward.
These numbers tell you whether to adjust timing, copy or the retry schedule itself.
Key takeaways
- Align dunning emails with your retry window, and decide the end-of-window consequence before writing.
- Five emails is enough: inform, remind, explain, final notice, confirm.
- Link directly to the payment update page and keep the account working during the window.
- Plain, polite, replyable emails recover more than alarming ones.
- Prevent what you can with pre-expiry reminders.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
