Dunning messages do a lot of unglamorous work. They are the bridge between a payment system error and a save: the customer wanted to keep paying, something broke, and the message has to surface the problem clearly enough that they fix it before the subscription cancels. Most subscription stores under-invest here, which means they leave 5–15% of revenue on the table every month.
What a good dunning sequence looks like
- First retry notification (day 0). "Your payment didn't go through." Friendly tone, one clear action - update card. Mention the next retry date so the customer is not surprised.
- Reminder (day 3 or 4). "We tried again and it still didn't work." Add a touch more urgency and explain what happens if it keeps failing.
- Final notice (day 7 or 10). "Last try - we'll pause your subscription tomorrow." Make the consequence explicit. This message converts the most.
- Pause / cancel notification. "We've paused your subscription. Resume any time." Keep the door open; many of these still come back within 30 days.
Tone and copy choices that recover more revenue
- Lead with the problem, not the apology. "Your payment didn't go through" converts better than "Sorry, there was a problem."
- Tell them why. If the platform knows the decline reason (expired card, insufficient funds), say so. Generic "error" messages get ignored.
- One call to action. Update your card. Not three buttons, not a long FAQ link - one button.
- Mobile-friendly. Most card updates happen on phones. The update form has to work in a thumb-driven flow.
What to avoid
Apologetic, anxious-sounding messages. Walls of text. Generic templates with no personalization. And the cardinal sin: not sending messages at all because the merchant assumes the platform handles it. Default platform dunning is usually thin; the merchants who customize their messages typically recover 30–50% more than those who do not. See dunning management and payment reminder email.