The Dunning Email Sequence: What to Send and When
A dunning email sequence is not a set of templates. It is a coordinated communication plan that varies by decline code, respects retry timing, and treats the customer as a person rather than a billing error.
Contents
Most dunning email sequences are built wrong. They are a fixed set of templates sent on a fixed schedule to every customer whose payment failed, regardless of why it failed or what the retry status is.
That approach recovers 30 to 42 percent of failures. A properly structured sequence recovers 60 to 80 percent. The difference is in three decisions: what triggers an email, what the email says, and when it fires relative to retries.
Decision 1: What triggers the email
The most important decision in a dunning sequence is not what the email says. It is whether an email should be sent at all, and when.
For soft declines, the answer is: not yet. generic_decline, do_not_honor, insufficient_funds, and processing_error should trigger a silent retry first, not an email. Most resolve within 24 to 72 hours without the customer ever knowing a failure occurred. Emailing immediately creates unnecessary friction and can alarm a customer over a problem that was never theirs to solve.
For hard declines, the answer is: immediately. lost_card, stolen_card, and do_not_try_again will never resolve on a retry. Email on day 1.
For card data errors, the answer is: immediately. expired_card and incorrect_cvc require customer action. Email on day 1.
Triggering emails on the wrong schedule is the most common reason dunning underperforms, and it starts with this single decision.
Decision 2: What the email says
The most common dunning email mistake is writing for a payment processor rather than for a person.
"Your payment of $79.00 for [SUBSCRIPTION NAME] on [DATE] has failed. Please update your payment method by clicking the button below to avoid service interruption."
That email gets ignored. It sounds like an automated system. It does not tell the customer anything useful. It implies their service is about to be cut off. It creates anxiety without giving the customer a reason to act quickly.
A better version:
"Hi [NAME], we had a small issue processing your last payment. Nothing to worry about, it happens. Could you take a moment to update your card? [Link]. Takes about 30 seconds."
Same information. Completely different tone. Customers who receive emails that read like a person wrote them click and update at meaningfully higher rates.
The email should:
- Use the customer's name
- Acknowledge the issue without technical jargon
- Not mention decline codes
- Include a single clear call to action with a direct link
- Be short. Three sentences maximum for the first email.
Decision 3: When it fires relative to retries
The email schedule and the retry schedule must be coordinated. A retry that succeeds on Tuesday should cancel the email scheduled for Wednesday. An email that fires on day 5 should be followed by a retry attempt on day 5, not day 7, so the customer reads the email and the retry fires while they are thinking about it.
The optimal coordination by decline type:
Soft declines (generic_decline, do_not_honor, insufficient_funds):
- Day 1: silent retry
- Day 3: silent retry
- Day 4: email (if day 1 and day 3 retries both failed)
- Day 7: retry and email follow-up in the same window
- Day 14: final email
Hard declines (lost_card, stolen_card, do_not_try_again):
- Day 1: email immediately, no retries
- Day 7: email follow-up
- Day 14: final email
Card data errors (expired_card, incorrect_cvc):
- Day 1: email immediately, no retries
- Day 3: email follow-up
- Day 7: final email
The follow-up email
Most businesses get the first email roughly right and then stop. The first email reaches about 40 to 50 percent of customers. The second email reaches a meaningful additional share. The third catches stragglers.
Each follow-up should acknowledge that you have reached out before. "Just checking in" is better than sending the same email again. The second email can add a little more context: "Your access is still active, and we want to keep it that way." The third can create gentle urgency without threats.
What Recova does
Recova generates each dunning email automatically using the merchant's brand voice, the specific decline code, and the customer's account history as part of a full payment recovery sequence that runs from the first webhook event through day 30. Retry and email timing are coordinated: a successful retry cancels pending emails. Every email includes a link to the merchant's Stripe-hosted payment update page.
The sequence runs from the first webhook event through day 30 without manual intervention.
- When should I send the first dunning email after a payment failure?
- Depends on the decline code. For soft declines, send after silent retries fail, typically day 4. For hard declines and card data errors, send on day 1.
- What should a dunning email say?
- Keep it short, human, and action-focused. Use the customer's name. Acknowledge the issue without alarm. Include a single direct link to update their payment method. Avoid technical jargon and billing system language.
- How many emails should a dunning sequence have?
- Three is the minimum that captures most recoverable customers. First email when retries fail, second at day 7, third at day 14. Some businesses run a fourth at day 21 for higher-value subscriptions.
- Should retries and emails be coordinated?
- Yes. A successful retry should cancel pending emails. Emails should fire in proximity to retry attempts so customers act while the subject is top of mind.
- What recovery rate should a good dunning email sequence achieve?
- Email-only dunning achieves around 42 percent recovery. Combined with intelligent retries, 60 to 80 percent is achievable based on Churnkey and Recurly benchmark data.
