WorkflowGrid Operations & Outage Management

Trouble Call Management

Trouble call management that pings the meters before the truck rolls, so crews go only where the power is really off

See one case, screen by screen ↓
Watch with transcript →

Built forOutage desk dispatchersOutage desk supervisorsContact center agentsField crews

The Problem Today

Each call is logged on its own, so trucks roll to homes where the fault is inside the home.

Each call read one at a time

  • Calls
  • App, texts
  • Map pins
  • Premises
  • Hazards hide in the queueA bang at the pole sits among the calls
  • Customers call twiceA home fault stays dark after the fuse is fixed

The Solution

  1. Each call read and mappedPremise and meter matched; calls on one device grouped together
  2. Meters pinged, fuse tracedCallers and neighbors answer; dark homes trace to the fuse they share
  3. Power on? A self-checkA home whose meter answers gets a fix-it message and a re-ping
  4. The dispatcher approvesOne incident and one crew, confirmed and sent by the dispatcher

Built-in controls

  • Hazard calls always go to a crew
  • Life-support customers get a person
  • Meters are read, never switched

What You Get

Fewer crew hours go to homes that have power, and a dark street gets one crew sent to its fault.

  • Home faults fixed without a visitSelf-check messages that customers solve themselves
  • One job per faultCalls on the same fuse become one incident, not many jobs
  • Customers told at onceThe restoration update and estimate sent by text and app
In short

What is Trouble Call Management?

Trouble call management is how an outage desk handles no-power calls: deciding, call by call, whether it is a network outage, a single home, an outage already known or a fault inside the customer's home, and sending a crew only where one is needed. Trouble Call Management does it with six agents that read, group, ping and trace each call, while the dispatcher confirms each incident and approves each crew.

How to choose AI solutions for utilities →

Updated

The problem

Trouble calls sorted by hand from words and a pin on a map

When a fuse blows on a lateral, the outage desk gets dozens of no-power calls in minutes, by phone, app and text. Each one has to be sorted by hand: a network outage on a fuse, transformer or feeder, a single home with a failed service cable, an outage the desk already knows about, or a fault inside the customer's own home, such as a tripped main switch, a residual-current device (RCD) or a blown fuse in the consumer unit. The dispatcher decides from the caller's words and a pin on a map, and many single-premise jobs end with the crew finding power at the meter.

The volume hides the calls that matter. “A bang and a flash at the pole” sits in the same list as forty “no power” calls unless someone reads each one, and a life-support customer looks like any other caller. Last gasp alone does not settle it: in a big outage, messages collide on the meter network and some do not arrive. And a caller with a tripped RCD inside a network outage stays dark when the fuse is replaced, calls again two hours later, and a second truck goes back to the same street.

estimated$250–$500for each truck roll, a conservative estimate
typical$9.54for a call to a utility contact center, across 15 utilities
typical366minof power lost by the average US customer in 2023, including major events
Where a month's crew days go on no-power calls that need no truckestimated
By hand80 days
With the solution5.1 days
  • Trips to homes whose meter shows power: the fault is inside the home63 → 2.6 d
  • Separate crews sent to calls on the same fault8 → 1 d
  • Second visits to homes still dark after the fuse is replaced5 → 1 d
  • Single-home jobs raised when the whole lateral is off4 → 0.5 d

Estimated split for two districts of the sample utility, in crew days a month (8-hour days), by hand and with the solution. The first row uses the sample's counts (338 jobs a month where the crew found power on at the meter before pings, 14 with them) at about 1.5 hours a job; the other rows are our estimate.

How it works

Each no-power call read, grouped, pinged and traced to its device

What comes in
Calls in4 sources · calls and app reports, meter pings and last gasps, outage incidents, premise history
Agents at work
Call readerpremise + hazard words
Then
Call grouper
Meter pinger
Then
Outage tracerlikely device
Then
Reply writer
Dispatch drafter
A person decides
Outage desk dispatcherconfirms and sends the crew
What comes out
Verified outage
One incident, one crew
Self-check reply
One case, step by step

One blown fuse, forty trouble calls and a single crew sent

