Involuntary churn: the cheapest revenue you are not collecting
Patients who wanted to stay and whose card failed. No persuasion required, no discount needed, and most of it is recoverable with infrastructure rather than marketing.
Key takeaways
- Involuntary churn is revenue lost to failed payments, not to patients deciding to leave.
- It is the cheapest churn to fix, because there is no persuasion involved and no discount required.
- Card account updater coverage converts would-be failures into successes with no patient action.
- Retry timing should respond to the decline reason, not run on a fixed interval.
- A properly built rebill engine recovers 0.5 to 1% of billings every cycle.
The distinction that matters
Voluntary churn is a patient deciding to stop. Fixing it means changing the product, the price or the experience, which is slow and expensive.
Involuntary churn is a patient who intended to continue and whose payment failed. Fixing it means changing infrastructure, which is fast and cheap. You already paid to acquire them, already served them, and lost them to a technical event.
Operators consistently spend more attention on the first and get more return from the second.
What actually causes it
Four causes account for most of it, and each has a different remedy, which is why a single blanket retry policy underperforms.
- Card expiry. Predictable, and almost entirely solved by account updater coverage.
- Reissued cards after fraud or loss. Same remedy, different trigger.
- Insufficient funds at the moment of billing. Retry timing matters enormously here; the same card often succeeds days later.
- Issuer declines on unfamiliar descriptors. Remedied by a recognisable statement descriptor, which requires owning the merchant account.
Why telehealth is unusually exposed
Subscription telehealth compounds the problem in three ways. Retention horizons are long, so more cards expire inside the relationship. Categories are frequently coded high risk, so issuer declines are more common. And in several categories the patient is deliberately not receiving marketing email, so the usual dunning channel is weaker.
That combination means the infrastructure has to do more of the work than in a typical consumer subscription.
The recovery stack, in order of return
These are ranked roughly by return per unit of effort, which is not the order most teams implement them in.
- Card account updater coverage. Highest return, requires no patient action at all.
- Decline-reason-aware retry timing. Retrying an insufficient-funds decline on a different schedule to a hard decline materially changes recovery.
- Self-serve card updates in the portal. A patient who fixes their own card is a recovery you never had to chase.
- A recognisable statement descriptor. Reduces both declines and disputes, and costs nothing once you own the account.
- Multi-MID routing. So one processor's risk posture does not become your decline rate.
- Proactive pre-expiry prompts in the portal for cards approaching expiry.
What it is worth
A well-run rebill engine recovers between 0.5 and 1% of billings every cycle. At $89,700 in monthly billings that is roughly $673 a month, about $8,000 a year.
At $300,000 in monthly billings the same range is $1,500 to $3,000 a month. None of that requires acquiring a single additional patient, changing the price, or running a campaign.
Why a generic subscription object underperforms
Standard subscription billing charges on a calendar and retries on a fixed schedule. It does not know that a shipment did not go out, that the dose changed, or why a particular decline occurred.
In telehealth those distinctions are the whole game. Charging for a shipment that did not ship produces a dispute rather than a recovery, and retrying a hard decline three times produces nothing except processor noise.
A rebill engine, not a subscription object
PharmaBro tokenises cards and bills on the ship date at the dose dispensed, with decline-reason-aware retry logic, card account updater coverage and routing across up to five merchant IDs.
Rebill forecasting shows expected collections, the failure cohort and the recovery curve before the cycle runs, so it is a planning input rather than a post-mortem.
Conclusion
Involuntary churn is the only churn you can fix without persuading anybody of anything.
Get account updater coverage, make retries respond to the decline reason, let patients fix their own cards in the portal, and make sure the descriptor on the statement is one they recognise. It is unglamorous, it takes a few weeks, and it recovers money every single cycle thereafter.
Frequently asked questions
What percentage of churn is involuntary?
It varies by category and by how well the recovery stack is built, but it is consistently a significant share of total churn in subscription businesses with long retention horizons. Telehealth is unusually exposed because relationships run for many months and the categories are frequently coded high risk.
What is a card account updater?
A card network service that supplies refreshed details when a card is reissued or expires, so a would-be failed payment succeeds without the patient doing anything. It is the highest-return item in the recovery stack for exactly that reason.
How much can a rebill engine recover?
Between 0.5 and 1% of billings per cycle in practice. At $89,700 in monthly billings that is roughly $673 a month, or about $8,000 a year that calendar-based billing would have written off.
References
Marcus ElleryHead of Payments and Billing
Works on the rebill engine, merchant routing and recovery logic. Spends most of his time on the unglamorous half of subscription telehealth: why a card failed, and whether it had to.