Dunning and Involuntary Churn Recovery (Retention)

Dunning and Involuntary Churn Recovery (Retention)

1. 01

   Pull the failed-payment ledger for the trailing 90 days and segment by failure code

   Separate soft declines (expired card, insufficient funds) from hard declines (closed account, stolen card) and from processor errors. Recovery rates diverge sharply by code, so a single blended number hides where the money actually sits.

2. 02

   Map each failure code to a retry schedule instead of running one global cadence

   Soft declines warrant retries on days 1, 3, 5, and 7; hard declines should stop retrying after the second attempt and route straight to a card-update request. Billing platforms such as Chargebee and Recurly expose retry logic per gateway, so the schedule can live in configuration rather than in a spreadsheet.

3. 03

   Write the pre-dunning email before the first retry, not after it

   A card-expiry notice sent 7 days ahead of the renewal date converts far better than a failure notice sent after the charge bounces. For membership builds on WordPress, MemberPress and Paid Memberships Pro both allow a scheduled reminder tied to the expiration date.

4. 04

   Route every dunning message through a single sender identity the client has approved

   Payment mail that arrives from an unrecognized domain gets marked as spam, which kills the recovery sequence. Confirm the sending domain, reply-to address, and footer entity match the client's billing descriptor.

5. 05

   Give the end customer a self-serve card update path that does not require a login reset

   A white-label billing portal shortens recovery time because the customer never has to contact support. Cloudmore and CloudBlue both ship customer portals for this purpose in reseller and CSP environments.

6. 06

   Escalate accounts past 21 days overdue to a human owner with a written save offer

   Define the offer in advance: a one-month pause, a downgrade tier, or a partial credit. Improvised retention calls produce inconsistent discounts that erode the client's margin.

7. 07

   Log every recovered and every lost account against the original failure reason

   This ledger is what lets an agency show a client that recovery work moved a specific dollar figure, which is the evidence that justifies keeping the retainer.

8. 08

   Review the recovery rate monthly and retire any message in the sequence that underperforms the control

   Sequences decay as payment behavior shifts. A quarterly prune keeps the cadence from accumulating dead steps that add noise without recovering revenue.