Churn, worst MVNO enemy!

1. Why Does a Customer Switch Mobile Operators?

I’m coming back with this blog post to one of the topics I find most interesting in our industry: customer satisfaction and customer experience.

In this article 8 Obvious and Not-So-Obvious Ways to Reduce Churn as an MVNO, Casey Zabaleta argues that an MVNO should not focus solely on acquiring new customers while maintaining a high churn rate at the same time.

To achieve this, she identifies three basic conditions that an MVNO needs to guarantee:

• A reliable mobile service.
• Good visibility into usage and billing.
• Strong customer support.

As I have been advocating for years, customer experience is one of the key differentiators for an MVNO, particularly in an increasingly saturated and competitive market, I will focus in this article en 1st and 3rd point above, let’s keep second for a future entry.

But this raises one of the biggest challenges:

How can an MVNO guarantee a reliable mobile service if it does not control the network delivering that service?

Even in the case of a Full MVNO, one of the most critical elements in ensuring service reliability, the Radio Access Network (RAN), remains completely outside the MVNO’s control.

However, not being in control does not mean being unable to understand what is actually happening.

And this is where I believe we need to change the way we look at the problem: by turning the subscriber’s own device into an observation point for customer experience.

2. OBSERVE: Understand What the Customer Is Actually Experiencing

The first step is to observe.

Instead of relying exclusively on network-side measurements, we can continuously collect information directly from the subscriber’s device.

This can be achieved through a lightweight SDK embedded in the operator’s application, capable of collecting device telemetry.

The difference is significant: we move from observing only the network to observing the customer’s actual experience.

3. UNDERSTAND: Put the Data into Context

Collecting data is not enough.

The next step is to understand: turning individual telemetry events into meaningful context that enables engineering, operations and customer-care teams to determine what is actually happening to a particular subscriber, device or group of users.

This is where the operator starts moving from simple infrastructure monitoring towards a real understanding of customer experience.

It is no longer just about knowing that there is a problem, but understanding where, when, how and who is affected.

4. PREDICT: Identify Risks Before They Become Problems

The next step is to predict.

By using historical and aggregated device-side information, it becomes possible to identify patterns, anomalies and customer segments that may require attention.

This represents a fundamental shift:

we move from analysing individual incidents to identifying patterns that can have a real impact on the business.

For example, certain behaviours may indicate emerging service-quality issues, recurring problems associated with specific devices or locations, or even situations that increase the likelihood of customer churn.

The objective is not simply to react faster, but to identify potential problems before the customer experiences them — or before they become a reason to leave.

5. DECIDE: Turn Intelligence into an Operational Action

After observing, understanding and predicting comes the moment to decide.

The intelligence generated from the device needs to be translated into an operational decision.

Engineering, operations, customer-care and commercial teams need access to the right information to determine what action should be taken, and on which customer or group of customers.

And this introduces another critical element:

all teams should be able to work from the same device-side source of truth.

Each team will have a different perspective:

• Engineering → Network and radio behaviour.
• Customer Care → Individual device and subscriber context.
• Commercial teams → Churn and ARPU exposure.
• Management → Aggregated KPIs and KQIs.

The information is the same. What changes is the perspective from which each team uses it.

6. ACT: Resolve the Problem, Not Just Identify It

None of the above has any real value if we are unable to act.

Identifying a problem and displaying it on a dashboard does not solve the problem.

In certain situations, we should be able to resolve the issue remotely, without relying on traditional manual troubleshooting processes.

This is where the capabilities of the device itself become particularly relevant, especially when the problem is related to device configuration. The ability to automate communication between the MVNO and its Host Operator can also play a critical role.

True automation does not stop at showing you the problem.

It should provide teams with the mechanisms required to take action directly on the device and resolve the issue whenever possible.

7. LEARN: Turn Every Interaction into Reusable Intelligence

And finally, in the age of AI, learning is critical.

Every interaction, measurement, diagnosis and action generates information that should not be lost.

The objective is to close the loop: retain and aggregate the information generated across devices, diagnostics, measurements and actions so that customer experience can be analysed over time.

This allows the system to learn from what has happened and continuously improve the operator’s ability to detect, anticipate and resolve problems.

The result is a continuous feedback loop in which every customer interaction becomes an opportunity to improve the next one.

8. OBSERVE → UNDERSTAND → PREDICT → DECIDE → ACT → LEARN

In my view, this is the path from reactive network and customer management to proactive experience management.

Because, ultimately, a customer does not leave an operator because a network KPI is poor.

They leave because their experience is poor.

And if we want to reduce churn, perhaps we should start by measuring, understanding and improving exactly what the customer experiences:

their device and their actual service experience.