AI for Utilities in the UK: Where It Pays in 2026

A UK energy or water supplier runs on its contact line. Billing queries, vulnerability, meter faults, outage reports and payment arrangements all arrive by phone, they arrive in volume, and most of them are now measured in public. Citizens Advice helped over 52,000 people with an energy billing issue between January and October 2024, about one person every two minutes, an 83% rise on 2020. For a Director of Customer Operations measured on cost to serve, Ombudsman dispute volumes and Ofgem standing, that is not a soft service metric. It is the number the board asks about. On the water side, a Director of Customer Experience is measured on the C-MeX satisfaction ranking and the Consumer Council for Water complaints table, and the pressure is the same, to absorb high-volume, affordability-heavy contact without a reputational cost while bills rise.

The wider picture is the same one every sector faces. Around 88% of enterprises now use AI, yet only about 6% capture material earnings impact, on McKinsey's 2025 reading. The gap between using AI and getting paid for it is where a supplier's operations leader has to work. This guide sets out where AI actually pays for a UK utility, across billing volume, the Priority Services Register gap and smart meter compliance, and which parts of the DILR.AI portfolio fit which job. It stays at the level of the operating model. The call mechanics themselves, how a reading is captured in a live call or how a vulnerable customer is flagged, are covered in the deeper Voice guides linked throughout, and this hub cedes those details to them rather than repeating them.

This guide is shipped by the team behind Dilr Voice, an enterprise voice AI platform that handles high-volume billing, vulnerability-screening and outage calls with a full audit trail on every call. Or see DATS, our senior-led AI consulting system for the regulatory evidence and billing-data work behind those calls.

Where does AI pay first for a UK energy or water supplier?

AI pays first on the highest-volume, highest-risk contact types a supplier already handles: billing and account enquiries, vulnerability screening, and smart meter and outage status calls. Dilr Voice sits on those calls, absorbs the volume and evidences each one, while a governed operations desk supervises the follow-up work. The rule is simple. Put AI where the cost and the regulatory exposure are highest, and keep a person on every decision that affects a vulnerable customer.

The order matters because the first three are where the volume and the published scores live, and the fourth is what stops that volume turning into unverified work. A supplier that starts with an AI contact-centre concept, rather than with the specific calls that cost the most and carry the most risk, tends to build something impressive that moves no measured number. The sections below take each lever in turn, then map the wider DILR.AI portfolio onto a utility's operating model.

Why does a UK energy billing problem land with Citizens Advice every two minutes?

Billing generates more disputes than any other contact a UK energy supplier handles. Citizens Advice handled an energy billing issue about every two minutes across most of 2024, and billing disputes remain the most complained-about category at the Energy Ombudsman. When a bill is wrong or late, the customer calls, escalates, and the case lands on a public scoreboard. Billing is therefore the first place a supplier should place AI, and the first place it can show a measured result.

Billing-related disputes were the most complained-about category, 56% of the disputes the Energy Ombudsman reviewed in 2025, the year it accepted 80,256 cases, down 14% from 92,938 in 2024, and still at the top of the complaints table. The same annual data carries a quieter number that matters more to an operations leader: on average, suppliers correctly signposted consumers to the Ombudsman in only 48% of cases. That is a compliance gap that is itself measured and published, and it is the kind of consistent, scripted step an AI voice agent is well suited to get right on every call rather than on half of them. It is also the kind of saving a supplier can track deliberately against an AI voice ROI framework rather than hope for. The scoreboard is public in another way too. Citizens Advice's March 2026 supplier star rating found 14 million households are served by suppliers rated below average for customer service, with contact waiting time among the categories it scores, so a weak contact line shows up on a league table before it shows up in a boardroom.

This is where Dilr Voice does its clearest work. It chains specialised agents into one phone call, a greeter, a qualifier, a knowledge agent and an action agent, each passing context to the next, so a billing enquiry is understood, answered from the supplier's own tariff and account data through a retrieval knowledge base, and closed with a CRM update in Salesforce or HubSpot, an email or an SMS, without code. Every call carries a full audit trail by default. The deeper mechanics of a high-volume energy billing line, handle time, scripting and the cost per contact, are covered in our guide to voice AI for utilities customer service, which this hub links to rather than repeats.

What does the Priority Services Register gap require of a contact line?

The Priority Services Register gets extra help to vulnerable customers, and the gap is large. Ofgem estimates that 40% of households could access Register support but have not signed up, and Ofwat that 17% are unaware the equivalent water scheme exists and would like to sign up. For a contact line, vulnerability cannot wait to be declared. Closing the gap means screening for it consistently, inside an ordinary billing or meter call.