One weekday evening at peak, in one district of a utility's network. At 19:41:52 a fuse on a pole near a primary school blows, and the lateral behind it drops seven transformers. Here is what happens next, screen by screen, in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 0119:42:10

    Forty no-power calls in four minutes, on the map as they arrive

    Outage desk dispatcher

    The dispatcher has the evening shift on the outage desk. The first call lands at 19:42:10 and by 19:46:05 there are 40 from the same neighborhood: 28 phone, 8 app and 4 text. Each call is a ring on the outage map, drawn on the feeder from its substation, with its laterals, the fuse and the nine transformers around the calls. At 19:44:02 the Call grouper opens a cluster on the lateral: 3 calls inside 400 m and 10 minutes, and no incident open there in the outage system.

    “40 no-power calls in 4 minutes” · 58 no-power calls tonight since 18:30

  2. 0219:43

    One call heard a bang at the pole: a hazard, crew first

    Call reader

    A customer reports from the app: “Loud bang and a flash at the pole by the school, then everything went off.” The Call reader matches the premise and the meter, finds the hazard words “bang” and “flash”, and flags the call to the dispatcher at once. Whatever that meter says later, this call is not answered with a self-check message.

    “The words “bang” and “flash” are on the hazard list. A crew checks the pole before the fuse is replaced. A self-check is never sent for a hazard call.”

  3. 0319:46:20

    Ping 214 meters: the callers and each neighbor

    Outage desk dispatcher

    Before anyone is sent, the dispatcher presses Ping 214 meters: the callers and their neighbors on 9 transformers. The Meter pinger sends on-demand pings through the head-end, with 3 retries per meter at most, and the wave runs out from the calls across the streets.

    “Ping the meters to see which homes are really off. Until then every call waits on the cluster, except the hazard.”

  4. 0411 seconds later

    38 callers off, 2 on, and one fuse behind the dark homes

    Meter pinger and Outage tracer

    At 19:46:31 the answers are in: of 214 homes, 171 are off and 43 are on; of 40 callers, 38 are off and 2 are on. The dark homes trace a single lateral back to one fuse, and the Outage tracer names it the likely device at 92%. From the first call at 19:42:10 to the outage confirmed with its fuse at 19:46:40 took 4 minutes 30 seconds.

    “Likely device: the lateral fuse · 92%” · “First call 19:42:10 → outage confirmed with its fuse 19:46:40 · 4 min 30 s”

  5. 05The agents' run

    Each step on the record, with its proof

    Six agents

    The run on the cluster shows each agent's step and its time. All 171 silent meters sent last gasp at 19:41:52–54; the 43 that answer read 236–242 V. Each dark meter is behind the fuse and no answering meter is. The Reply writer drafts 2 self-check messages, and the Dispatch drafter proposes the nearest troubleman, 6 minutes away with a 100 A fuse kit on board, and waits for the dispatcher.

    “Dispatch drafter · nearest truck proposed … Waiting for the dispatcher”

  6. 06Across the road

    The street is dark, but this meter answers at 239.6 V

    Customer

    A customer called at 19:42:35: “Power’s gone. The whole street is dark, I can see it from the window.” The meter answers at 239.6 V. The home is on a transformer fed from a neighboring lateral, which kept its supply. The load fell to zero at 19:41:55, three seconds after the voltage dip from the blown fuse, and the premise history shows two earlier RCD resets here last year. Most likely the RCD tripped again.

    Without the ping, the home would stay dark after the fuse is replaced, and the customer would call again.

  7. 07Why that fuse

    One incident for 171 customers, with the evidence

    Outage tracer

    The incident groups 40 calls: 171 customers off, 3 on the priority register. The Outage tracer lists its reasons: the last gasps from all seven transformers, the seven sharing only one lateral, the 43 meters on the neighboring lateral answering, the bang at the pole, and no incident open on the lateral before the calls. It also shows what it ruled out: the first transformer alone, at 3%, because six other transformers are dark too.

    Below 80% confidence the Outage tracer names the area, not a device. The dispatcher confirms the device.

  8. 0819:47

    Two self-checks sent, the incident confirmed, the crew approved

    Outage desk dispatcher

    The dispatcher sends the self-check to the two homes with power, confirms the incident and approves the truck, with a restoration estimate of 21:30. 169 customers get the restoration update by text and app; a contact center agent phones 2 of the 3 priority customers, and the third asked for text only. At 19:52 the customer across the road replies: “FIXED, the trip switch was down.” The second home with power replies FIXED at 19:55.

    “FIXED, the trip switch was down” · 19:52

  9. 09After the message

    The self-check, then a re-ping 20 minutes later

    Reply writer and Meter pinger

    The message tells the customer their smart meter shows power reaching the home, asks them to check the fuse box (main switch and trip switch first, and not to touch it if it is wet, damaged or hot) and to reply FIXED or STILL OFF. Twenty minutes later the meter is pinged again: load back closes the call with no visit; still off with voltage present brings electrician advice and a call-back; a meter that has gone silent gets a crew job drafted.

    Sent only when the meter answers with voltage, the call has no hazard words and the customer is not on life support.

  10. 10Tonight

    One crew to the fuse, seven truck rolls held

    Troubleman

    The troubleman is on the way to the pole to inspect it and replace the fuse, with the hazard note “Bang reported · check before re-fusing”. Each job on the crew board carries its proof: a ping with 171 off and last gasp, hazard words with the meter on, a meter off alone, a silent meter with its neighbors on. Seven homes whose meter answered with voltage got a self-check message instead of a crew.

    “The meter answered with voltage, so the home has power: a self-check message went instead of a crew.”

