A dunning sequence is the recovery journey you trigger when a payment fails. Email on day 1, SMS on day 3, email on day 5, final warning on day 7. A series of automated messages that guide the customer toward fixing the problem.
Without this sequence, a failed payment leads straight to churn. With a well-designed sequence, you can recover 50-70% of these payments.
Anatomy of a dunning sequence
A typical sequence lasts 7-14 days and contains 4-6 touchpoints. Here's an example:
Day 0 — First failure The payment fails. You trigger an automatic retry and send a first informational email. Neutral tone, no urgency. "Your payment didn't go through — here's a link to update your card."
Day 2 — First reminder The retry failed too. Second email, slightly more direct. "We tried again, it didn't work. Your subscription will be suspended if you don't update your card."
Day 4 — SMS Emails might not be getting read. A short, direct text message. "Your [Product] payment failed. Update your card: [link]"
Day 6 — Urgent email The tone shifts. "Final reminder before suspension. Your access will be disabled in 48 hours if we don't receive your payment."
Day 8 — Suspension No response. Subscription suspended. One more email explaining how to reactivate the account.
Day 14 — Last message A week after suspension. "We miss you. Your account is still there — just update your card to pick up where you left off."
What makes a good sequence
Progressive urgency. Start friendly and informational, end urgent. Not the other way around. The first email shouldn't scare anyone.
Clear call to action. Each message contains ONE link to ONE action: update the card. No distractions, no other CTAs.
Multi-channel. Email alone doesn't cut it anymore. Average open rate is 20-25%. Add SMS for critical messages — read rate > 90%.
Basic personalization. First name, product name, amount due. That's enough. No need for sophisticated personalization, just the useful info.
Smart timing. No messages on Sunday. Avoid end-of-month for "insufficient funds" cases. Tuesday and Wednesday mornings work well.
What separates good from bad
Bad sequence:
- 3 identical emails saying "Your payment failed"
- Robotic, corporate tone
- Link that goes to the login page
- No SMS
- Suspension after 3 days with no warning
Good sequence:
- Progressive messages with different angles
- Human, direct, jargon-free tone
- Direct link to card update page (no login if possible)
- SMS for critical moments
- Clear grace period with countdown
Adapting to the failure type
Not all failed payments deserve the same sequence.
For a soft decline (insufficient funds, temporary error): shorter sequence, more automatic retries, fewer emails. The payment might go through on its own.
For a hard decline (expired card, invalid): longer sequence, no pointless retries, focus on card update. Only the customer can fix this.
How long before you cut them off?
Your grace period length depends on your business:
B2B SaaS (high-ticket): 14-21 days. These customers pay a lot, they deserve more time. And decision-makers might be on vacation.
B2C SaaS (low-ticket): 7-10 days. Shorter cycles, more responsive customers.
Physical subscriptions: 10-14 days. You have shipping costs, but cutting too fast loses the customer forever.
Test and measure. The right timing maximizes recovery without losing too much revenue to "freeloaders" who use the service without paying.
Automate without losing the human touch
A dunning sequence is automated by definition. But that doesn't mean it should sound like a robot.
Write your emails as if you were sending them to a specific customer. Read them out loud. If it sounds fake, rewrite it.
The best dunning messages are the ones you don't recognize as automated. Short, direct, useful. No "Dear customer," no "We regret to inform you," no "Please do not hesitate to contact us."