Dunning Cadence Planner: Day-by-Day Sequence

A dunning cadence is the calendar your recovery runs on: which day the next retry fires, which day an email goes out, when a text is justified, and when the whole sequence stops. Without that calendar, retries and messages drift apart — a customer gets a card-update email after they have already paid, or three silent retries burn the window before anyone asks them for a new card. This planner lays out one complete sequence, day 0 to day 16, plus variants for high-value accounts and annual plans.

Pair it with the working assets it schedules: the messages themselves are in our dunning email templates, the text-message layer is covered in dunning SMS, and the tooling choice behind running this automatically is compared in subscription dunning software.

The principles behind the cadence

• One clock. Retries and messages share the same day count, starting at day 0 — the day the regular charge fails. Every touch below is placed against that clock.
• Retries lead early, outreach leads late. In the first days, many failures fix themselves on a well-timed retry. As the window runs down, the customer becomes the only path left, so messages get clearer and more direct.
• Each added touch has a job. Research behind this cadence is specific on one point: each additional dunning email touch adds roughly 1–2 points of recovery, per Churnkey's published analysis of Stripe data. That is a reason to include several considered touches — not a license to send daily. Every email below exists because it says something the previous one did not.
• SMS is a scalpel. Text messages appear on day 1 and day 7 in this plan, following the site's established pattern: an early, short pointer and one mid-sequence escalation. SMS is not repeated at every step; its value is that it is rare enough to be read.
• The sequence ends on purpose. Six attempts over about 16 days, then a clean ending. Hard declines leave the retry track on day 0 — they are never retried — and stay on the outreach track only.

The day-by-day sequence: day 0 to day 16

Day	Retry attempt	Email touch	SMS touch	Escalation note
0	Original charge fails (not a retry). Record the decline code — it routes everything after this point.	Email 1, same day: payment failed, here is the secure card-update link, service continues for now. Plain subject, no alarm.	None.	Hard decline? Leave the retry track immediately; this calendar continues for outreach only. Authentication required? Move to the authentication message, not Email 1's generic wording.
1	Retry 1 for temporary declines such as insufficient funds.	None — Email 1 is still fresh.	SMS 1: one short line naming the brand, the failed payment, and the update link.	Check status before the SMS sends. A customer already recovered by Retry 1 gets neither this text nor anything after it.
2	No retry. A one-day gap lets funds and issuer conditions change.	None.	None.	Quiet day by design. Cadence is spacing, not volume.
3	Retry 2.	Email 2 if Retry 2 fails: shorter than Email 1, restates the update link, names the date access will pause if payment is not fixed.	None.	The grace-period deadline enters the copy from here on. Specific dates outperform vague urgency.
4	No retry.	None.	None.	Watch for replies and support tickets instead. A human conversation at this point replaces the next scheduled touches for that account.
5	Retry 3.	None on the same day as the retry.	None.	If the decline code has changed, re-route the outreach wording to the new cause while keeping this calendar.
6	No retry.	Email 3 if still unpaid: change the angle — what the subscriber will lose, in concrete terms, and one clear update button.	None.	This is the last purely informational email. Later touches carry explicit deadlines and consequences.
7	No retry.	None.	SMS 2: the mid-sequence escalation — payment still outstanding, update link, deadline date.	Day 7 is the planned second and final routine SMS. Any further texting should be part of the high-value variant below, not the standard plan.
8	Retry 4.	None on the retry day.	None.	Past the halfway point of the window: from here, every message assumes the customer, not the calendar, is the remaining path.
9	No retry.	Email 4: direct tone, deadline in the subject line, update link above the fold. Mention any pause or help option your cancellation and save flows offer.	None.	Segment check: high-value accounts leave the standard track here and get the personal touch described in the variant below.
10–11	No retry.	None scheduled.	None.	A deliberate pause before the final stretch. It makes the day-12 message read as an escalation rather than as noise.
12	Retry 5.	Email 5 if Retry 5 fails: final-notice framing begins — this is one of the last attempts, access ends on the stated date without an update.	None.	Confirm the stated end date matches your actual grace period and platform settings. A deadline you do not enforce trains customers to ignore the next one.
13–15	No retry.	None scheduled.	None.	Hold for customer action. Replies, card updates, and support contacts are worked by a person where possible; no new automated touches compete with them.
16	Retry 6 — the final attempt.	Email 6 if the final attempt fails: the closing message. Payment could not be recovered, the subscription ends on the stated date, and here is the simplest way back if they return.	None.	Sequence ends. End the subscription cleanly, record the outcome and decline history, and move the account to reactivation or winback later — not to a seventh retry.

