Dunning emails are the automated messages you send to a customer when their subscription payment fails, asking them to update their billing details before their account is canceled. They are the front line of failed payment recovery, and they exist to solve a specific problem: a customer whose card expired or got declined did not decide to leave. They are still getting value from your product. They just have a billing problem nobody fixed yet.
This kind of loss has a name, involuntary churn, and it is one of the most fixable leaks in any subscription business. Subscription companies lose an average of around 9% of monthly recurring revenue to failed payments, and most of that is recoverable with a process that costs almost nothing to run. This guide covers what dunning is, how to time and write the emails, the retry logic that does half the work, and the B2B details that quietly decide whether you recover the money or write it off.
What is a dunning email?
A dunning email is an automated notice sent after a recurring payment fails, telling the customer what happened and asking them to update their payment method before they lose access. The word "dunning" just means persistently asking for payment that is owed. In a subscription business it has become the standard term for the email sequence that recovers a failed charge without a human ever picking up the phone.
The reason it matters is that most failed payments are not the customer's choice. A card expires, a bank flags a charge as suspicious, a billing limit is hit, or a one-time network error declines a perfectly good card. The customer still wants your product. If you do nothing, they churn for a reason that had nothing to do with your value. A dunning email turns that silent cancellation back into a thirty-second fix.
What is dunning management?
Dunning management is the whole system for recovering failed payments: the schedule of automatic card retries, the sequence of reminder emails, the in-app messages, and the rules that decide when to keep trying and when to finally cancel. The emails are the visible part, but dunning management is the entire recovery operation that sits between a declined card and a lost customer.
Done well, it is mostly invisible. A charge fails, the system retries it on a smart schedule, a short email goes out, the customer updates their card or the retry succeeds, and they never think about it again. Done badly, it is either silence, where you lose customers without ever asking, or noise, where you bombard people who already paid. The goal is a calm, reliable process that recovers the recoverable and lets go of the rest cleanly.
Why failed payment recovery matters more than most teams think
Failed payment recovery is high-leverage because the customer is already sold. You spent the acquisition cost, they made the buying decision, they are using the product. Winning them back costs a few automated emails. Acquiring a replacement costs five to twenty-five times more than retaining the one you have, which makes recovered revenue some of the cheapest revenue in the business.
The compounding effect is the real prize. A customer you recover through dunning does not just pay this month. They keep paying, on average, for many more months after the save. So a recovery sequence that quietly rescues a few percent of MRR every month is not a small billing chore. It is a retention engine running on autopilot, and it sits right next to the rest of your billing experience, where small errors erode trust fast.
Retry the card before you email anyone
About half of all failed payment recovery comes from automatic card retries alone, before a single email is read. That makes "retry first, email second" the most important structural decision in dunning. Many declines are temporary: a momentary network issue, a bank that approves the same card a day later, an account that gets topped up over the weekend. Retrying on a smart schedule recovers those with zero customer effort.
Smart retry logic spaces attempts to match how these problems resolve. A common pattern retries on the day of failure, then a few days later, then around a week out, avoiding times banks are more likely to decline and favoring times a paycheck has likely cleared. Your payment processor's recovery tools or your billing platform handle this. The point is simple: do not lead with a guilt-trip email when a quiet retry would have fixed it on its own.
When should you send dunning emails?
Send the first dunning email right after the payment fails, then space follow-ups every three to seven days across roughly a thirty-day window before you cancel. The longer you wait after a failure, the lower your odds of recovery, so speed on the first message matters. A typical cadence sends on day 0, day 3, day 7, day 15, and a final notice around day 30.
Each email in the sequence should shift tone as the deadline approaches. The first is a light heads-up: your card did not go through, here is the link to fix it. The middle ones add a little more urgency and remind them what they will lose. The last is a clear final notice with a hard date. You are not nagging; you are giving a paying customer several easy chances to keep something they use before it switches off.
What makes a dunning email actually work
A good dunning email gets to the point in the first two sentences and makes the fix take under a minute. State plainly what happened and what they need to do, then give a one-click link that takes them straight to updating their card without making them log in and hunt for the billing page. Over 70% of card updates happen on mobile, so the link has to work on a phone in a few taps.
The details that lift recovery are small but real:
- Lead with the problem and the fix. "Your payment didn't go through. Update your card here to keep your account active." Everything else is secondary.
- Use a one-click, login-free update link. Every extra step between the email and a working card costs you recovered revenue.
- Send from a person, not "billing@". Emails from an individual see open rates rise around 15% over generic system addresses.
- Use loss aversion honestly. The fear of losing access they already have motivates more than a reminder of benefits. Show exactly what switches off if the card is not updated.
- Offer a way out that is not churn. Add a link to support or a downgrade path. Some declines are affordability, not an expired card, and a cheaper plan keeps a customer a cancellation would have lost.
- Keep it plain and short. This is a transactional message, not a marketing campaign. Clean text, one clear button, no clutter.
The B2B detail most teams miss: email the right person
In B2B SaaS, the person using your product is often not the person who pays the bill. The day-to-day user gets your dunning email, shrugs because it is not their credit card, and never forwards it to the finance contact who can actually fix it. That single mismatch quietly kills recovery rates. Targeting the correct billing contact instead of the default user lifts recovery by roughly 10% on its own.
If your product supports multiple users on an account, send dunning emails to every contact on the account, or at least to the designated billing admin, so the message reaches someone with the card. Make the billing contact a field you capture at signup and keep current. The best-written dunning sequence in the world recovers nothing if it lands in the inbox of someone with no authority to update payment. This is the same back-office discipline that decides so much of whether customer experience holds up: getting the right document, or in this case the right message, to the right person.
A sample dunning email
Here is a clean first email in a sequence. It is short on purpose.
Subject: Your payment didn't go through
Hi Maria,
We tried to charge your card for your monthly Acme plan and it was declined, most likely an expired card or a temporary bank issue. Your account is still active for now.
You can fix it in under a minute here: [Update payment method]
If you have any trouble, just reply to this email and I will help.
Thanks, Daniel, Acme Billing
Notice what it does not do. It does not lecture, threaten, or bury the link under three paragraphs. It says what happened, reassures them their account is still on, gives a one-tap fix, and offers a human if they get stuck. Each later email in the sequence keeps that structure and adds a clearer deadline.
How do you automate dunning?
You automate dunning by using your billing platform or payment processor to run the card retries and trigger the email sequence on a schedule, so failed payments are recovered without anyone watching a dashboard. Most subscription billing tools and processors include dunning features: automatic smart retries, a configurable email cadence, and rules for when to finally cancel. You set the schedule and the copy once, and the system runs it on every failure.
The pieces to configure are the retry schedule, the email timing and content, the billing-contact targeting, and the cancellation rule at the end of the window. Once those are set, dunning becomes a background process that consistently recovers a slice of MRR every month. Automation here regularly returns ten times its cost or more, because it rescues revenue you had already earned and would otherwise have lost to a billing glitch.
Where dunning fits in the bigger billing picture
Dunning is the recovery side of billing, but it works best when the rest of billing is clean. Clear invoices, accurate charges, and a payment page that does not confuse people all reduce the failures and disputes that feed involuntary churn in the first place. For the trust side of that equation, see how invoicing mistakes erode customer trust, and once a customer is recovered, the same operational care shows up everywhere from onboarding to how you measure churn. Dunning is not a finance afterthought. It is one of the clearest places where back-office operations directly decide whether a customer stays.