How Many Months of Zero Usage Should Trigger Action: A practical framework for balancing telecom savings with reactivation risk

For mobility managers, zero usage appears to offer an easy savings opportunity. A line shows no activity, so the natural response is to disconnect it. The difficult question is timing. Acting after one month captures more savings but creates a higher risk that the user still needs the service. Waiting too long reduces that risk, but much of the available savings disappears while the organization continues paying for inactive lines.

A recent sample analysis of 12 months of T-Mobile billing and usage data found that four consecutive months of zero usage provided the best practical balance. It retained about half of the savings identified after one month while reducing the observed three-month reactivation rate from 56.3 percent to 13.4 percent. The result supports a tiered review process rather than a single automatic cancellation rule.

The Tradeoff Between Savings and Risk

The number of zero-usage months used as the threshold materially changes the savings opportunity. A one-month rule identified 542 billed lines and $9,616 in potential monthly savings. A four-month rule identified 285 lines and $4,884 per month. By six months, the opportunity declined to 213 lines and $3,488 per month. Waiting 12 months reduced the available monthly savings to $1,808, only 18.8 percent of the one-month opportunity.

The decline is expected. Each additional month removes lines that resumed usage, left the account, or otherwise no longer met the eligibility criteria. A conservative threshold lowers the chance of disrupting a valid user, but it also allows avoidable charges to continue.

Why One Month Is Too Early for Automatic Disconnection

A single month without activity is a useful signal, but it is a weak basis for an automatic disconnect. In the sample, 56.3 percent of observable one-month-zero episodes resumed usage within the following three months. At two months, the return rate remained 34.7 percent. These lines may represent employees on leave, spare or emergency devices, seasonal workers, devices awaiting deployment, or services that are used intermittently.

This does not make a one-month report useless. It makes it a watchlist. The report can start an investigation, identify ownership problems, and prompt managers to confirm whether the line is still needed. It should not be treated as final proof that the service is unnecessary.

Why Four Months Provides a Practical Middle Ground

At four consecutive months of zero usage, the sample still retained 50.8 percent of the savings available under a one-month rule. At the same time, the observed three-month reactivation rate fell to 13.4 percent. This level is low enough to support action after validation, while the remaining monthly savings is still meaningful.

Four months should not become a universal rule applied without context. It is a starting point for an operating policy. Before disconnecting a line, the organization should confirm the employee or device owner, service purpose, contract status, device payment obligations, and any approved business exception.

Results by Zero Usage Threshold

Zero months	Lines	Monthly savings	Reactivation rate	Recommended use
1	542	$9,616	56.3%	Watchlist
3	326	$5,682	19.3%	Owner validation
4	285	$4,884	13.4%	Action after validation
6	213	$3,488	8.7%	Lower-risk action
8	166	$2,543	3.1%	Automation with exceptions

The Initial Backlog Is Different From Ongoing Savings

The first month of a zero-usage program often produces an unusually large savings opportunity because it captures an accumulated backlog. That amount should not be used as the expected result for every future month.

After excluding the opening backlog month, the one-month policy in this sample generated an average of approximately $2,160 in new monthly run-rate savings per cycle. The comparable averages were about $614 for a four-month policy and $411 for a six-month policy. The new opportunity becomes smaller, but savings already implemented continue reducing the bill.

This distinction matters when presenting results. A program should separately report newly identified monthly savings, previously implemented recurring savings, and total cumulative savings. Combining these figures can make performance appear larger or less stable than it is.

A Tiered Zero Usage Policy

The analysis supports a staged process that increases the level of action as inactivity continues.

• After one month Place the line on a watchlist and confirm the assigned user, service purpose, and employment or device status.

• After three months Require owner or manager validation and review contracts, device installments, and business exceptions.

• After four months Take disconnect or suspension action when validation does not identify a legitimate need.

• After eight months Consider unattended action only when approved exception rules are built into the process. The observed return rate was 3.1 percent, although the 95 percent confidence interval extended to 5.4 percent.

Exceptions Must Be Part of the Policy

Usage data cannot explain why a line is inactive. Critical, seasonal, emergency, shared, executive, spare, IoT, and newly activated services may be valid even when they show no recent activity. A zero-usage process should maintain an exception list with an owner, justification, and expiration or review date.

The source files used for this analysis did not contain employee status, inventory status, contract dates, device purpose, exception approvals, or actual disconnect outcomes. Those fields should be added to the operational workflow before decisions are automated.

Data Quality Determines Whether the Result Is Trustworthy

A zero-usage analysis depends on accurate matching between billing and usage records. In this sample, billing-to-usage service-ID coverage was 100 percent in every month. Duplicate service-month usage records were aggregated before analysis, and any activity reported in detailed usage fields was treated as usage even when core total fields were zero.

Savings estimates included positive recurring monthly charges only. Taxes, equipment charges, one-time charges, and usage charges were excluded. These rules prevent the model from overstating savings that would not actually disappear after a service change.

The Practical Recommendation

For this sample, four consecutive months of zero usage is the strongest default threshold for validated action. It captures meaningful savings while reducing the chance that the line will quickly return to use. One month should trigger investigation, three months should trigger owner confirmation, and eight months can support more automated action when exception controls are reliable.

Organizations should test these thresholds against their own service mix and operating needs. More than 12 months of history would improve confidence, reveal seasonal patterns, and allow the reactivation risk of longer thresholds to be measured. The goal is not to select the most aggressive or most conservative rule. It is to use evidence to determine when savings become actionable.

About the Analysis

This analysis used a 12-month sample of T-Mobile billing and usage data from October 2025 through September 2026. Results describe the sample and should not be treated as a universal benchmark. Each organization should validate its own usage patterns, line purposes, contractual obligations, and risk tolerance before implementing a zero-usage policy.