Failed payment emails: the dunning sequence that doesn't feel like nagging

A failed payment isn't necessarily a customer trying to avoid paying, it's often an expired card, a bank's fraud flag on an unfamiliar recurring charge, or an issuer-side decline unrelated to the customer's intent. The dunning sequence (the automated reminders after a failed charge) should reflect that assumption rather than treating every failure as a collections problem.

A reasonable cadence

• Immediately: a factual, low-pressure notice that the charge failed and what to do about it (update payment method)
• A few days later: a second reminder if unresolved, still factual, not escalating in tone
• Around the point service is at risk: a clearer statement of what happens next (service pauses, downgrade, etc.) so there's no surprise
• A final notice at the actual cutoff point, stating plainly what's about to happen

What makes it feel like nagging

Escalating urgency language across the sequence ("URGENT: action required" by email two) reads as aggressive rather than helpful, especially for what's very often an honest card-expiry issue, not a customer avoiding payment. Keep the tone consistent and factual across the whole sequence: what failed, what to do, what happens if it isn't resolved by when.

The actual tradeoff

More emails, more aggressively worded, do recover marginally more failed payments in the short term. They also measurably increase unsubscribes and support complaints, and they're the kind of email most likely to get a domain flagged if the sequence is long and pushy enough to trigger spam reports. A shorter, calmer sequence usually recovers most of the recoverable revenue (a legitimate card-expiry issue gets fixed regardless of how strongly worded the third email is) without the reputation cost of an aggressive one.