When Financial Stress Shows Up Before the Metrics Do

Show notes

Churn and bad debt are the metrics every operator watches. They are also lagging indicators. By the time they move, the financial stress behind them has usually been building for weeks.

On this episode of Bandwidth, Rick Seemann, Georgette Lopez-Aguado, and Larry Weidig dig into how economic pressure changes subscriber behavior, why the obvious metrics show up late, and what ISPs can do to protect customer relationships before a missed payment turns into a cancellation.

The First Signal Isn't a Missed Payment

Georgette put it simply: financial stress creates friction long before it creates churn. The early signals are changes in behavior. More payment arrangement requests. Customers asking to move their billing date to line up with payday. Downgrades instead of upgrades. Support calls about pricing or the minimum service available. More visits to cheaper packages and cancellation policies on the website.

Larry added a few more: customers logging into the portal more often to check charges, and customers swapping credit cards repeatedly because the last one didn't go through. As Georgette noted, customers usually tell you they're struggling. They just don't always use their words.

Rick flagged the one he would set a trigger for immediately: an autopay opt-out, especially from an account with a long history of stable autopay. And because ISPs sit on thousands of data points across billing, support, and web behavior, this is a strong use case for AI that can spot shifting patterns and tap someone on the shoulder before the account is gone.

One data point from Georgette stood out. The month customers most often turn off autopay across the Sonar ecosystem is December, likely to free up money for the holidays. The second is May, with graduations, weddings, and summer travel on the horizon.

Stress Makes Customers Less Predictable

Do customers become more price sensitive or more service sensitive when times get tough? The panel's answer was both, and the bigger problem is that everything becomes less predictable.

In stable times, customers optimize for convenience and speed. Under pressure, they optimize for monthly cash flow. Someone who would never wait on hold will spend 45 minutes with a CSR trying to lower their bill. Some will happily accept slower speeds to save $20 a month. Others become less tolerant of outages, because every hour of downtime feels more expensive.

Rick added a caution about timing. When operators face rising costs of their own, a price increase can push a customer who had budgeted $60 for internet past what they can carry at $75. Some of that stress is within the operator's control, and reading the room matters.

Rigid Processes Speedrun Cancellations

When customers stop behaving the way systems expect, the operational cracks show. More partial payments, billing date changes, short disconnects and reconnects, waived fee requests, and high-friction support calls all create overhead.

Rick's point was that systems built for pure black and white billing rules end up speedrunning cancellations without anyone noticing. A well-designed payment plan that tier one staff are trained and empowered to use can be a real retention tool. Without one, different agents offer different options and the experience becomes inconsistent.

Georgette framed it this way: billing systems and collection policies may work perfectly, but they were designed for predictable behavior, not uncertainty. The process doesn't break. The assumptions behind it do. That is where automation needs to get smarter, not just stricter. She also suggested watching local context, like a layoff at a major employer in your footprint, since those households may start making hard decisions weeks later.

Larry reminded listeners that the effects reach beyond support. Cash flow expectations shift, and that flows into builds, inventory, and the rest of the business.

Love It or Hate It: A Rare Unanimous Round

Should subscribers lose service faster when payment consistency drops? All three hated it. Internet is essential infrastructure for work, school, healthcare, and job searching. Disconnecting faster often means losing the customer forever, and every retained customer avoids real acquisition costs. As the panel noted, there is a huge difference between a customer who won't pay and a customer who can't pay.

Should customers have more ways to spend less before they cancel? All three loved it. Downgrades, vacation pricing, short-term payment relief, equipment adjustments, and referral programs are all levers. Georgette's math: if someone saves $15 to $25 a month for six months and stays another five years, everybody wins. Rick added that any relief should be transparent, transactional, and easy to reverse, like a lower speed tier the customer can upgrade from when they're back on their feet.

Is it better business to prioritize high ARPU customers over retaining those who are struggling? All three hated that one too. Lower income customers refer their neighbors, stay for years, and strengthen local reputation. ISPs win by maximizing lifetime value, not monthly value.

What If Conditions Keep Getting Worse?

The closing scenario asked the panel to pick one strategy for the next 12 months: protect ARPU with pricing discipline and tighter collections, or protect relationships with flexibility and temporary relief. Everyone chose relationships.

Georgette's reasoning: the revenue follows the relationships, and relationships rarely follow aggressive collection measures. Customers who feel trapped often leave through the back door, including disputing charges instead of calling. Customers remember how they were treated during hard times, and many upgrade again when things improve.

She also suggested testing it. Identify customers whose payment behavior has shifted, proactively offer half of them a relief option or the referral program, and compare retention against the rest. Flexibility is not weakness when the options are well designed.

Rick closed on the point the whole panel agreed on: these options only work if they are defined, consistent, and proactive, not improvised differently by every person on the team.

Listen to the Full Episode

Catch the full conversation on the Bandwidth podcast.

Available now on Spotify, Apple Podcasts, and the Bandwidth YouTube Channel.

If you enjoyed this episode, be sure to subscribe wherever you get your podcasts so you never miss a conversation.