Dunning Copy Best Practices

When silent retries are exhausted and you need to contact the customer, your messaging determines whether they update their payment method or cancel. This guide covers everything from subject lines to full templates across the dunning escalation timeline.

Subject Line Formulas That Convert

Subject lines drive open rates, and open rates drive recovery. The best dunning subject lines balance clarity with the right emotional register for the escalation stage.

Formula Comparison

Subject Lines to Avoid

• "URGENT: Payment failed!!!" -- all caps and exclamation marks trigger spam filters and create anxiety
• "Invoice #INV-38291 past due" -- too impersonal, reads like a collections notice
• "Your account has been suspended" -- dishonest if the account is still active, and creates panic
• "Final warning" on a first email -- erodes trust and leaves no room to escalate

Email Tone Guide

Tone should escalate gradually across the dunning sequence. Start warm and helpful; only become firm and urgent near the end.

Tone Spectrum

The best-performing dunning sequences follow an Empathetic > Professional > Urgent arc. Starting urgent and staying urgent fatigues the customer and increases unsubscribe rates.

What to Include in Every Dunning Email

Every dunning email should make it as easy as possible for the customer to fix the problem. Include these elements:

1. The amount due -- customers want to know what they are paying before clicking anything
2. Last 4 digits of the card -- helps them identify which card failed and whether they have already updated it
3. A direct update link -- one click to the payment method update page, no login required if possible
4. A clear deadline -- when their access will be affected if they do not act
5. Your support contact -- a real email or chat link in case the failure is not their fault

What NOT to Include

Avoid these patterns. They reduce recovery rates and damage your brand.

• Threatening language -- "Your account will be permanently deleted" creates panic and drives cancellations rather than updates
• Account deletion threats -- unless you genuinely delete data (and even then, use softer framing like "your data will be archived")
• Legal or collections language -- "failure to remit payment" or "amount outstanding" reads like a debt collection letter
• Multiple CTAs -- do not combine a payment update request with upsell offers, surveys, or feature announcements
• Blame -- "You failed to pay" vs. "Your payment did not go through" -- the latter is factual without assigning fault
• Excessive detail about the decline reason -- customers do not need to know it was do_not_honor; they need to know what to do

Template Examples by Escalation Stage

Day 1: Empathetic Notification

Subject: We had trouble processing your payment

Body:

Hi {first_name},

We tried to charge the {card_brand} ending in {last_4} for your {product_name} subscription ({amount}), but the payment did not go through.

This happens sometimes -- it is usually a temporary issue with the card or bank. In many cases, it resolves on its own and we will retry automatically.

If you would like to update your payment method now, you can do so here:

[Update Payment Method]({update_url})

If you have any questions, just reply to this email.

-- The {company_name} Team

Why it works: No alarm. Normalizes the failure. Provides an action path without demanding action. Mentions that automatic retries are happening.

Day 3: Professional Follow-Up

Subject: Action needed: update your payment for {product_name}

Body:

Hi {first_name},

Your {product_name} subscription payment of {amount} on {card_brand} ending in {last_4} was not successful, and our automatic retries have not resolved the issue.

To keep your subscription active, please update your payment method:

[Update Payment Method]({update_url})

Your access to {product_name} will not be affected while we work this out, but we do need updated payment information within the next few days.

Need help? Reply to this email or reach us at {support_email}.

-- The {company_name} Team

Why it works: Slightly more direct. Acknowledges that retries have been attempted. Provides a soft deadline without a specific date. Reassures that access is intact.

Day 7: Urgent with Deadline

Subject: Your {product_name} subscription expires on {deadline_date}

Body:

Hi {first_name},

We have been unable to process your {product_name} payment of {amount} since {failure_date}. Your subscription will be paused on {deadline_date} unless we receive updated payment information.

When paused, you will lose access to:
- {feature_1}
- {feature_2}
- {feature_3}

Updating takes less than a minute:

[Update Payment Method]({update_url})

If you have already updated your card, you can disregard this email -- we will process the payment automatically.

Questions? Contact us at {support_email}.

-- The {company_name} Team

Why it works: Specific deadline creates urgency. Lists features they will lose (personalized based on usage data). Acknowledges they may have already acted. Uses "paused" rather than "cancelled" -- it is less final and more accurate.

Day 14: Final Notice

Subject: Last chance to keep your {product_name} subscription

Body:

Hi {first_name},

This is our final notice regarding your {product_name} subscription. Your payment of {amount} has been unsuccessful since {failure_date}, and your subscription will be cancelled on {final_deadline_date}.

After cancellation:
- Your account data will be preserved for 90 days
- You can reactivate at any time by updating your payment method
- Any team members on your plan will also lose access

[Update Payment Method Now]({update_url})

We would hate to see you go. If there is anything we can help with -- whether it is a billing issue, a plan change, or anything else -- please reach out to {support_email}.

-- The {company_name} Team

Why it works: Clear finality without being hostile. Specifies exactly what happens after cancellation. Mentions data preservation (reduces anxiety). Offers alternatives (plan change). Expresses genuine sentiment without being sycophantic.

SMS Copy Guidelines

SMS dunning messages follow different rules than email. You have roughly 160 characters to communicate the problem and drive action.

Principles

• Lead with the brand name -- recipients need to know who is texting them
• State the problem in one sentence -- "Your payment for [Product] did not go through"
• Include a short link -- the only CTA should be the payment update link
• No more than 2 messages per recovery cycle -- SMS is interruptive; overuse leads to opt-outs

SMS Templates

Day 3 (first SMS):

{company_name}: Your {product_name} payment of {amount} did not go through. Update your card here: {short_url}

Day 10 (final SMS):

{company_name}: Your {product_name} access expires {deadline_date}. Update payment now: {short_url}

A/B Testing Recommendations

Dunning copy is one of the highest-leverage areas to test. Small changes in subject lines and CTAs can shift recovery rates by 5-15%.

What to Test

Testing Best Practices

• Test one variable at a time -- if you change the subject line and the CTA simultaneously, you will not know which one drove the result
• Minimum sample size -- wait for at least 200 sends per variant before drawing conclusions (LostChurn shows statistical significance in the campaign analytics)
• Test across the full funnel -- a higher open rate is meaningless if it does not translate to more payment updates
• Retest quarterly -- customer behavior shifts with market conditions, and last quarter's winning subject line may not win this quarter
• Do not test on Day 14 emails -- final notice emails should be clear and direct; creative testing at this stage risks confusing the customer at a critical moment

Setting Up A/B Tests in LostChurn

LostChurn's Campaigns builder supports A/B testing natively. When creating a campaign step, click Add Variant to create an alternate version. LostChurn will split traffic evenly and report conversion rates for each variant with confidence intervals.

Next Steps

• Retry Timing Best Practices -- optimize when retries happen before customers are contacted
• Retry Strategies -- configure the retry engine that runs before dunning
• Campaigns -- build and deploy your dunning sequences
• Recovery Overview -- return to the three pillars of recovery optimization