Who it’s for

The desk, the contact center and the crew on a night of trouble calls

The same blown fuse, seen by the people who take the calls, decide, drive out and switch the lights back on: what their night looked like, and what it looks like now.

Outage desk dispatcher
Confirms incidents and approves crews
Before
Watches the outage map 16:00–00:00 with 11 crews to send, and builds incidents by hand from the callers' words and pins on a map.
Now
Sees which houses are really dark before anyone is sent, with the likely device and its proof.
Outage desk supervisor
Crew levels, storm escalation, outage minutes
Before
Owns crew levels and storm escalation, approves second crews and estimate changes, and counts each truck that finds the lights on as a truck taken off a real fault.
Now
Sees truck rolls held, calls pinged before a decision and minutes from first call to confirmed outage over 7, 30 or 90 days, and approves each message version.
Contact center agent
Takes calls, phones priority customers
Before
Takes 40 no-power calls in four minutes when a fuse goes, with no way to tell a tripped switch from a blown fuse over the phone.
Now
Phones the priority customers on the incident while 169 restoration updates go by text and app, and can send a crew from any call.
Troubleman
First responder to fuses and wires down
Before
Is sent to single homes where the fault turns out to be inside, when the job that matters is the fuse.
Now
Gets one job to the pole with the device, the evidence and the hazard note, and reports restored on site.
Customer
On a different transformer from the street
Before
Saw the street go dark and phoned in, assuming the home was off with everyone else.
Now
Gets a text saying the meter shows power, resets the trip switch and replies FIXED five minutes after the message.
The agents

Call, grouping, ping, trace, reply and dispatch agents

Each no-power call is read, grouped with its neighbors, pinged and traced by six agents; the dispatcher confirms the outage and sends the crew.

Call reader

Reads each phone summary, app report and text; matches the premise and its meter from the caller ID, account or registered mobile, notes the symptoms in plain words and finds any hazard words.

  • Never downgrades a hazard; a call with a hazard word goes to the dispatcher at once
  • Never contacts the customer itself
Call grouper

Places each call on its transformer, lateral and feeder; opens a cluster when 3 calls share a device within 10 minutes and 400 m, and attaches calls inside an open incident or planned work so the customer is told its estimate.

  • Never closes or merges an incident in the outage system
  • Proposes; the dispatcher confirms
Meter pinger

Pings the callers' meters and each neighbor on the same transformers; records the answer, voltage, load and last gasp. A meter with no answer and no last gasp is silent, and its neighbors are pinged.

  • At most 3 pings per meter in 10 minutes
  • Never connects or disconnects a meter
Outage tracer

Walks the network model upstream from the dark meters to the deepest device they all share and no answering meter shares, weighs the callers' words and the last-gasp times, and gives the likely device with its confidence and evidence.

  • Below 80% confidence it names the area, not a device
  • The dispatcher confirms the device
Reply writer

Drafts the self-check message for a home whose meter answers at 207 V or more, the restoration update with the estimate the dispatcher set, and call-back notes for priority customers; books the re-ping 20 minutes after a self-check.

  • Never sends a self-check to a hazard call or a life-support customer
  • Never invents a restoration estimate
Dispatch drafter

Drafts the crew job for a confirmed incident or a single home with no answer (device, pole, hazard notes and evidence) and proposes the nearest free crew with the right skill and kit.

  • Never dispatches; the dispatcher approves each crew
  • A second crew needs the supervisor
Outage desk dispatcher

Confirms every incident and crew.

Ask in plain words

A trouble call, a home or an incident, explained in plain words

Ask about any call, home or incident in plain words, or say what to change. Each answer points to the ping, the meter events or the network model behind it.

Why are the two homes across the road not part of the outage?

