Configure dunning and failed payments before they cost you customers you already won

Configure dunning and failed payments before they cost you customers you already won

Here is a number that should change how you prioritise: a meaningful slice of churn is involuntary. The customer wanted to keep paying, but their card expired, hit a limit, or got declined, and nobody recovered the payment. That is revenue you already earned, walking out the door over a configuration you skipped. Dunning is the system that recovers it, and it deserves real attention.

Configure a retry schedule that is intelligent, not aggressive. Smart retries that space attempts over days and time them to when payments are more likely to succeed recover far more than hammering the card four times in an hour. Most commerce platforms offer a smart-retry option, turn it on, and tune the window rather than accepting the default.

Pair retries with a communication sequence the customer actually sees. A failed payment should trigger a clear, human email that tells them what happened and gives them a one-click way to update their card. The recovery rate on dunning is driven as much by the quality of that email and the ease of the update flow as by the retry logic itself.

Decide what happens at the end of the retry window, and configure it deliberately. Does the subscription cancel, pause, or downgrade to a free tier? Each choice is a different customer experience and a different chance to win them back. A hard cancel after one failed cycle throws away customers who would have paid; a grace period with a clear deadline often recovers them.

Set up card-expiry handling proactively too. The best dunning is the dunning that never fires, so use the network's automatic card updater where available and prompt customers before a known expiry, rather than waiting for the decline.

INTERVIEW EWOUD: Share a real recovery rate. When a client switched on smart dunning and a proper recovery sequence, how much involuntary churn came back?