Industry guides

Utility Customer Service Phone Handling: Faults and Outages

How utility customer service teams can put emergencies first, cope with outage surges, support customers in difficulty and use automation carefully.

Call editorial team · Published · 5 min read

Utility customers do not choose their provider the way they choose a restaurant, and they call at the worst moments: when the power is out, the water is brown or the bill looks wrong. The phone is the main route for urgent reports, and a failure to answer is not just poor service, it can be a safety risk.

A customer service adviser with a headset in a utility control and contact room
Illustrative image

This guide is for electricity, gas, water and telecommunications-adjacent utilities, and for contractors who handle their calls. It looks at how to separate emergencies, plan for outage surges, support callers in difficulty and use automation carefully. See also Supporting Vulnerable Customers by Phone and Designing Service Levels.

Three kinds of utility call

Routine, urgent and sensitive

RoutineUrgentSensitive
ExamplesMeter reading, change of address, tariff questionGas smell, power line down, burst main, no supplyStruggling to pay, bereavement, health reliance on supply
Speed neededSame day is usually fineImmediateUnhurried but prompt
Best handlerSelf-service or standard agentEmergency team, no queueTrained advisers
Risk if mishandledFrustrationHarm to people or propertyDistress and complaint

The structure of the phone menu should follow this table. Urgent options come first, and urgent callers hear what to do for safety before any menu.

Putting emergencies first

A caller reporting a gas smell needs to hear immediately what to do: leave the building, avoid switches and flames, and call the official emergency number for your area. Staff and recorded messages should use the exact wording agreed with your safety team and regulator.

An emergency-first menu

  1. Safety messageBefore any option, a short statement of what to do in an emergency and which number to use.
  2. Emergency optionThe first menu option for gas, electrical or water emergencies, going to a staffed queue.
  3. Fault reportsA second option for loss of supply or faults that are not dangerous.
  4. Everything elseBilling, accounts and moves, in a second step.
  5. Always a way outA visible route to a person at every level.

Do not put emergencies behind identity checks or long menus. Ask the caller's location and details after the call is answered. Emergency Messages in Your IVR has wording and structure suggestions.

Planning for outage surges

When supply fails, thousands of customers call within minutes, and the call volume has little relationship to staffing. The answer is not to staff for the peak, which is unaffordable, but to give most callers the answer without a person.

Tools for an outage

  • Recorded status messageKnown area, cause if known, and a realistic update time.
  • Fault reporting optionTake the address and details quickly, without a long conversation.
  • CallbacksOffer a call back when the situation changes, rather than holding.
  • OverflowRoute excess calls to another team or to an agent that takes reports.
  • UpdatesChange the message whenever the situation changes, and say when it was last updated.

Only publish dates and times you can keep. A message that says "supply will be restored by 6pm" and is wrong makes the next call angrier. Crisis Readiness for Contact Centres covers the planning in more detail.

Customers in difficulty

Bills are the other source of distress. Callers who cannot pay need a human who listens, explains the options available and records what was agreed. An automated line that reads a payment reminder to someone in difficulty can do real harm.

Ethics in Collections Calls and AI Reception and Elderly Callers offer further guidance.

Where automation helps

Routine tasks are a good fit: meter readings, opening hours, explaining a bill layout, how to report a fault online, moving house. A voice agent can answer them from approved text and take a request. It should be designed to hand over whenever a caller sounds distressed, mentions safety or asks for a person. It should not decide on payment arrangements, disconnections or disputes.

TaskAutomate?Note
Opening hours, contact detailsYesApproved text only
Meter reading submissionYes, if connected securelyConfirm back to the caller
Moving home requestTake the detailsStaff process
Gas or electrical emergencyNo: immediate human or official numberSafety first
Payment difficultyNo: trained adviserRecord the agreement
ComplaintTake the detailsHuman follows up

See Voice AI Guardrails and The EU AI Act and Voice Agents for the wider picture on responsible automation.

Accounts, identity and recordings

Utility accounts carry addresses, usage patterns and sometimes vulnerability information, which is sensitive. Verify identity before discussing an account, record only what is needed, and keep access tight. See Access Controls in a Contact Center and Data Retention for Call Recordings.

Measuring service

Utility phone dashboard

  • Time to answer emergency calls, reported on its own
  • Fault reports taken and the time to a first update
  • Calls per outage and the share handled by recorded messages
  • Complaints and how fast they were acknowledged
  • Repeat calls about the same fault or bill

Report emergency calls separately from the rest. Blending them with routine calls hides exactly the failures that matter. The 80/20 Service Level explains how targets are set and why they differ by call type.

A worked example: a storm night

Imagine a regional distributor on a night when high winds bring down power lines. Within minutes, many customers call. Some have lost supply; one reports a wire on the ground; others call about their bill, unaware of the outage.

With an emergency-first menu, the safety message plays first: stay away from fallen lines and use the official emergency number. The caller with the wire on the ground reaches the emergency team immediately. Customers reporting a loss of supply hear the current status message and may leave their details or ask for a callback. Billing callers hear that billing is closed tonight, and can leave a message. The example is hypothetical, but it illustrates why urgent calls should never have to wait behind routine ones.

Doing it in Call

In Call, an IVR can put the emergency option first and send it to its own staffed queue, with fault, billing and account options in the next step. Business hours decide staffing and what callers hear when closed, and callback requests help during surges. An AI agent can answer routine questions from your approved text and hand over on safety or distress. Call summaries, contact records and supervisor views help managers see what is happening during an event. See Setting Up Call Queues and Supervisor Live Listening.

Frequently asked questions

Should emergencies go through the same menu as billing?

No. Put the emergency option first or announce the safety message before any menu, and route it to a staffed queue.

Can an AI agent take fault reports?

It can collect address and fault details and pass them on. Gas, electrical or water emergencies should go to a person or the official emergency number immediately.

How do we cope with an outage surge?

Use a short recorded status message, offer callbacks and fault reporting, and add overflow. Update the message whenever the situation changes.

How should we treat customers who cannot pay?

Offer a human conversation with a trained adviser and record what was agreed. Avoid automated pressure.

Do we need to record utility calls?

Many do for quality and complaints, but rules differ. Check regulator guidance, tell callers, and limit who can access recordings.

What should we measure first?

Time to answer for emergency calls, reported separately, then fault-report handling and repeat calls about the same issue.

Put emergency calls first and plan for outages in Call

In the demo console you can try incoming calls in a simulation.

Related guides