Source: https://www.revvly.ai/blog/voluntary-vs-involuntary-churn Churn 9 min read Sep 7, 2026 # Voluntary vs involuntary churn: why the two need different fixes A CS leader looks at last month's churn number and sees one figure, but that single number is hiding two completely different problems. SA Samuel Adeyemo Revenue Systems, Revvly A CS leader looks at last month's churn number and sees one figure: X accounts canceled. That single number hides two completely different problems. Some of those accounts were canceled on purpose, by a person who decided the product was not worth the money anymore. Others never decided to leave at all; their card expired, a charge got declined, and the subscription lapsed without anyone making a choice. Treating both as "churn" and fixing them with the same playbook is why so many retention programs underperform. ## Quick answer > Voluntary churn is when a customer actively decides to cancel their subscription, driven by price, lack of value, or a competitor. Involuntary churn is when a subscription lapses due to a failed payment (an expired card, insufficient funds, a declined charge) even though the customer never intended to leave. Recurly's benchmark research shows involuntary churn makes up roughly 20 to 40 percent of total subscription churn across industries, with SaaS specifically running closer to one-third [1]. The two require different fixes: retention workflows and pricing changes for voluntary churn, and dunning plus payment-retry logic for involuntary churn. ## What separates voluntary and involuntary churn, and why the distinction matters Voluntary churn is a decision. The customer logged in, looked at what they were paying, weighed it against the value they were getting, and chose to cancel. The reasons vary (price, a missing feature, a better-fit competitor, declining usage) but the common thread is intent. Somebody decided to leave. Involuntary churn has no decision behind it. A card on file expires. A bank declines a charge for insufficient funds. A payment processor has a transient failure. The subscription lapses on a technicality, and unless the company catches it and recovers the payment, that customer is gone without ever choosing to be. Recurly's churn research breaks SaaS churn down to roughly 2.16 percentage points voluntary against 1.06 percentage points involuntary out of a combined monthly churn rate near 3.22 percent, meaning involuntary churn accounts for close to a third of all SaaS cancellations even though none of those customers actually chose to go [1]. That gap is why lumping the two together produces bad decisions. If a CS team sees overall churn rise and responds by launching a new onboarding sequence or a loyalty discount, but a third of that increase is actually failed credit cards, the intervention targets the wrong third of the problem. Revvly's own deep dive on involuntary churn frames it as an undercounted "silent revenue leak" for exactly this reason: it is often invisible in a churn dashboard that does not separate cancellation reasons from payment-failure reasons, so it gets explained away as "normal churn" instead of treated as a fixable billing problem. That post covers the mechanics of detecting and recovering involuntary churn in depth; for a full treatment of dunning sequencing and retry logic, see [the involuntary churn deep dive](https://www.revvly.ai/blog/involuntary-churn-subscription-billing). This post focuses the rest of its space on voluntary churn, since that is where most of the deliberate retention work actually needs to happen. ### What drives voluntary churn Voluntary cancellations cluster around a small number of recurring causes: perceived price-to-value mismatch, a competitor offering a better fit, declining product usage that precedes the cancellation by weeks or months, unmet expectations from the sales or onboarding process, and organizational changes at the customer (budget cuts, team restructuring, a tool consolidation decision made above the user's head). None of these are billing problems. All of them require a human or product-level response: pricing adjustments, a retention conversation, a win-back offer, or a product fix. ### What drives involuntary churn Involuntary churn is mechanical. Cards expire on a schedule (most issuers reissue every two to four years) and nobody updates billing details proactively. Declines happen for insufficient funds, especially around monthly billing dates that cluster near payday cycles. Processor-level failures, network timeouts, and anti-fraud flags from the card issuer add a smaller but real share. None of these reflect the customer's opinion of the product. The fix is retry logic, not a retention offer. ### Why voluntary churn needs retention workflows, not payment fixes Because voluntary churn is a decision, the fix has to engage with the decision. That means usage monitoring that flags accounts trending toward disengagement before the cancel click, pricing and packaging that match what a given segment actually values, and proactive outreach from CS or automated retention workflows when risk signals appear. A [churn prediction model](https://www.revvly.ai/blog/churn-prediction-software) built on usage and engagement data is the right tool here, because the inputs that predict voluntary churn (login frequency, feature adoption, support ticket sentiment) are fundamentally different from the inputs that predict involuntary churn (card expiration dates, processor decline codes). ### Why involuntary churn needs dunning, not retention offers Sending a win-back discount to someone whose card just expired misreads the situation entirely; they do not need to be convinced to stay, they need a working payment method. The correct response is a structured dunning sequence: automated retry attempts timed around when a retry is statistically more likely to succeed, proactive card-expiration reminders before the failure happens, and a simple, low-friction update-payment-method flow. This is a billing and automation problem, and it is largely solvable without ever involving a human on the CS team. ### Where the two categories blur A small set of cases sit in between. A customer who has been quietly disengaged for months and whose card then happens to expire may represent both problems at once, their payment failed, but they also were not getting enough value to notice or care. In these cases, dunning recovers the immediate lapse, but the account is still at voluntary-churn risk going forward. Account-level churn and expansion reporting that tracks usage trends alongside payment health is the only way to catch this overlap rather than treating a successful dunning recovery as "problem solved." ## Breakdown: voluntary churn vs involuntary churn at a glance | | Voluntary churn | Involuntary churn | | --- | --- | --- | | Cause | Customer decision | Failed payment | | Typical share of total SaaS churn | ~two-thirds [1] | ~one-third [1] | | Primary signal | Usage decline, support sentiment, pricing fit | Card expiration, decline codes, processor errors | | Right fix | Retention workflows, pricing review, CS outreach | Dunning sequences, payment retry, card-update reminders | | Who owns it | CS, Product, Growth | RevOps, Finance, Billing | | Recoverable without customer action? | No, requires a decision reversal | Often yes, through retry and proactive reminders | ## A short checklist for separating the two in your own reporting - Does your churn dashboard split cancellations by reason (decision) versus payment status (failure), or is it one blended number? - Are retention workflows (outreach, offers, pricing conversations) only triggered for accounts flagged as voluntary risk? - Is dunning and card-update messaging automated and separate from any human-led retention motion? - Do you track what share of "recovered" involuntary churn later re-churns voluntarily within 90 days? - Does your CS team see usage and payment health in the same account view, or in two disconnected systems? ## Where this fits in the bigger picture Churn is not one number to manage down; it is at least two separate operational problems that happen to show up in the same metric. A CS leader who treats both with the same playbook will over-invest in retention conversations for customers who were never going to be reached by a conversation (their card just failed), and under-invest in the harder, slower work of understanding why engaged, paying customers decide to leave on purpose. Splitting the reporting is the first step; building distinct workflows for each is what actually moves the number. ## Frequently asked questions **What is the difference between voluntary and involuntary churn?** Voluntary churn is a customer's deliberate decision to cancel, driven by price, value, or a competitor. Involuntary churn happens when a subscription lapses due to a failed payment, such as an expired card or a declined charge, even though the customer never intended to leave. **Which type of churn is more common in SaaS?** Voluntary churn is more common. Recurly's benchmark data shows SaaS churn splitting roughly 2.16 percentage points voluntary against 1.06 percentage points involuntary, meaning deliberate cancellations account for roughly two-thirds of total churn [1]. **Can involuntary churn be prevented entirely?** Not entirely, but most of it is recoverable. Proactive card-expiration reminders, automated payment retries timed for higher success rates, and a frictionless update-payment-method flow recover a large share of failed payments before the subscription actually lapses. **Does a win-back discount help with involuntary churn?** Generally no. A customer whose card expired or was declined did not decide to leave, so a discount does not address the actual problem; they need a working payment method, not an incentive to stay. **How should a CS team split its churn reporting?** Churn should be split by cause, not reported as one number: cancellations driven by a customer decision should route to retention and CS workflows, while lapses driven by payment failure should route to billing and dunning workflows, each with its own metrics and owner. **What causes most voluntary churn in subscription businesses?** The most common drivers are a perceived mismatch between price and value, a competitor offering a better fit, declining product usage in the weeks before cancellation, and organizational changes at the customer's company that are unrelated to the product itself. **Where can I read more about fixing involuntary churn specifically?** A full treatment of involuntary churn detection and dunning sequencing, including why it is often undercounted as a silent revenue leak, is covered in [Revvly's involuntary churn deep dive](https://www.revvly.ai/blog/involuntary-churn-subscription-billing). ## Sources 1. Recurly, "Churn rate benchmarks: SaaS, media, retail & more industries," Recurly Research, 2026. [https://recurly.com/research/churn-rate-benchmarks/](https://recurly.com/research/churn-rate-benchmarks/) ## Frequently asked questions ### What is the difference between voluntary and involuntary churn? Voluntary churn is a customer's deliberate decision to cancel, driven by price, value, or a competitor. Involuntary churn happens when a subscription lapses due to a failed payment, such as an expired card or a declined charge, even though the customer never intended to leave. ### Which type of churn is more common in SaaS? Voluntary churn is more common. Recurly's benchmark data shows SaaS churn splitting roughly 2.16 percentage points voluntary against 1.06 percentage points involuntary, meaning deliberate cancellations account for roughly two-thirds of total churn. ### Can involuntary churn be prevented entirely? Not entirely, but most of it is recoverable through proactive card-expiration reminders, automated payment retries timed for higher success rates, and a frictionless update-payment-method flow. ### Does a win-back discount help with involuntary churn? Generally no, because a customer whose card expired or was declined did not decide to leave. They need a working payment method, not an incentive to stay. ### How should a CS team split its churn reporting? Churn should be split by cause rather than reported as one number, with decision-driven cancellations routed to retention and CS workflows and payment-failure lapses routed to billing and dunning workflows. ### What causes most voluntary churn in subscription businesses? The most common drivers are a perceived mismatch between price and value, a competitor offering a better fit, declining product usage before cancellation, and organizational changes at the customer's company unrelated to the product. ### Where can I read more about fixing involuntary churn specifically? A full treatment of involuntary churn detection and dunning sequencing, including why it is often undercounted as a silent revenue leak, is covered in Revvly's involuntary churn deep dive. SA Samuel Adeyemo Revenue Systems, Revvly Samuel builds the systems that turn billing events into trustworthy revenue numbers. He writes about retention, pricing, and the operational details that decide whether the metrics hold up. Revvly Orchestrate the flow of revenue. © 2026 AcceleratorApp Limited. All rights reserved.