Review Utility Restoration Service With a Scorecard

Utility restoration customers compare branches constantly, and when a customer tells you one branch treats them well while another leaves them stranded, a blanket apology does not fix anything. The customer is not asking you to feel bad. They are asking you to explain why two branches on the same account behave so differently, and what you plan to do about it. An Outside Account Manager who wants to keep that account has to turn the complaint into a real review, built on incident by incident facts rather than a promise to do better.

Why the Conversation Goes Wrong

Storm and outage work moves crews across your service area fast, so small differences in response time show up right away, and customers notice. When a customer opens with a complaint like uneven service, most reps respond with an apology and a general promise, something like we will do better going forward. That answer treats a complaint about operations as if it were a complaint about mood. The customer already has evidence, dates, wait times, a crew that got no update from your team. A vague apology tells them you have not looked at any of it, and it invites them to turn one bad incident into a judgment about the whole program. The real cause might be a single branch that lost site access after a road closure, or one dispatcher who missed a call. Until you separate the specific incidents from the general feeling, you cannot fix either one.

How to Prepare Before You Call

Pull the incident record yourself before you talk to the customer. Choose three or more events the customer is likely to raise. For each one, write down the branch that handled it, the time the customer requested service, whether delivery happened on time, any access issue the crew ran into, what the service record shows, and who from your team contacted the customer and when. Put this on one page with only facts you can verify against dispatch logs and delivery records, not commentary or excuses.

Call the branch manager for the underperforming branch before you call the customer. Ask what happened, and ask them to bring their own dispatch record to the customer meeting in case the customer wants to see it directly. Decide in advance what you can commit to, an owner for each gap and a date to check progress, because a customer who already feels ignored will not accept another vague promise. If this account has already been through a service recovery conversation, apply the same discipline you would use to Lead an Account Recovery Review After Paving Downtimewhere the fix depended on naming an owner and a date rather than offering a general apology.

What to Say When the Customer Pushes Back

Here is how this can go. Rory, a utility operations lead, opens with the complaint most account managers dread. Rory says, "Your north branch kept us waiting on three separate requests while your south branch answered every call the same day. Give me one reason to keep this program instead of moving it to another supplier."

Dana, the account manager, does not defend the north branch and does not apologize in general terms either. Dana says, "I want to go through the actual requests with you rather than guess at what happened. Can we compare request times, approved delivery points, the access conditions each crew found on site, and the updates the branch gave your team, for each of the three events."

Rory pulls up dates from an outage log, and one event turns out to involve a site that moved after a road closure the branch was never told about. Dana says, "I will bring the branch manager onto that call so you hear the dispatch record directly instead of secondhand. We will name an owner for each gap you found, and we will pick a date before your next readiness meeting to check that it actually improved."

That exchange does not erase what the customer's crews went through. It moves the conversation from a broad accusation to a shared list of facts, and from a shared list of facts to an owner and a date. That is the only version of this conversation that survives contact with a skeptical customer.

Mistakes That Undo a Good Scorecard

A few habits will wreck this review even when you have good data behind you.

1. Leading with an apology before you have looked at the record. It signals that you already agree the customer is right about everything, before you actually know what happened.
2. Promising a system wide fix for a problem that was local to one branch or one dispatcher. That promise sounds good in the room and falls apart the next time only that branch has an issue.
3. Naming a problem without naming a person who owns fixing it. If nobody at the branch is accountable, the same gap shows up again in three months.
4. Closing the call without a specific date to check progress. A customer who hears we will monitor this closely has heard that line before and will not believe it a second time.

Each of these trades a hard conversation now for a harder one later, once the customer decides the review itself was empty.

How to Practice and Score This Conversation

This conversation is hard to get right the first time you try it live, because the customer's frustration is real and your instinct is to soothe it rather than investigate it. Practice it before the account meeting happens. Pick three real past service events on the account, build the one page record described above, and run the conversation with someone playing a customer who opens with a broad complaint instead of a specific one.

A manager watching that practice run should score three things. Did the rep acknowledge the complaint without dismissing it or accepting blame for something not yet verified? Did the rep ask permission to review the record together instead of arguing from memory? Did the rep close with a named owner and a real date, not a general commitment to improve? A rep who hits all three under pressure from a frustrated customer will hold the account. A rep who skips straight to reassurance usually loses ground even when the underlying service was actually fine.

DealSpeak's Equipment Rental practice conversations let you run this exact scenario against an AI customer who pushes back the way Rory does, and a scorecard shows you where your response held up and where it slipped into vague reassurance. The same discipline applies to other high pressure equipment requests, like when you Move a Pipe Leak Equipment Request Forward Safely for a customer anxious about an active leak rather than a service history complaint.

The Review Is the Relationship

The scorecard will not undo what the customer's crews went through during a bad restoration event. What it does is show them that you looked at the actual record instead of managing their mood, and that someone specific is now responsible for the gap they found. That is what keeps a utility account through the next storm, not the apology you gave after the last one.