What the Ofcom data is really telling you about your operating model
Three patterns in the Q4 2025 complaints data that the headlines missed.
The Q4 2025 Ofcom complaints figures came out a few weeks ago and almost every outlet that picked them up ran the same story. Complaints up for the first time since 2023. Mostly driven by mobile mid-contract price rise announcements from O2 and others (mild regulator finger-wag). Cue pieces about the cost of living and consumer trust.
All fair and accurate. And the wrong story for a service leader.
The interesting thing about regulator complaints data is not the headline number. It’s the operational gap between providers selling broadly the same product, in the same market, under the same rules. That gap, the one between the best and the worst, is where the lessons actually live. And the lessons in this latest set of numbers are worth a closer look.
Three of them are worth your attention. This isn’t really a piece about telecoms. It’s about what the data exposes about the operating models inside any service business, and what to do about it if you find yourself running one.
Observation one: the gap that only operating model explains
Vodafone took 11 broadband complaints per 100k customers in Q4 2025. Virgin Media took five. The industry average sat at seven. Same broadband technology, broadly comparable products, the same regulator looking over their shoulders.
That gap, more than double the complaint rate in the same market, has to be explained by something. Strategy doesn’t explain it. Pricing doesn’t. Brand doesn’t, at least not all of it.
I worked at Virgin Mobile in the UK when we ran on the T-Mobile network. The network was identical: the same masts; the same coverage; the same dropped calls. Every year, JD Power ranked Virgin higher than T-Mobile on network performance. The reason was the Virgin brand halo. Customers wanted to believe their service was better, and so they perceived it as better. Brand absolutely shifts perception, and to some extent it shifts whether people bother to escalate a complaint at all.
But there is a limit to what brand can do. Complaints to a regulator are not a satisfaction score. They are someone deciding that service was bad enough to actively put effort in to report it. Brand halo can soften the edges. It cannot turn a failed installation into a successful one, or stop a fault going unfixed for three weeks. The 11-versus-5 gap is too wide to be brand alone, and what’s left is operating model. The unglamorous work of doing the basics consistently well.
So the practical takeaway for any service leader reading this: stop benchmarking your service operation against the sector average. Benchmark against the best in your sector. That number is what’s actually possible in your market, because someone is already there.
Observation two: the unglamorous 52%
As others have stated, over half of Vodafone’s broadband complaints, 52% to be exact, came from issues with the broadband service itself: faults, service performance, and provisioning. Not journey design. Not voice of customer programmes. Not omnichannel strategy. The boring middle of the operating model: does the kit work, does the install happen on the day it’s booked, does the fault get fixed inside SLA.
This is what businesses consistently under-invest in, not because service leaders don’t want to fix it, but because operational basics don’t compete well for board attention against shinier strategic initiatives. The slide on “AI-driven self-service” or “frictionless customer experience” lands better than “we need to improve our installation right-first-time rate from 78% to 85%.” So the operational basics get squeezed out of the investment plan, year after year, while the leadership team spends its energy on the bits that look strategic in a deck.
The Ofcom data is a useful. It says that for the most complained-about broadband provider in the country, more than half of the reason customers are escalating to a regulator is operational failure. Not a clever experience design problem. Not a digital transformation issue. Things not working the way they’re supposed to.
There is a number worth thinking about. In many service operations I’ve worked in, somewhere between 30% and 60% of contact volume is “failure demand,” contact that should never have happened because something broke. If that’s true in yours, then a substantial chunk of your operating cost is being spent cleaning up after preventable failures. That’s also where the genuine ROI of any improvement programme lives. Not in the headline-grabbing transformation, but in the unsexy work of fixing what’s already breaking.
Before you buy anything new, fix what’s already broken. The data shows you exactly where to look.
Observation three: the price rise that became a service event
The mobile complaints spike came from mid-contract price rise announcements in Autumn 2025. Several providers told their existing customers they’d be paying more, mid-contract. The decision was made by commercial teams, signed off by leadership, and landed in service operations after the fact. The wave of inbound contact, the churn risk, the regulatory scrutiny: all of it was predictable from the moment those comms went out.
This pattern is everywhere, in every sector, not just telecoms. Pricing changes, product launches, system migrations, billing updates, marketing campaigns. Decisions get made in one part of the business, and the service operation finds out either at the same time as customers or shortly afterwards. By the time the volume hits, the staffing isn’t there, the advisors haven’t been briefed, the FAQ on the website is out of date, and the conversation has already turned into a complaint.
The instinctive response from senior service leaders is usually to get better at firefighting. Build a rapid response capability. Improve forecasting. Hire flex resource. All of that helps at the margins, but it treats the symptom, not the cause. The real fix is structural. Service has to be at the table when those commercial decisions are being made, not informed about them afterwards.
That sounds like a soft, political point. It isn’t. It’s an operating model question. Either the service function has the standing, the relationships and the data to push back on commercial decisions before they go live, or it doesn’t. If it doesn’t, you’ll keep being surprised by the same kind of event quarter after quarter, and the Ofcom data will keep telling the same story.
Ofcom data isn’t really a league table. It’s a mirror. The thing it shows you most clearly isn’t where everyone else is. It’s what’s possible in your market, because someone in your market is already achieving it. Best in class isn’t an aspiration, it’s an existence proof.
Three questions worth carrying out of any data set like this:
How does our complaint rate compare to the best in our sector, not the average?
What share of our contact volume is operational failure that should never have happened?
Are we involved when commercial decisions land in our operation, or finding out afterwards?
If the answers are uncomfortable, that’s the point. Uncomfortable is useful. It tells you where the genuine improvement lives.
The temptation when reading data like this is to look for reassurance. Most providers are average. Most operations are flawed. The regulator is mainly worried about a few outliers. Resist it. Treat the data as a finger pointing at your own operating model. Then go and see what it’s actually pointing at.
Brand promises don’t close the gap. Operations do.