Dunning Email
Automated emails sent to recover failed subscription payments before they result in churn.
Definition
Dunning emails are automated messages triggered when a customer's payment fails. They notify the customer about the issue and prompt them to update their payment method. For SaaS businesses, dunning is one of the highest-ROI email sequences you can build because it directly recovers revenue that would otherwise be lost to involuntary churn.
Why It Matters
Failed payments cause 20-40% of all SaaS churn, and most of it is preventable. Customers often have no idea their card expired or their bank flagged the transaction. A well-crafted dunning sequence can recover 50-70% of failed payments. That is pure revenue you would have lost without sending a single email.
How It Works
When a payment fails, your billing system (like Stripe) triggers a webhook. Your email platform catches this event and starts a dunning sequence. The first email goes out immediately, explaining the issue and providing a direct link to update payment details. Follow-up emails escalate urgency over the next 7-14 days before the subscription is cancelled.
Best Practices
- 1Send the first email within minutes of payment failure, not hours
- 2Include a direct link to update payment info with no login required if possible
- 3Use a friendly tone in early emails and increase urgency gradually
- 4Send 3-5 emails over 7-14 days before cancelling
- 5Show what the customer will lose access to if not resolved
- 6A/B test subject lines because open rates directly impact recovery
Automated Dunning Sequences
Sequenzy connects directly to Stripe to trigger dunning emails instantly when payments fail. Build multi-step recovery sequences with our visual automation builder.
Learn MoreDunning Sequence Timing Table
| Timing | Message angle | |
|---|---|---|
| 1 | Immediately after failure | Friendly notice with direct payment update link |
| 2 | Day 2-3 | Reminder that the issue is still unresolved |
| 3 | Day 5-7 | Explain access risk and what will be paused |
| 4 | Day 10-14 | Final warning before cancellation or downgrade |
Dunning Failure Reason Table
| Failure reason | Customer likely knows? | Email emphasis |
|---|---|---|
| Expired card | Often no | Quick update link and reassurance |
| Insufficient funds | Sometimes | Retry timing and alternate payment method |
| Bank decline | Rarely | Ask them to contact bank or use another card |
| Authentication required | Often confused | Explain that payment needs approval |
Dunning Recovery Table
| Recovery lever | Why it matters | Example |
|---|---|---|
| Direct billing link | Removes login and navigation friction | "Update payment method" button |
| Product value reminder | Makes the consequence concrete | "Your automations will pause on Friday" |
| Sender identity | Signals the email is operational, not marketing | Billing or account team sender |
| Escalating urgency | Matches the timeline without sounding hostile | Friendly first, clear deadline later |
Frequently Asked Questions
Related reading
- GuideHow to Set Up Failed Payment Recovery Emails (Dunning)
- GuideDunning Email Sequence: Recover Failed Payments and Reduce Involuntary Churn
- Use caseHow to Recover Failed Payments in SaaS With Email
- Use caseThe Complete Guide to Dunning Emails for SaaS
- Templates12 SaaS Dunning Email Templates for Payment Recovery (2026)