Utility contact volume is close to flat until it is not. A storm, a substation fault, or a widespread outage produces the sharpest demand curve in any customer-facing industry, and unlike retail peaks it arrives with no notice at all.
Three distinct contact types, one queue
Outage events generate reports of a loss of supply, requests for restoration estimates, and — critically — safety reports about downed lines, gas odours, or damaged equipment. These are not equivalent, and routing them identically is the most consequential design mistake available in this sector.
A safety report is not a customer service contact. It needs its own path and its own urgency.
Safety reports need an unconditional escalation route
An agent taking a report of a downed line or a gas smell should have one job: capture the location precisely, give the caller the scripted safety instruction, and escalate immediately. There is no version of this where agent judgement improves the outcome, and the escalation path has to work at full queue depth rather than only when things are calm.
What agents can safely say about restoration
Restoration estimates change, and an agent repeating an estimate that later slips creates a second, angrier contact. The workable approach is to relay only what the operational system currently shows, state plainly that it is an estimate, and avoid any commitment beyond it. Scripts that allow reassurance beyond the data cause more damage than a blunt “we do not know yet” does.
Volume rises as your own capacity falls
Widespread events affect staff as well as customers. The value of outsourced coverage is that the agents are not in the affected area, and that only holds if it was arranged in advance — routing, access, and authority all take time to establish and cannot be improvised while the event is running.
Deflection is worth more here than anywhere
A well-maintained outage map, proactive text updates, and an accurate recorded message remove a large share of “is it off, and when is it back” contact before it reaches a queue. Programmes that invest here first need materially less live capacity during an event.
Measure the tail, not the peak
Everyone watches the spike. The number that predicts customer sentiment is how long the queue stayed elevated after restoration, because those are billing questions, damage claims, and complaints — and they arrive when the emergency staffing has already stood down.
The energy and utilities outsourcing overview covers the wider service mix.