Coaching clear delivery of a required disclosure
Help a new agent use approved wording at a pace customers can understand.
Required wording loses its value the moment a new agent reads it too fast for a caller to follow. The words might be exactly what compliance approved, but if the caller has to ask what they just heard, the disclosure did not do its job. As a quality manager, your job is not to rewrite approved language. It is to coach the behaviors around that language, the pace, the pauses, and the moment where the agent lets the caller catch up.
Why this conversation goes wrong
Most agents rush a required disclosure for one of two reasons. Either they are worried about handle time and want to get past the awkward part quickly, or they are afraid of stumbling over the exact wording and speed up to get it over with. Both reasons make sense from the agent's seat. Neither one serves the caller.
Coaching on this topic goes wrong when a manager treats it as a compliance lecture instead of a delivery problem. If you open with warnings about regulatory risk, the agent hears blame and gets defensive. If you suggest changing the wording to make it easier to say, you have just created a compliance problem where none existed. The agent also tends to hear "slow down" as "take longer on every call," which triggers the handle time worry all over again. Your coaching has to separate the fixed part, the script, from the variable part, the pace and the pause, or the agent will keep treating the whole exchange as one immovable thing.
How to prepare
Before you sit down with the agent, confirm the current version of the disclosure with compliance. Scripts get updated, and coaching from an outdated version wastes the conversation and undermines your credibility. Pull the recording you plan to use and find the exact moment where the caller asks for clarification or repeats the question back in confusion. You want a specific clip, not a general impression from a shift review.
Decide in advance what you are asking the agent to change. It is pace and a pause at the end of the disclosure, nothing else. Have handle time numbers on hand if the agent raises them, but plan to acknowledge the pressure without accepting it as a reason to skip the pause. A two second pause rarely moves handle time in any meaningful way, and you should be ready to say that plainly rather than let the conversation drift into a debate about metrics.
What to say
Priya pulled up the recording and said, "I want to listen to this together. It is your call from Tuesday, right after the account disclosure." Marcus said, "Yeah, I know I went fast through that part. I had calls holding and did not want to run long." Priya said, "The wording itself is fine, every word matches what compliance approved. Listen to what happens right after you finish it." They played the next few seconds, where the caller asked, "Wait, what does that mean for my account?" Priya said, "That question is not about the content. It is about pace. You gave her no room to process it before you moved on. Let us try the same disclosure again, same words, with a short pause at the end."
Marcus read the disclosure again, slower this time, and paused before continuing. Priya said, "That took you maybe two extra seconds, and it gave her a chance to respond instead of guessing. What will remind you to pause like that on your next calls?" Marcus said, "I could mark a spot on the script where I stop." Priya said, "Do that. Mark it now, and we will check a few of your calls this week to see how it lands."
Notice what did not happen in that exchange. Priya never questioned the wording, never told Marcus he did not care about compliance, and never let the handle time comment turn into a longer argument about staffing. She named the specific moment, played it back, and asked for one small, repeatable change.
Mistakes to avoid
A few habits undercut this kind of coaching even when the manager means well.
-
Rewriting the disclosure to sound more natural. If a script feels clunky, that is a note for compliance, not something to fix in a coaching session. Changing even a word or two on your own creates risk you do not want to own.
-
Framing the conversation around regulatory consequences instead of the specific call. Abstract warnings about audits or fines do not change behavior nearly as well as a caller's actual voice asking what they just heard.
-
Letting handle time pressure go unaddressed. If you skip past the agent's concern, they will assume you do not take it seriously, and the old habit will return within a week. Say directly that a short pause costs almost nothing on the clock.
-
Piling on other feedback in the same session. Stick to delivery. If you also want to cover call notes or transfer etiquette, do that separately so the disclosure coaching does not get lost.
How to practice and score it
Ask the agent to mark the pause point directly on the approved script, then roleplay it with you playing a confused caller who asks the same kind of question heard in the recording. Watch for two things, whether the pace changes and whether the agent actually stops after the pause instead of rushing through it out of habit. A single successful roleplay does not mean the behavior has stuck, so review five of the agent's subsequent calls specifically for delivery, not content, and note whether the pause shows up without prompting.
This is also a good candidate for rehearsal outside of live calls, since the agent can run the same disclosure against an AI counterpart that plays a range of confused or impatient callers before ever testing it on a real customer. DealSpeak is built for exactly this kind of rehearsal, and the Contact Centers practice conversations hub has more scenarios built around the situations quality teams coach most often. If the same call later escalates and you need to coach how the agent documents what happened, the piece on Coaching escalation documentation after a recovery covers that follow on skill. And if the caller's tone gets sharp during the disclosure itself, Coach escalation tone without dismissing a difficult caller walks through that adjacent problem.
Score the behavior, not the script. Did the agent use the approved wording, did the pace allow the caller to follow along, and did a pause appear at the end. Those three questions give you a consistent, repeatable way to check progress without ever asking the agent to change a single approved word.
Practice these next
How a quality manager can discuss a difficult call when a supervisor questions the coaching value of a score.
A quality manager conversation that connects case notes to continuity after a successful service recovery.
A quality manager guide for supporting helpful agents who gave customers information outside the approved update.
Help agents organize a difficult conversation through signposts, checks, and a clear next action.
Use a resolved call to show why case notes and a recorded owner protect the next interaction.
Use a recorded interaction to help an agent explain the purpose of a hold and return with a useful update.