The Markin ROI Report for Enterprise Growth TeamsRead now
MARKIN
Field notes
Guides9 min read

Voluntary vs involuntary churn: two problems, two fixes

Payment-failure churn is a dunning problem. Intent churn is a decisioning problem. How to split them, who owns each, and how to measure both correctly.

Romà Llambés
  • #Churn
  • #Payments
  • #Retention
Voluntary vs involuntary churn: two problems, two fixes

Frequently asked

Questions readers ask about this.

What is the difference between voluntary and involuntary churn?
Voluntary churn is a customer actively choosing to leave: cancelling, downgrading or lapsing. Involuntary churn is a customer leaving because a payment failed, usually through an expired card, insufficient funds or a bank decline, often without knowing it happened.
What percentage of churn is involuntary?
In card-on-file B2C subscription bases, involuntary churn usually accounts for 20 to 40 percent of gross churn. It runs higher in markets with heavy debit or prepaid usage, in long-tenure bases where card reissues are frequent, and after a price increase.
How do you reduce involuntary churn?
With payments levers rather than marketing ones: smart retry timing based on decline code and issuer behaviour, network tokenization and account updater services to survive card reissues, pre-dunning notices before the charge fails, and separate handling of soft and hard declines.
How do you reduce voluntary churn?
By ranking interventions on uplift rather than churn probability, so margin goes to customers whose behaviour actually changes, and by preserving an untreated holdout of equally scored customers so the reported save rate is incremental.
Can involuntary churn actually be voluntary?
Yes. Some customers let a payment fail instead of cancelling. Separate them behaviourally: a customer active in the week before the decline is genuinely involuntary and needs a frictionless card-update path, while one whose engagement decayed for weeks beforehand needs a value intervention first.

See it in the product

This runs in Markin today.

The same loops this note describes run 24/7 against your customer base. Watch the workspace decide, experiment and execute 1:1.