Because their meters answer. At 19:46 the ping found 239.6 V at one and 241.2 V at the other. Both are on a transformer fed from a neighboring lateral, which kept its supply; the homes across the road are behind the blown fuse. At the first home the load fell to zero three seconds after the voltage dip, so the RCD most likely tripped; it has happened there twice before.

Which calls tonight could still waste a truck roll?

Three to watch. One meter is silent with no last gasp and its 6 neighbors are on; a truck is going, but it may be the meter's radio, not the supply. Another meter is on at 238.8 V, with a self-check sent at 19:38 and no reply yet; re-ping at 19:58. A third home is still off with voltage present after the self-check: an electrician is advised, not a crew.

Ping the cluster automatically at the third call

Done. New rule, version 8: when 3 calls cluster on a shared transformer or lateral within 10 minutes, the Meter pinger pings each meter on it without waiting. You still confirm the incident and approve the crew. Hazard calls still go to a crew first. Tonight that would have pinged the neighborhood at 19:44:02, two minutes sooner.

The screens

The outage map before and after the ping, and the crew board

From the working solution, on its sample data. Pick one to see it large.

The outage map after the pingThe neighborhood's 214 homes, dark or green: 38 callers off and 2 on, 171 homes off behind the lateral fuse at 92%, and what the desk does next.
Calls arriving on the map40 no-power calls in 4 minutes, each a ring on the streets, grouped on one lateral, with the hazard call flagged crew first.
Pinging the metersOn-demand pings to the callers and their neighbors on 9 transformers, before anyone is sent.
The agents on the clusterEach agent's step with its time and proof, from 40 calls read to a truck proposed and waiting for the dispatcher.
Confirmed and on the waySelf-checks sent, the incident confirmed, the truck on the way with a 21:30 estimate, and the first customer reply.
Tonight's no-power calls58 calls with what the customer said, the meter's answer and the verdict: network outage, known outage, single home off, power at the home, hazard, priority customer, meter silent.
A call with power at the homeA home across the road: the meter answers at 239.6 V on a different transformer, the premise history shows earlier RCD trips, and the self-check message.
A hazard callA bang and a flash at the pole: hazard words found, and a crew checks the pole before the fuse is replaced, with no self-check.
The grouped incident40 calls into 1 incident: why that fuse, the homes off by transformer, the crew and the customers told.
The crew board11 crews on the evening shift, tonight's jobs with their proof, and the truck rolls held because the meter showed power.
Self-check messagesThe message as the customer sees it, tonight's replies and outcomes, and what happens after the 20-minute re-ping.
Trends30 days: truck rolls held, what the meters said on 4,380 calls, calls pinged before a decision and minutes from first call to confirmed outage.
Desk settingsGrouping, pings, who gets a self-check, hazard words and who decides, each change saved as a new version.
Governance

Hazard rules, approvals and proof behind trouble call management