Variant: high-value accounts

For accounts whose value justifies human time, keep the same retry calendar — issuers do not move faster for important customers — and change only the outreach layer:

Day	Change from the standard cadence
3	Email 2 comes from a named person at your company, with a direct reply path, instead of the standard automated sender.
9	Replace Email 4 with a personal outreach: a short, specific note offering help, a call, or a temporary arrangement your policies actually allow.
12	One additional SMS is acceptable here — and only here — if the personal outreach has had no reply. State the deadline and the update link; nothing else.
16	The closing message offers a defined return path and a named contact, so an ended subscription stays a relationship rather than a closed door.

Variant: annual plans

An annual payment is one large charge, so the cost of losing it is higher and the customer's surprise at a large failed charge is greater. Adjust the framing, not the retry count:

Element	Annual-plan adjustment
Pre-dunning	Add a notice before the renewal charge and a card-expiry warning ahead of it. Preventing an annual failure is worth far more than recovering one.
Email 1 (day 0)	Name the full annual amount plainly and confirm what the payment covers. Customers dispute charges they do not recognize; clarity on day 0 prevents that second problem.
Grace period	Keep access running for the full sequence. Cutting off a year-paid customer early over a card problem converts a billing fix into a cancellation decision.
Save options	Where your offers allow it, present the pause and help options earlier — at day 6 rather than day 9 — because the amount at stake makes an assisted save worth offering sooner.
Stop rule	Unchanged: final attempt on day 16, then a clean ending and a return path. A larger amount does not justify extra retries beyond the plan.

Running the cadence without breaking it

• Suppress on success, instantly. Every scheduled retry and message checks the account first. The fastest way to destroy trust in a dunning sequence is to chase a customer who already paid.
• Suppress on conversation. If the customer is talking to support, pause automated touches for that account until the conversation resolves. Two voices at once reads as chaos.
• Keep the sender and page consistent. Emails, texts, and the card-update page should carry the same branding and the same business name the customer bought from, so the sequence reads as your company fixing a problem — never as a third party demanding card details.
• Review the calendar, not just the results. Once a quarter, read the sequence as a customer would, in order, on a phone. Touches that made sense when added one by one often repeat each other when read as a set.

The bottom line

Plan dunning as one calendar: 6 retry attempts across about 16 days, six purposeful email positions, SMS on days 1 and 7, and a stop rule you actually honor. Adjust the human layer for high-value accounts and the framing for annual plans, and leave the retry skeleton alone. A cadence this plain is easy to automate, easy to audit, and easy for a customer to act on — which is the entire point.

Swipe Again runs this kind of sequence for subscription businesses on Stripe, Recharge, Seal Subscriptions, Skio, Loop Subscriptions, Chargebee, Recurly, Braintree, and Paddle: smart retries, branded dunning emails and card-update pages, SMS in the sequence, cancel deflection, and a 90-day backfill on connect, for $179/mo flat with a 14-day trial. The promise: Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days.

Frequently asked questions

How many dunning emails should a sequence include?

This planner uses six email positions across 16 days, each with a different job, from the first failure notice to the closing message. Published analysis of Stripe data by Churnkey found each additional dunning email touch adds roughly 1 to 2 points of recovery, which supports several considered touches rather than one or two.

When should SMS be used in a dunning sequence?

On day 1 as a short early pointer to the update link, and on day 7 as one mid-sequence escalation with the deadline. Keeping SMS to those two planned touches preserves its impact. High-value accounts may justify one further text near the final deadline.

How long should a dunning sequence run?

About 16 days in this plan, holding 6 retry attempts and the full outreach arc. That window is long enough for pay cycles and issuer problems to change, and short enough that the ending still means something to the customer.

What happens at the end of the cadence if payment is not recovered?

The subscription ends cleanly on the stated date, the final email explains what happened and gives the simplest path back, and the account moves to reactivation or winback efforts later. The sequence does not add extra retries beyond the plan.

Should annual plans use a different dunning cadence?

The retry skeleton stays the same. Annual plans add pre-dunning notices before the renewal charge, clearer day-0 wording naming the full amount, and earlier presentation of pause and help options, because the single charge is larger and the cost of losing it is higher.