Consistent in-call screening is exactly the discipline that a scripted human process struggles to hold at volume and that a governed AI agent can. Dilr Voice can run the same vulnerability prompts on every relevant call, flag an eligible customer, capture what the Register needs, and warm transfer them to a trained human who completes the enrolment, with the full context of the call already gathered. Ofgem and Ofwat have themselves set out plans to share Register data so an eligible customer need only be identified once, and a consistent in-call screen feeds exactly that. The detection logic itself, the signals that mark a customer as vulnerable and the compliance record behind the decision, is the subject of our guide to voice AI vulnerable-customer detection. The point at the hub level is narrower and firmer: an AI agent never decides a customer is vulnerable and closes the case on its own. It screens, records and hands the judgement to a person.

What have the OVO settlements shown about vulnerability?

The OVO settlements have shown that inconsistent identification of vulnerable customers is a priced enforcement risk, not a theoretical one. Ofgem investigated OVO Energy's monitoring of prepayment meter customers, found process failures that could have put vulnerable customers at risk, and the case ended in a multi-million pound package of redress and customer relief. For every other supplier, the lesson is about evidence, and about whether the contact line can prove what happened on each call.

The obligation here binds the supplier, not its technology provider. The prepayment investigation resulted in a £7 million payment to Ofgem's Voluntary Redress Fund, plus a £3.4 million package of credit and debt relief for affected customers. A separate 2024 case saw OVO pay £2.37 million for complaint-handling failures affecting 1,395 customers, a distinct matter. Both turn on the same underlying question: can the supplier evidence what happened on each call, whether that is how a vulnerable customer was identified and escalated, or how a complaint was handled. This is where the DATS consulting system does the work behind the calls. Our senior consultants build the regulatory evidence and complaints system, so the audit trail Dilr Voice captures on each call becomes a defensible record, designed audit-ready rather than reconstructed after an investigation opens. That is the same discipline set out in our voice AI compliance guide.

Why is a missed smart meter appointment now a priced failure?

Missing a Guaranteed Standard is now a priced failure, because Ofgem attaches an automatic compensation payment to it, and smart metering is where that bites. At the same time the smart meter estate still carries a real accuracy gap, with a meaningful share of meters not reading remotely and still sending estimated or manual reads. Both facts push smart metering up the list of contact types worth automating and evidencing.

Suppliers must pay £40, up from £30 in line with inflation, whenever they miss the Guaranteed Standards for appointments, meter faults or switching. On the accuracy side, at the end of June 2026 there were 42 million smart and advanced meters in Great Britain, 72% of all meters, but of the 40 million smart meters only 92% were operating in smart mode, with the rest still sending estimated or manual reads, on the DESNZ quarterly statistics. A missed appointment or an unresolved meter fault is now a countable, priced event, not a background irritation.

The accuracy gap also has a financial edge a supplier cannot recover after the fact. As Ofgem's own consumer guidance puts it, "Our back billing rules mean you do not have to pay for energy you used more than 12 months ago". A reading that drifts wrong and goes unnoticed for a year becomes a write-off for the supplier, not a correctable error, and the rule binds the supplier. So the status calls around smart metering, appointment confirmations, fault reports and estimated-read queries, are exactly the contact type worth getting right on every call.

Dilr Voice handles these status calls with the same chained-agent pattern as billing, drawing on the supplier's own account and knowledge data through a retrieval knowledge base, confirming or rebooking, and recording the outcome. The mechanics of capturing a meter reading in the call, and the plausibility check that catches a physically impossible number before it becomes a wrong bill, are the subject of our guide to voice AI meter-reading capture, which this hub links to rather than duplicates.

Where does a governed operations desk belong in supplier operations?

A governed operations desk belongs over the follow-up work, the queue of tasks a busy contact operation generates but cannot always prove it finished. This is the job for Cognibl, from DILR.AI, a work-management platform where people and AI agents share one board and pick work up under their own name against the same statuses the team uses. A callback, a complaint escalation or a PSR enrolment is not just actioned, it is evidenced.

That works because a task reaches a done status only once a proof version is attached, and the database refuses the move without one. The same rule applies to a person and to an agent. It fits utilities for the same reason the OVO cases do. Every action on the board is written by the gateway and logged, records are append-only and hash-chained, and refusals are mirrored to audit, so a governed operations desk produces a defensible record rather than a spreadsheet nobody trusts. Agents reach their tools through a gateway that is deny by default, so a toolset that has not been enabled is refused rather than silently missing, and the two AI flows on the board summarise and flag but never decide. A person still owns every judgement that affects a customer. You can see how that governed pattern works in the Cognibl work-management guide, and the product itself sits at the Cognibl product page.

