Coaching an Unverified Outage Estimate

A customer stuck without service does not want a script read at them. They want a real answer, and a tense agent will often give one, even when the real answer is not in front of them. An agent who quotes a restoration time that never came from the approved update has usually done it out of genuine care for the customer, not carelessness. Coaching this well means protecting that instinct while fixing the habit that put a wrong number in a customer's ear.

Why This Conversation Goes Wrong

Most coaching on this topic fails because the manager treats it as a compliance problem instead of an information problem. They tell the agent to stop guessing, the agent nods, and the same thing happens on the next call, because nobody addressed why the agent guessed in the first place. Usually the agent had a knowledge card open on their screen with a time on it, and that time looked official. The agent was not freelancing. They were reading a source that was already stale.

A second reason this goes wrong is that managers focus only on the agent and skip the content defect. If the knowledge card still shows the outdated estimate after the coaching session ends, the next agent who opens it will make the exact same call. Coaching the person without fixing the source guarantees a repeat.

A third reason is tone. If the manager treats an honest, customer focused mistake as if it were dishonesty, the agent gets defensive, and defensive agents stop giving you the details you need to find the real cause. You need the agent to tell you exactly what they saw on their screen at the moment of the call, and that only happens if the conversation feels safe.

How To Prepare

Before you sit down with the agent, pull the call recording and find the exact timestamp where the estimate was given. Then pull the approved update that was live at that same timestamp, not the current one. Field operations often revises restoration times, and comparing the agent's answer against today's update instead of the one that existed during the call will make an accurate agent look wrong and a wrong agent look accurate.

Next, check what knowledge source the agent actually had open. Ask your knowledge team for the version history of that card. You are looking for a gap between when the update changed and when the card was corrected. If that gap is measured in hours and the call happened inside it, the agent was working from bad information through no fault of their own.

Separate the two threads before the conversation even starts. One thread is coaching, how should the agent handle a customer pressing for a number when the approved update has not changed. The other thread is a content fix, get the stale card corrected or pulled. Walking in with both threads already identified keeps the conversation focused and keeps you from blaming the agent for a documentation failure.

What To Say

Open by naming the specific moment rather than the general behavior. Suri starts the conversation this way. "At two eighteen, you gave the customer a restoration time that was not in the approved update. Walk me through where that number came from." Cole answers honestly. "The customer kept pushing for a number, and the time I gave matched what my knowledge card showed. I thought it was current."

Suri does not treat this as a lie. "Field operations updated the estimate after your card was published, so you were reading a source that had already gone stale. That is on the knowledge team, not on you. But I want to work through what you say next time a customer pushes for a number before you have confirmed the current update." Cole thinks about it. "I could tell them I am checking the latest confirmed information right now, instead of giving them a time I have not verified."

Suri confirms the plan and closes the loop on the content issue in the same conversation. "That is exactly right. Say that, then go check, then call them back with the real number if you cannot get it in the moment. I am also flagging your knowledge card today so the next agent does not hit the same wall you did." That last line matters. It tells Cole the system is being fixed, not just his behavior.

Mistakes To Avoid

Do not let the coaching stop at telling the agent to stick to the script. That instruction ignores the real problem, which is a customer who will not accept silence and an agent who has nothing else to offer. Give the agent an actual phrase to use, something like confirming they are checking the current update, so they have a real alternative instead of a rule with no substitute behavior.

Do not skip the correction to the knowledge card. If you coach the agent and never touch the source document, you have fixed one person and left a trap for everyone else who opens that card. Treat the card fix as part of the coaching session, not a separate task you might get to later.

Do not compare the agent's answer against the update as it stands today. Always compare against the update that was live at the time of the call. Getting this backward turns an accurate, well intentioned agent into someone who looks like they broke a rule.

Do not make the conversation about trust when the actual issue is a stale document. An agent who reads from a bad source is not the same as an agent who invents numbers to get a customer off the phone. Treat those two situations differently, because the coaching each one needs is different.

How To Practice And Score It

Set up a roleplay where the customer character presses hard for a promised time and refuses to accept a vague answer. Give the practicing agent an approved update that intentionally lags behind a fictional field operations change, so the temptation to reach for outdated memory is built into the scenario. Score three things. First, did the agent hold to the approved update instead of quoting a number from memory or an old card. Second, did the agent offer the customer a real next step, such as confirming they are checking the current source, rather than only refusing to answer. Third, did the agent flag the discrepancy afterward so someone corrects the source document.

This is the kind of scenario DealSpeak practice conversations are built for, since the agent needs to handle a pushing customer in real time and you need a consistent way to score whether they used the current source. If you run quality calibration across a team, the same discipline applies to outage updates as it does in Calibrating Quality for an Outsourced Sales Teamwhere the score has to reflect the actual source used, not just the tone of the call. You can find more scenarios built around this kind of pressure in Contact Centers practice conversationsincluding cases like Coaching an approved accessibility support option where the agent again has to choose between what feels helpful and what is actually approved.

The Point Of This Coaching

An agent who reaches for an outdated number is usually trying to help, not cutting corners. Coach the behavior you want next time, fix the document that misled them, and you end up with an agent who handles pressure better and a knowledge base that stops setting the next person up for the same mistake.