Coach an agent through unhelpful silence on a call
Use a call recording to replace unexplained silence with clear updates and purposeful checking.
Silence on a call feels harmless to the agent doing it. They are reading a screen, checking a system, or waiting on a page to load. To the customer on the other end, that same silence sounds like the call dropped, the agent gave up, or something is wrong that nobody wants to explain. Coaching this well means fixing the habit without turning the agent into someone who narrates every click.
Why this conversation goes wrong
Most coaching on silence fails because the manager treats it as a discipline problem instead of a skill gap. The agent was not being rude. They were concentrating, and concentrating on a screen while a customer waits is a normal, common failure mode in a contact center. If the manager opens with "you went quiet for eighteen seconds and that is unacceptable," the agent gets defensive, and defensiveness blocks learning. The agent will explain what they were doing, the manager will half listen, and the conversation ends with a vague promise to "communicate more," which changes nothing on the next call.
The other common failure is overcorrection. A manager hears one bad pause and tells the agent to narrate everything, every keystroke, every screen change. That produces agents who talk over themselves, sound robotic, and annoy customers a different way. The goal is not more talking. It is talking at the right moment, once, with the right amount of information.
How to prepare
Pull the actual recording before the conversation. Do not rely on a summary or a score from a quality form. You need the exact moment, the exact number of seconds, and the exact words the customer used right before the silence started. That specificity matters because it turns the coaching from an opinion into an observation the agent cannot argue with.
Pick one pause, not every pause in the call. If the recording has three or four gaps, choose the one that follows a direct question from the customer, since that is where silence does the most damage to trust. Write down what the agent was actually doing during that gap if you know it, and if you do not know it, plan to ask rather than guess.
Also decide in advance what a good update sounds like for this specific contact type. A shipment lookup needs a different phrase than a billing dispute or a technical troubleshooting step. Walking in with a real example ready means you can offer it if the agent gets stuck, instead of leaving them to invent language on the spot.
What to say
Start by playing the moment back and asking the agent to describe it in their own words, not by accusing them of going silent.
"There are eighteen seconds with no response after the customer asks about the shipment," says quality manager Priya. Agent Marcus replies, "I was pulling up the order screen and checking the tracking history." Priya asks, "What did the customer hear on their end while you did that?" Marcus pauses, then says, "Nothing. I had my head down looking at the screen." Priya says, "Right, and eighteen seconds of nothing after a direct question makes most people wonder if the call dropped. Try this line, I am checking the latest shipment status right now, give me just a moment. What would you say if the lookup takes longer than expected?" Marcus answers, "I could say I am still confirming the details and let them know what I will check next." Priya asks him to say both lines out loud, once as if the lookup is quick, once as if it drags on.
Notice what that exchange does. It asks before it tells. It gets the agent to state what the customer experienced, which is the insight that actually changes behavior, since most agents have never thought about the call from the customer's side of the silence. Then it hands the agent a short, specific phrase rather than a vague instruction to communicate better. And it closes with a rehearsal, out loud, because agents who only hear the advice rarely produce it under pressure on a real call.
Mistakes to avoid
Do not ask the agent to narrate every action. If they say "I am opening your account now" and then "I am clicking into billing" and then "I am scrolling down," the customer will find that more exhausting than the silence was. One update at the start of a pause and one check if the pause runs long is enough for almost any contact type.
Do not skip the question of what the customer could reasonably know at that moment. Managers sometimes jump straight to giving the agent a script, and the agent recites it without understanding why it matters. Asking the agent to state what the customer heard, or did not hear, builds the judgment they need to apply this on calls you never review.
Do not coach every silence in the same call. Pick one, work it fully, and let the agent leave with one clear commitment. Piling on three or four moments at once dilutes the lesson and the agent will remember none of them.
Do not let the agent give you a generic promise like "I will talk more." Push for the actual words they will use, and have them say those words out loud before the coaching session ends. A commitment that has never left the agent's mouth in that room rarely survives a real customer on the line.
How to practice and score it
Roleplay the exact scenario before you move on, with you playing the customer and asking the same question that triggered the original silence. Score three things separately. First, did the agent give an update before the gap ran long. Second, did the update match what the customer actually needed to hear, rather than a generic filler phrase. Third, did the agent offer a second check if you, as the customer, stayed on the line without responding.
Write the coaching record with the specific pause you reviewed, the update the agent committed to, and the follow up check they agreed to use. Then queue up a later call from that same agent and listen for that specific behavior, not for silence in general. If the agent used a natural update in a similar moment, the coaching worked. If they went quiet again, you know the phrase did not stick and needs another round of rehearsal, maybe with a different contact type this time.
This is also where a practice tool helps, since an agent can rehearse the update and the check against an AI counterpart as many times as needed before a real customer ever hears it, and DealSpeak sets up exactly that kind of rehearsal. For related work on how agents wrap up calls clearly, see Coach clear summaries before an agent ends a calland for another moment where agents go quiet on the wrong details, see Coach an agent to explain a transfer with ownership.
Closing thought
Silence is not a character flaw. It is a habit built from focusing on the task instead of the person waiting on the other end of it. Fix it with one clear observation, one rehearsed phrase, and one follow up listen, and most agents carry the change into their next call. If you want more coaching approaches built around real call moments, DealSpeak's Contact Centers practice conversations cover this kind of scenario alongside the other habits that shape how a call actually feels to the customer.
Practice these next
Help agents organize a difficult conversation through signposts, checks, and a clear next action.
Use a recorded interaction to help an agent explain the purpose of a hold and return with a useful update.
Turn an interruption pattern into a specific listening practice that works within a busy contact center.
Improve issue discovery by identifying the question that would have changed the agent’s next action.
Help agents confirm the next action so customers leave a contact with an accurate understanding.
A quality manager conversation that uses a call record to reinforce identity checks with respect.