Each verdict shows its proofEach verdict cites what it rests on (the ping answer with its voltage and time, the last gasp, the path in the network model, the caller's own words), and each crew job on the board carries that proof.
The dispatcher confirms and approvesAgents read, group, ping, trace and draft; they do not dispatch. The dispatcher confirms each incident, approves each crew and sets the restoration estimate; a second crew on one incident or an estimate change over 2 hours needs the supervisor.
Hazards always go to a crewA call with any word on the hazard list (wires down, sparking, bang, flash, smoke, burning smell, tree on the line, shock and more) goes to a crew and not to a self-check. It is a fixed rule that cannot be switched off.
Life-support customers get a personA self-check message is not sent to a life-support customer; a person in the contact center phones them instead.
Meters are read, never switchedThe Meter pinger sends at most 3 pings per meter in 10 minutes and does not connect or disconnect a meter. Customer data stays with the utility.
Who pressed Ping, confirmed and approved, on recordEach agent step and each person's decision is recorded with who, when and the evidence: who pressed Ping, who confirmed the incident, who approved the crew. Customer messages are kept with the call, and each settings change is saved as a new version.
Configuration

Cluster, ping and self-check settings in trouble call management

How calls are grouped, when meters are pinged, who gets a self-check and who decides are settings. Each change is saved as a new version.

SettingDefaultChoose from
Calls that make a cluster3 callsCalls on a shared transformer or lateral inside the window and radius — set with − and +
Window10 minTime between the first and the last call — set with − and +
Radius400 mDistance between calls in a cluster — set with − and +
Ping a clusterOffOff: the dispatcher presses Ping · On: the Meter pinger pings at the third call
Ping every single-home call before a job is draftedOnOn · Off — a crew is drafted only if the meter does not answer
Voltage that counts as power at the home207 V230 V minus 10% — set with − and +
Re-ping after20 minMinutes after the self-check message — set with − and +
Never to a hazard callAlways onFixed rule, cannot be switched off; the hazard word list is versioned (version 7)
Connections

The meter head-end, outage system and network model the desk already runs

Calls and app reportscontact center call summaries, app reports and texts
Smart meter head-endon-demand pings, last-gasp events and meter events
Outage systemopen incidents and the planned work calendar
Network modelfeeders, laterals and transformers, and past incidents by device
Premise history and priority registerearlier calls at the address, life-support and priority customers
Crews and work managementcrew locations, skills, jobs and van stock
What it changes

Truck rolls held and faster confirmed outages in trouble call handling

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
5min
from the first call to a confirmed outage and its likely fuse
Calls only≈ 27 min
With pings≈ 5 min
demo
$1.1M
a year of truck rolls avoided to homes whose meter shows power, on sample inputs
Before pings338 a month
With pings14 a month
target
Every
hazard call goes to a crew, never to a self-check message
each hazard call to a crew
from the hazard words in the call

“demo” = seen in the working solution, on its sample outage-desk data · “target” = the design goal, measured in the live solution · “estimated” = our arithmetic, inputs shown ($1.1M a year rests on sample inputs for a large utility: the truck rolls it sends in a year to homes whose meter shows power, at $300 a roll; the crew-days split is our estimate on the sample's counts) · “estimated” also marks vendor figures (S&C Electric, The Real Cost of a Truck Roll: $250–$500 a dispatch) · “typical” = published figures (E Source, 15 utilities: $9.54 a call; US EIA, Electric Power Annual Table 11.1: 366 minutes in 2023 including major events). Practice described as context: the smartgrid.gov OMS ping and on-demand poll use cases. Names on the screens are sample data.

Questions

AMI outage verification and trouble call system questions

What is trouble call management?

Trouble call management is how an outage desk handles no-power calls: deciding, call by call, whether it is a network outage, a single home, an outage already known or a fault inside the customer's home, and sending a crew only where one is needed. Trouble Call Management does it with six agents that read, group, ping and trace each call, while the dispatcher confirms each incident and approves each crew.

How does AMI outage verification work before a truck rolls?

When calls arrive, the Meter pinger sends an on-demand ping to the callers' smart meters and their neighbors on the same transformers, and reads the answer, voltage, load and last gasp. A meter that sent last gasp and does not answer is off; one that answers with voltage has power at the home; one with no answer and no last gasp is silent, and its neighbors are pinged. In the sample, the ping of 214 meters took 11 seconds: 171 off and 43 on.

How does trouble call software reduce OK-on-arrival truck rolls?

Each single-home call is pinged before a job is drafted, and a crew is drafted only if the meter does not answer. A home whose meter answers at 207 V or more, with no hazard words and not on life support, gets a self-check message instead. In the sample's last 30 days, 312 truck rolls were held and jobs where the crew found power on at the meter fell from 338 a month to 14.

Does it ever send a self-check message to a hazard call?

No. A call with any word on the hazard list (wires down, sparking, bang, flash, smoke, burning smell, tree on the line and more) goes to a crew. It is a fixed rule that cannot be switched off; in the sample's last 30 days, 41 hazard calls went to a crew and none to a self-check.

How does it find the device behind an outage?

The Outage tracer walks the network model upstream from the dark meters to the deepest device they all share and no answering meter shares, and weighs the callers' words and the last-gasp times. It gives the likely device with its confidence and evidence, and below 80% it names the area, not a device.

What happens to life-support and priority customers?

They are not handled by a self-check message. A person in the contact center phones them, and the Reply writer drafts a call-back note for each. On the sample incident, 2 of the 3 priority customers were phoned (the third asked for text only), while 169 customers got the restoration update by text and app.

Can the agents send a crew or switch a meter on their own?

No. The agents propose and draft; they do not dispatch, close or merge an outage-system incident, or connect or disconnect a meter. The dispatcher confirms each incident, approves each crew and sets the restoration estimate, and the supervisor approves a second crew or an estimate change over 2 hours.

What does an outage desk share to set up trouble call management?

Your call scripts, hazard words, self-check rules and a sample of past no-power calls, meter events and incidents. The Agentic Solution Engine builds and deploys it from those requirements and documents, and it goes live once each quality gate has passed. We will walk you through it on your own calls first.

Ping the meters behind
your own no-power calls.

We'll run Trouble Call Management on a sample of your own no-power calls, meter events and outage incidents.