The Dunning Sequence That Actually Recovers Failed Payments (Timing + Templates)
A day-by-day dunning sequence for failed payments: retry timing, email and SMS templates, and when to add a call. Built for subscription teams losing revenue.
Pratheek Adi
Co-Founder & CTO
Table of contents
Share
Every failed payment starts a race. Recover it in the first week and the customer barely notices. Let it sit a month and you are running a win-back campaign for someone who never meant to leave. Recurly’s network data shows involuntary churn running at a 1.25% annual median across industries, and businesses that work failed payments as a program have collectively recovered nine figures, including more than $155 million in SaaS alone.
An effective dunning sequence pairs silent card retries with escalating human-feeling outreach over about three weeks: a pre-dunning notice before renewal, an immediate retry on failure, friendly emails on days 3 and 7, an SMS on day 7, a call around day 12, and a final notice by day 18. The customer is treated as someone worth keeping, because they are.
Why Do Dunning Sequences Fail?
Most sequences fail in one of three ways. They rely on retries alone, so every hard decline, like an expired or cancelled card that will never clear, slips through untouched. They send robotic payment-failure emails that read like accusations. Or they stop after two emails, when a meaningful share of recoveries happens after the second touch.
The fix is not more messages. It is the right message, on the right channel, at the right hour of the sequence. Understanding what is involuntary churn helps here: the customer has not left. You are not collecting a debt from a stranger; you are helping a customer keep something they chose to buy.
The Day-by-Day Dunning Sequence
Day | Action | Channel | Tone |
|---|---|---|---|
Day -3 | pre-dunning expiry notice | helpful heads-up | |
Day 0 | silent retry by decline code | none | none |
Day 3 | friendly flag | warm, no blame | |
Day 7 | follow-up plus text | email and SMS | specific, soft deadline |
Day 12 | personal call | phone | warm, conversational |
Day 18 | final notice | honest, specific date | |
Day 21+ | lapse and move to win-back | none | new track |
Three days before renewal: the pre-dunning notice
Check for cards expiring this cycle and notify only those customers. One line does it: a heads-up that the card on file expires this month, with a link to update it in 30 seconds. Pre-dunning is the cheapest recovery you will ever run, because it happens before there is anything to recover.
Day 0: the failure and the silent retry
The charge fails. Do not email yet. Soft declines, like insufficient funds, temporary holds, and issuer timeouts, often clear on their own within days, and messaging a customer about a payment that fixes itself creates friction for nothing. Let retry logic take the first swing, timed by decline code rather than a fixed schedule.
Day 3: email one, the friendly flag
If retries have not cleared it, the customer enters the sequence. The template: “Hi there, we tried to process your renewal and the payment did not go through. This is usually a card expiry or a bank hiccup, nothing dramatic. You can update your details in 30 seconds here. Your access is unchanged for now.” No shame, no red banners, a deadline implied but not threatened, one link, one action.
Day 7: email two plus SMS
Two channels, same day, different jobs. The email adds specificity and a soft consequence: “Quick follow-up: your payment is still pending after a couple of attempts. To keep your account active past the renewal date, update your card here. If something is off on our end, reply and a human will sort it.” The SMS is shorter: your renewal payment did not go through, keep your access here, reply HELP with questions. SMS earns its place in dunning because failed payments are often an attention problem, and texts get seen.
Day 12: the call
This is the step almost nobody runs at scale, and the step that separates real recovery programs from email drips. A short, warm call recovers customers the inbox never reached: the email went to spam, the customer meant to fix it and forgot, or there is a question a template cannot answer. The economics used to make calls impossible below enterprise ARPU. An AI voice agent changes that math completely; calling 300 lapsed subscribers costs the same effort as calling three.
Day 18: the final notice
Honest, specific, still kind: “Your account will pause on the stated date because we have not been able to process payment. Updating your card now keeps everything exactly as is. If you have decided to move on, no hard feelings, though we would love to know why.” That last clause matters. If the customer is actually cancelling, learning the reason converts a silent lapse into retention data.
Day 21 and beyond: lapse and win-back
Pause access, keep the data, and move the customer to a win-back track with a different tone and cadence. The dunning sequence is over; do not keep sending payment-failure emails to someone who has lapsed.
What Makes Dunning Messaging Work?
Sound like a person
Templates should read like a helpful teammate wrote them, not a billing system. Contractions, first names, one idea per message. Every message should pass the test: would you be comfortable receiving it?
One action per message
Every touch has exactly one link and one job: update the card. No plan upsells, no surveys, no newsletter footer.
Escalate consequence, never tone
The stakes rise across the sequence, from access date to pause to lapse, but the warmth stays level. The customer did nothing wrong. Their card did. The same principle drives our past-due invoice email sequence on the B2B invoicing side.
Segment by value and history
A subscriber three years in deserves a call earlier. A high-value account might get a human call instead of an AI one. A serial failed-payer might get a nudge toward a payment method that fails less often.
Where Abivo Fits
Abivo runs this entire sequence as an AI employee. Kate sends the emails and texts, makes the day-12 calls in a natural voice, recovers the card update or the payment, and escalates the conversations that need a human, which in practice is about 14% of them; the other 86% resolve autonomously. Subscription teams also get monthly insight reports on why customers churn, summarized from real conversations. Most teams are live in under a week.
Curious what this sounds like in practice? Here’s a 98-second sample call: https://abivo.ai/#live-demo
Practical Takeaways for Subscription Teams
Run prevention first: pre-dunning notices to expiring cards and automatic card updates kill failures before they happen.
Give silent retries 72 hours before messaging. Soft declines often self-heal, and premature emails create needless friction.
Use three channels, not one. Email carries detail, SMS wins attention, calls recover what both miss.
Escalate consequences, not tone. Warm and specific beats stern and vague at every step of the sequence.
End the sequence deliberately. At day 21, lapse cleanly and switch to win-back; perpetual dunning trains customers to ignore you.
Frequently Asked Questions
What is a dunning sequence?
A dunning sequence is the scheduled series of payment retries and customer messages, across email, text, and calls, that a business runs after a recurring payment fails, designed to recover the payment before the subscription lapses.
How long should a dunning sequence run?
About three weeks. Recovery odds decay with every day past the failure, so front-load the sequence: retries in the first 72 hours, first email by day 3, multi-channel contact by day 7, and a final notice around day 18.
How many dunning emails should I send?
Three emails is the practical core: a friendly flag at day 3, a follow-up at day 7, and a final notice near day 18, supplemented by SMS and a call. More than four emails adds annoyance faster than recovery.
Should dunning messages include a phone call?
Yes, where economics allow. Calls recover customers email never reaches. AI voice agents now make per-customer calls viable even at low ARPU, which historically was the blocker.
What is the difference between dunning and collections?
Dunning recovers failed recurring payments from current subscribers, usually a card problem. Collections recovers overdue invoiced receivables in B2B relationships. The tone, timing, and tools differ, though both reward fast, consistent, human-feeling follow-up.
Want this sequence running for your subscribers next week? Get Started.
