Visit Website →
← Back to blog

Recover Subscription Revenue with Dunning Emails (5–7 Touch Plan)

September 6, 2026
Recover Subscription Revenue with Dunning Emails (5–7 Touch Plan)

This article gives you ready-to-copy dunning email templates and a recommended five to seven touch sequence for recovering failed subscription payments. You'll find templates for pre-due reminders through final warnings, subject-line formulas that improve open rates, and the cadence to send them on. Subscription businesses and membership managers can pull these straight into their billing automation today.

TL;DR:

  • Sending automated dunning emails in a five to seven touch sequence over 45 to 60 days can recover most overdue payments without losing customers.
  • Subject lines should include invoice numbers and dollar amounts, with early emails focused on facts and later messages emphasizing suspension dates.
  • Personalization, clear payment details, and consistent cross-channel links significantly increase open and payment rates.
  • Automated retry rules should align with billing processor schedules, and high-value accounts benefit from earlier manual outreach.
  • Gradually escalating language from gentle reminders to formal notices and final warnings helps retain customer goodwill while prompting payment.

Table of Contents

Dunning Email Examples for Every Stage of the Sequence

A dunning email is a transactional message triggered by a failed or overdue payment, built to recover the charge or get billing details updated before the customer's access lapses. Stripe frames these messages as customer-experience moments, not just collections notices, and that distinction shapes everything below. The goal is money recovered without a customer lost.

Each template follows the three-sentence structure Mailchimp recommends: what happened, what to do, what happens next. Keep that skeleton and swap the tone as the sequence escalates.

  1. Pre-due reminder (3 days before charge). Subject: "Your subscription renews on [Date]." Body: "Your plan renews on [Date] for [Amount]. No action needed if your card on file is current. Update your payment method here: [Link]." This one is pure courtesy, not dunning yet, but it prevents half your failures before they happen.

  2. Gentle reminder (day of failure). Subject: "We couldn't process your payment." Body: "We tried to charge your card on file for [Amount] and it didn't go through. Update your payment info here: [Link]. Your account stays active for now." Keep this warm. Assume it's a mistake, not neglect.

  3. Second notice (day 3 to 5). Subject: "Action needed: Invoice #[Number]." Body: "Your payment for [Amount] is still outstanding. Please update your card or retry payment: [Link]. We'll try again automatically, but updating now avoids any interruption." This is where you name the invoice number for the first time. AP clerks and busy founders start scanning for it here.

  4. Firm follow-up (day 10 to 14). Subject: "Your account is at risk of suspension." Body: "Invoice #[Number] for [Amount] remains unpaid after two attempts. Update your payment method within 5 days to avoid a pause in service: [Link]. Reply to this email if you're facing an issue we can help with." Add the door for disputes here, not later.

  5. Formal notice (day 21 to 30). Subject: "Final notice before service suspension." Body: "Your account will be suspended on [Date] unless Invoice #[Number] is paid. Pay now: [Link]. Contact us if you need a payment plan." State the consequence plainly, no threats, just facts.

  6. Final warning (day 45 to 60). Subject: "Your account has been suspended." Body: "Access has been paused due to non-payment of [Amount]. Restore your account instantly by paying here: [Link]. Unresolved balances may be sent to collections after [Date]."

Segment by customer value before you send: a high-lifetime-value account might skip straight to a human email at stage four instead of an automated one.

Cadence and Sequence: When to Send Each Touch

A high-performing dunning sequence runs five to seven emails over 45 to 60 days, starting before the charge date and ending with escalation to collections if nothing lands. Here's the timing that maps to the templates above:

  1. Day minus 3: pre-due reminder.
  2. Day 0: gentle reminder, sent the moment the charge fails.
  3. Day 3 to 5: second notice, first mention of the invoice number.
  4. Day 10 to 14: firm follow-up, first mention of suspension risk.
  5. Day 21 to 30: formal notice with a hard suspension date.
  6. Day 45 to 60: final warning and account pause.
  7. Day 60+: collections referral if there's still no response.

Retry logic matters as much as the copy. Most processors retry the card automatically two to four times across the sequence, so build your emails around those retry windows instead of hammering the customer daily. Disputed charges or enterprise accounts should exit the automated track entirely. Segmenting high-value accounts for earlier human outreach protects the relationships that matter most while your automation handles the long tail.

If your accounts receivable team is small, a shorter five-touch cadence over 30 days keeps workload manageable. Higher customer lifetime value justifies a longer runway and more manual checkpoints before suspension.

Subject Lines That Actually Get Opened

Subject lines carry more weight than most founders assume, since lines with invoice numbers, dollar amounts, or explicit action phrases consistently outperform vague ones. Skip the alarmist tone. AP clerks scan for one thing first: the invoice reference.

Formulas that work at each stage:

  • Early stage: "Invoice #[Number] — Payment due [Date]"
  • Mid stage: "Action required — Invoice #[Number]"
  • Late stage: "Your account will be suspended on [Date]"
  • Final stage: "Final warning before account escalation"

Industry analyses show early-stage factual subject lines and late-stage authority lines both tend to post stronger open rates than generic prompts like "Payment reminder." Avoid all-caps and words like "urgent" in the subject itself. They trip spam filters and read as aggressive before the recipient has even opened the email.

Best Practices: Personalization, Payment UX, and Multichannel Nudges