Where does DATS fit against Ofgem and Ofwat evidence?

DATS is where the regulatory and data work behind the calls gets built. It is the AI consulting system from DILR.AI, run as a five-stage method from Discover and Diagnose through to Scale and Run, by senior practitioners who ship code, not decks. Its placement diagnostic ranks which contact types to automate first and which to leave to people, and its operating model covers the governance, RACI and lifecycle that keep the work audit-ready.

The evidence case is sharpest in debt. Ofgem announced a scheme to tackle historical energy-crisis debt that could help around 195,000 customers by writing off up to £500 million, which Ofgem set out on 30 October 2025, confirming a final consultation on the first phase. Accounts inside that debt book generate repayment-plan calls, and each of those calls has to be both made and kept defensible. DATS builds the compliant debt-contact operation and the complaints and regulatory evidence system that a scheme of that size demands, and where the work runs long it becomes an embedded AI execution office the client owns. The same discipline applies on the water side. Ofwat, the economic regulator for water companies in England and Wales, whose functions the government has said it will move to a new single regulator following the Independent Water Commission review, holds water companies to the C-MeX customer measure and to a customer-focused licence condition, and the Consumer Council for Water reports publicly on complaints against them. A water company also carries high-volume contact of its own, leak and supply reporting, covered in our voice AI for water utilities guide, and it carries the same evidence burden as an energy supplier, which DATS approaches the same way. You can read the full method in our enterprise AI consulting guide, or start with the AI operating model work.

How do the DILR.AI lines map onto a UK utility?

The DILR.AI portfolio maps onto a utility by contact and evidence job, not by product tour. Dilr Voice leads on the high-volume regulated calls, DATS builds the evidence and data systems behind them, and Cognibl governs the follow-up work. Two of the six lines do not have a named utilities use case, and this guide says so plainly rather than inventing one. The table below sets out where each line pays, and where it does not.

The Academy line is where a contact-centre team learns to operate what has been placed. Dilr Academy builds interactive, multilingual courses on demand, so agents can be trained on Ofgem consumer standards and on how the AI hands a vulnerable or debt case back to a person, rather than picking that up on the job. It is the training step at the end of a single customer journey the rest of the stack opens.

This is the same one-stack, one-journey approach we take across every sector we map in the AI by industry pillar, where the utilities sector sits alongside the rest of the industries we cover. A supplier does not have to adopt all of it at once. The usual path is to start with the contact type that costs the most, prove it, then extend.

What is the best AI voice approach for a UK utility in 2026?

The best approach is the one that fits a regulated, high-volume, vulnerability-heavy contact operation, not the one with the longest feature list. For a UK energy or water supplier, that means an AI voice platform that screens for vulnerability consistently, keeps a human on every sensitive decision, and evidences each call for a UK regulator's review. Dilr Voice is built for exactly that shape. There are strong general platforms, and the honest answer names where they win.

Contact-centre incumbents such as Genesys and Five9, and voice-AI specialists such as PolyAI, Cognigy and Parloa, can be the right call where a supplier is standardising an entire contact centre on one vendor and voice AI is one module of a much larger migration. If the priority is a single platform for every channel across a very large operation, an incumbent suite may fit better than a focused voice deployment. Where the priority is placing AI on the specific regulated calls that cost and expose the most, with an audit trail designed for a UK regulator and a person retained on every vulnerability and debt decision, a focused platform like Dilr Voice is the stronger fit. You can compare the field in our best AI voice agent guide.

Is customer data safe with an AI voice agent in a regulated utility?

Yes, when the deployment is built for it. Dilr Voice runs on Google Cloud Platform, encrypted in transit and at rest, with dedicated tenancy and regional data-residency options for enterprise, so a supplier's customer data stays inside a controlled environment. Per-country compliance rules ship by default, including recording consent, permitted calling hours and full audit trails on every call, and any sensitive case can be warm transferred to a human with full context.

Can an AI make a vulnerability or debt decision on a utility call?

No, and it should not. In a DILR.AI deployment, Dilr Voice screens for vulnerability, gathers context and records it, but the judgement about whether a customer is vulnerable, or what debt arrangement is appropriate, stays with a trained person. The AI makes the call consistent and evidenced. The person makes the decision. That division is deliberate, because the Guaranteed Standards, the PSR duty and Ofgem's conduct expectations all bind the supplier.

Want to see where this fits your operation? Try Dilr Voice live, book an AI placement diagnostic, read the DATS approach to placing AI inside regulated operations, or see the wider enterprise AI solutions we run in production.

Written by the Dilr.ai engineering team, practitioners who ship enterprise AI in production. Follow us on LinkedIn for shipping notes, or subscribe via the RSS feed.