Openreach Make UK Organisation Changes to Improve Performance
Network access provider Openreach has moved to improve how they engage with UK communication providers (e.g. broadband ISPs) and their customers by making a series of organisational updates, which they hope will deliver an “even sharper focus on customer experience and end to end operational performance“.
The first step in this involves the creation of a new Customer Experience team, bringing together several parts of the business already dedicated to service and transformation. Surinder Khatter, Managing Director within Service Delivery, has thus been appointed Chief Customer Experience Officer (CCEO) to lead this new unit. “Surinder will oversee how we manage every stage of the customer journey, from getting customers onto our network quickly and easily to the communications they receive and the behind-the-scenes processes that keep services running smoothly,” said the announcement.
Openreach are also unifying all their service engineering capability into a new Service Operations team. This will be led by Pete Stewart, currently MD of Service Delivery, GB Operations. The new unit will bring together UK Operations, their FTTP service engineering teams, the Complex Engineering teams responsible for maintaining the copper network, and their Civils teams.
Advertisement
Openreach Statement
By bringing these teams together, we aim to deliver an even more joined up, efficient and responsive service. This will help us connect customers faster and more effectively, while continuing to improve the day-to-day experience for the people who rely on our network.
Engineers in this structure will benefit too, with access to a broader mix of work and more opportunities to build new skills. This approach helps us preserve essential copper expertise while continuing to grow and strengthen our fibre capability across the network.
The changes will come into effect on 1st April 2026.
Mark is a professional technology writer, IT consultant and computer engineer from Dorset (England), he also founded ISPreview in 1999 and enjoys analysing the latest telecoms and broadband developments. Find me on X (Twitter), Mastodon, Facebook, BlueSky, Threads.net and Linkedin.
Advertisement
Leave a Reply
Privacy Notice: Please note that news comments are anonymous, which means that we do NOT require you to enter any real personal details to post a message and display names can be almost anything you like (provided they do not contain offensive language or impersonate a real person's legal name). By clicking to submit a post you agree to storing your entries for comment content, display name, IP and email in our database, for as long as the post remains live.
Only the submitted name and comment will be displayed in public, while the rest will be kept private (we will never share this outside of ISPreview, regardless of whether the data is real or fake). This comment system uses submitted IP, email and website address data to spot abuse and spammers. All data is transferred via an encrypted (https secure) session.
Openreach will still be in the awkward situation of “engaging” both with CPs and with end customers at the same time as trying to keep its distance from the latter.
A new approach will need to be a lot cleaner and clearer.
For the last five weeks I have (edge case, to be honest) been receiving appointment reminders from Openreach by text, confirmations by email, notifications of delays, prompts to re-book by text and email, even two Openreach(!) phone calls: all at the same time Openreach systems engage with my ISP who prompt me and alert me to the same appointments, prompts, reminders, and changes blizzard. (My ISP mostly uses email, occasionally text, but documents everything with updated ticket statuses.)
I realise that some customers choose to ignore email, others ignore any text with a hyperlink, and everyone blames the junk folder. But cleaning up who to expect to update you about what could quite be a tricky challenge. Good luck.
I want Openreach to setup Live Engineer Visit via app (for live tracking) would be a good idea!