Every dunning email should carry enough detail that the recipient doesn't have to dig for context. Stripe notes that showing the exact amount, invoice number, and last four digits of the card on file cuts the chance the email gets dismissed as spam.

  • Include invoice number, amount owed, and card's last four digits in every body.
  • Personalize beyond the first name: reference plan tier, renewal date, or usage if you have it.
  • Make the CTA a single click that lands on a pre-filled payment or card-update page.
  • Offer a second payment method (bank transfer, alternate card) for customers whose primary card keeps failing.
  • Layer in SMS or in-app nudges starting around the firm follow-up stage, not before.

Pro Tip: Keep the payment link identical across every channel, email, SMS, and in-app. A mismatched link between your email and your text message forces the customer to start over, and that friction is where recoveries die.

Coordinating channels pays off specifically because the call-to-action stays consistent across touchpoints, so the customer never has to relearn the flow.

How to Word Escalation Without Losing the Customer

Consequences should show up gradually, not all at once. Mention suspension risk starting at the firm follow-up stage, name a specific suspension date at the formal notice stage, and only mention collections in the final warning. Keep the language neutral and factual: "Access will be paused on [Date]" reads better than "We will cut off your account."

Route any reply that mentions a dispute, a billing error, or a hardship straight to a human, and pause automation for that customer immediately. A staged escalation policy tied to account value lets your team focus manual attention where it earns the most back, and your cancellation flow should offer a graceful off-ramp instead of a dead end.

Measuring What Actually Works

Track four numbers: payment recovery rate, MRR recovered, open and click-to-pay rate, and reply rate (your signal for disputes). These four cover both the financial outcome and the friction points in your copy, according to Postmark's dunning measurement guide.

Run these tests one variable at a time:

  • Subject line wording (factual versus urgent framing)
  • CTA button copy ("Update card" versus "Pay now")
  • Sender name (a founder, a billing team, or an automated "Billing" address)
  • Send time (morning versus afternoon)

Testing sender name alone often moves open and click rates measurably, so don't skip it just because it feels like a minor detail. If recovery rate stalls for two consecutive cycles, revise your cadence before you touch the copy again.

Aria's Checklist for Automating Your Dunning Sequence

Turning these templates into a working sequence takes four setup steps. First, map dynamic tokens (invoice number, amount, card digits, renewal date) so every email auto-fills correctly. Second, set retry rules that match your processor's automatic retry schedule. Third, add channel fallbacks so a failed email touch triggers SMS or in-app follow-up. Fourth, build exception routing so disputes or high-value accounts skip straight to a human inbox.

Four steps for automating dunning workflows

Automating this workflow removes the manual chasing that eats an AR team's week and closes the gap where involuntary churn usually starts. For the mechanics of building the trigger logic, see Aria's guide to email automation workflows.

What a Dunning Email Is For (and Why It's Not Just Collections)

A dunning email exists to solve one narrow problem: a payment that should have gone through didn't. That's different from a collections letter chasing a debt the customer never agreed to. In subscriptions, the customer already said yes once, at signup, and usually wants to keep their access. The card just expired, or the bank flagged the charge, or the billing address changed.

That framing changes the job of the email. Its purpose is twofold: recover the specific payment, and prevent involuntary churn, the kind of cancellation nobody chose on purpose. Stripe's research treats these as customer-experience touchpoints rather than collections notices, and that's the right lens for a subscription business specifically, where the customer relationship is ongoing rather than one-and-done.

Involuntary churn is a bigger problem than most founders budget for, since a meaningful share of subscription cancellations trace back to a card decline rather than an actual decision to leave. A well-built dunning sequence recovers a chunk of that revenue automatically, before a human ever has to get involved. Get the first two or three emails right, factual, low-pressure, easy to act on, and most customers fix the problem themselves without ever feeling chased. For more on how billing recovery ties into overall retention, see Aria's guide to membership retention strategies.

A Balance Worth Getting Right

A Balance Worth Getting Right — overview diagram

The instinct with failed payments is to escalate fast, because unpaid invoices feel urgent. That instinct is usually wrong for the first half of the sequence. Most failed payments are logistical, not intentional, and treating every one like a delinquent account burns goodwill you didn't need to spend.

Where I'd push back on the conventional approach: too many teams write their formal notice the same way they write their pre-due reminder, just with scarier words. Escalate the tone gradually and only as slowly as the calendar demands. Test your templates in small batches before rolling them out fully, and let the recovery rate tell you whether your firmer language is working or just annoying paying customers. If you're managing this across dozens of touchpoints a week, automation isn't optional. It's the only way to keep the tone consistent at scale.

— Anastasia

Put These Templates on Autopilot with Aria

Copying templates into a spreadsheet works for a handful of customers. It breaks down fast once you're running hundreds of subscriptions through manual reminders. Aria replaces that patchwork with dynamic tokens that auto-fill invoice details, retry rules tied to your billing cycle, and fallback channels that move a stalled email into SMS or an in-app nudge automatically.

Aria

Every template above, from the pre-due reminder to the final warning, can be built once inside Aria's automation builder and applied across your entire customer base, with exception routing that pulls disputed or high-value accounts into a human queue instead of the automated track. If you're currently juggling separate tools for email, SMS, and payment recovery, this is where those costs start adding up. See how the full platform handles billing recovery alongside everything else you run, or head to Aria's homepage to start building your first sequence today.

Sources