First Call Resolution in Utilities: A Teardown of the 6 Handoffs That Kill It

Most utility teams measure resolution with a disposition code. The agent picks resolved, the call closes, the number looks healthy.

Customers use a harder test. If they ring back inside 7 days about the same account and the same reason, it was not resolved.

Use the customer definition. Repeat contacts inside 7 days on the same account and reason type, divided by answered calls, subtracted from 100.

Two rules keep it honest. Count a transfer as unresolved when the customer has to explain themselves twice. Count a promised callback as unresolved until the callback happens.

The Ofgem consumer satisfaction survey puts overall satisfaction with suppliers at 81 percent, with 2 percent of people reporting a complaint. Most dissatisfaction never becomes a complaint. It becomes a second call.

Takeaway. A disposition code measures agent confidence. A 7 day repeat measures resolution.

Every one of these leaks at a boundary. A person passes a call, a system passes a record, or a shift passes a queue.

1. Menu to agent. The customer already keyed the account number and the meter reference, then the agent asks for both again. Fix: pass what the menu collected into the screen pop, and delete any branch that does not change the routing decision.
2. Agent to billing. Bill shock calls after a tariff change need the consumption estimate, the last reading and the instalment history on one screen. Fix: build one read only view for the top three billing questions instead of three tabs and a calculator.
3. Agent to field. No supply and outage calls resolve when the agent can give a window, not a ticket number. Fix: surface field slot data in the screen the agent already uses, even when the honest answer is a two hour window and a caveat.
4. Service to credit. The customer rings about a bill, says they cannot pay it, and gets transferred to a team that closed at 5pm. Fix: let service agents set a small instalment plan inside a fixed policy band, and script the handoff for anything above it.
5. Shift to shift. The 4:50pm call turns into a callback promise nobody owns at 9am. Fix: callbacks get an owner and an SLA, not a note. Anything unowned after 24 hours lands in the supervisor queue.
6. Channel to channel. A web form, an email, an SMS reply and a call about the same problem are four tickets and one customer losing patience. Fix: thread by account, not by channel.

Takeaway. Five of those six are data and authority problems. Only one of them needs new staffing.

Five steps. One analyst, two days, no procurement.

1. Export last month answered calls with account number, disposition, handle time and daypart.
2. Flag every account that appears more than once inside 7 days. That is your repeat set.
3. Tag each repeat with the boundary it crossed: menu, billing, field, credit, shift or channel.
4. Rank boundaries by call minutes lost, not by call count. One 14 minute bill shock repeat costs more than three meter reading repeats.
5. Fix the top boundary only, then re-run the same export in 30 days against the same daypart.

Fix one boundary at a time and the number moves for a reason you can name in a finance review.

An illustrative example, not a customer. A 40 seat contact centre at a mid sized water utility in northern Portugal. Tuesday, 11:20.

A tenant rings about a bill for a flat she moved out of in July. The agent finds the change of tenancy request sitting unprocessed, says she will chase it, and promises a callback.

Nobody owns that callback. Nothing on the account records that she already called.

Thursday she rings again and explains the whole thing to a new agent. Same story, 9 minutes, and Tuesday still counts as resolved.

Three calls and 24 minutes later the account gets corrected. The dashboard reports three answered calls and one satisfied customer.

Takeaway. Change of tenancy and moving house calls are the quietest resolution leak in a utility book, because nobody files them as a complaint.

Most repeat calls get created in the last 20 seconds of the first call.

Three lines, in the customer language.

1. Name the outcome. Your instalment moves to 110 euro from the October bill, and nothing changes before then.
2. Name the proof. You will get an SMS within 5 minutes with that figure and the reference 4471.
3. Name the next step and the owner. If that SMS has not arrived by tonight, ring back and quote 4471 and it comes straight back to this team.

Play your last ten recordings from the 5pm hour. Count how many close with all three lines.

Takeaway. Confirmation beats politeness. People ring back because they are not sure it happened.

Two things drag the number down: calls nobody answers, and calls answered by someone without the data.

AutoNurture.AI answers inbound without a phone tree, identifies the customer, resolves what it can on the first call, and sends payment links, status updates or callbacks. The first boundary disappears.

When intent or risk rises, the call passes to a human seat with the transcript, the intent and the account already on screen, in under two seconds. Nobody makes the customer start again.

After hours is the cheapest win. inbound answered in under two seconds, around the clock, in 12+ languages means the 8pm bill shock call never becomes tomorrow callback.

For utilities the plumbing sets the ceiling, so read the integrations list before you script anything. Resolution depends on what the agent can read and write back.

The utilities and energy playbook walks the workflow end to end, from overdue accounts to payment plans inside the policy your finance team sets.

Takeaway. Automation covers the volume and the repetition. Your agents keep hardship, disputes and negotiation, where a person changes the outcome.

Practical, not scary. Walk this before you put AI on a live queue, then have your compliance team sign it off.

1. Recording notice delivered at the start of every call, in the customer language.
2. A clear statement that the caller is speaking with an AI worker, and a route to a human at any point.
3. Retention set and enforced on recordings and transcripts, with a deletion job you can evidence.
4. Data residency confirmed for processing, not only for storage.
5. Vulnerability flags read from the source system before the call is handled, not after.

Obligations vary by market and by regulator, so check with your compliance team before you sign anything.

Pull your repeat call rate for last month. If it sits above 20 percent, abandonment is not your most expensive number.

Then hear a sample call in your own language and book a demo, and we will map the six boundaries against your own queue live on the call.