Chapter 1: Your Team Sounds Like You

A supervisor named Dana ran a twelve person billing team at a regional utility. Her CSAT sat at 74 percent top box against a company target of 85. She had done the things you are supposed to do. She had rewritten the call opening. She had added an empathy requirement to the scorecard. She had held a team meeting about the importance of the customer experience, complete with a slide that said "we are the voice of the company."

Six weeks later the score was 75.

What finally moved it was not a script. It was a recording of Dana's own Monday huddle, which she made because a peer dared her to, and which she listened to alone in her car because she did not want anyone else to hear it first.

Here is roughly what it sounded like. Two minutes of numbers. Adherence was down. AHT was up eleven seconds. Then a run through of a policy change, read directly off the email she had been forwarded, in the voice you use to read something you did not write and do not like. Then a short paragraph about how she knew it was a lot, and the team was doing great, delivered at the speed of a person who has another meeting at nine. Then "any questions," followed by four seconds of silence, followed by "okay, good calls today."

Dana listened to it twice. The second time she heard something she had not caught. She had used the phrase "I know it is a lot" the same way her agents used "I apologize for the inconvenience." Same rhythm. Same placement. Same complete absence of anything behind it.

Her team did not sound flat because they were flat people. They sounded flat because they were doing an accurate impression of the last human who spoke to them about the work.

The transfer effect

Tone travels downhill. So does urgency, cynicism, curiosity, and care. It travels faster than any policy you publish and it survives longer than any initiative you launch.

There is a reason for this that has nothing to do with mysticism. An agent takes forty to seventy interactions a day. They have almost no other model for what this work sounds like when it is done by someone with authority. Their exposure to leadership language is concentrated into a few short encounters: a huddle, a coaching session, a chat message when the queue spikes, an email about a metric. Those encounters are dense. They carry more signal per minute than anything else in the agent's day, and agents absorb them the way anybody absorbs the dominant voice in a room.

So when a leader says "just get through it today," the team gets through it. When a leader introduces a policy change with a shrug and a sentence that begins "apparently corporate decided," every agent on that team now has permission to explain the policy to a customer with the same shrug. The customer cannot see the shrug. They can hear it perfectly.

There is a harder version of this. If you are impatient with your agents in a coaching session, they will be impatient with a customer who does not understand the first explanation. If you interrupt them to get to the point, they will interrupt a customer to get to the point. If you treat their questions as delays, they will treat customer questions as delays. Agents do not learn service behavior from the training deck. They learn it from how it feels to be on the other side of you.

This is not a guilt exercise. It is leverage. It means you have a channel into every call on your floor that does not require you to be on the call.

The three postures agents can hear

Over a long enough stretch, most service leaders settle into one of three postures. Agents can identify them within about two weeks of joining a team, and customers can hear the results.

**The enforcer.** This leader manages by scorecard and consequence. Their coaching consists of the delta between the agent's number and the target. Their huddles are compliance briefings. Their language is heavy on "you need to" and light on "let me show you." Enforcers are not lazy. Many of them are the hardest working people in the building. But their teams learn one lesson very quickly: the goal is to avoid getting caught, not to serve well.

What it sounds like on a call: technically compliant, emotionally empty. Every required element present, in order, with nothing added. Agents on enforcer teams read the empathy statement because it is on the form. They do not ask the second question, because the second question is not on the form, and nothing they have ever been rewarded for came from the second question.

**The absentee.** This leader is buried. They are in meetings, in escalations, in reports, in projects that were assigned to them because they are reliable. Their team is largely unmanaged, which some agents love for about four months. Absentee leaders are usually well liked and quietly resented, because being liked is not the same as being developed.

What it sounds like on a call: wildly inconsistent. Your three strongest agents are excellent because they came that way. Your bottom four have never been corrected on anything, and by the time somebody notices, the habits are two years old and the conversation feels like an ambush. Absentee teams have the widest performance spread of any team type, and the widest spread produces the most unpredictable customer experience.

**The coach.** This leader spends the majority of their agent facing time on behavior rather than on numbers. They listen to calls with agents instead of about agents. They give one correction at a time. They ask more questions than they answer. They defend the customer's experience and the agent's dignity in the same breath, which is harder than it sounds and is most of the job.

What it sounds like on a call: recognizable. You can hear the team's shared standard in different personalities. This is the tell. On a coached team, agents do not sound identical, they sound aligned. There is a family resemblance in how they open, how they acknowledge, how they close, and enormous variety in everything else.

Nobody is one posture permanently. Most leaders drift toward the enforcer during a bad metrics month and toward the absentee during a busy project quarter. The point is not purity. The point is knowing which one you have been for the last thirty days, because your team already knows.

Why "just follow the script" produces exactly what you hate

Every leader who has ever complained that their team sounds robotic has, at some point, told their team to follow the script more closely.

Both things are true at the same time, and that is the trap.

A script is a floor. It exists so that the worst call of the day still contains the disclosure, the verification, the required offer, and the accurate information. That is a real function and it deserves respect. Compliance language is not the enemy of good service. In regulated industries it is the price of being allowed to have the conversation at all.

The failure is treating the floor as the ceiling. When the only feedback an agent ever receives is about script adherence, the rational response is to deliver the script and nothing else. Adding warmth carries risk. Warmth takes seconds, and seconds show up in AHT. Warmth is unscored, and unscored behavior is unprotected behavior. An agent who improvises and gets dinged learns in one session that the safe move is the flat move.

So the flat delivery your team gives you is not defiance. It is compliance, executed exactly as incentivized.

The fix is not fewer scripts. It is being specific about which parts are fixed and which parts are theirs. Say it plainly, out loud, in a huddle: "These four elements are required, word for word, because legal requires them. Everything else is yours. I will never coach you for making the rest sound like a person." Then prove it by praising an agent, in front of the team, for something that was not on the form.

There is a second half to this. If you are going to tell an agent that the delivery is theirs, you have to give them something to deliver. Most agents who sound mundane have never been taught the mechanics of vocal variety, and telling them to "sound more engaged" is roughly as useful as telling someone to be taller. Chapter 14 handles the mechanics. For now, note the sequence: permission first, technique second. Technique without permission just produces a more elaborate script.

The audit: score yourself on your own form

This is the exercise that changed Dana's team, and it costs nothing.

**Step one.** Record your next team huddle or your next one on one. Phone voice memo is fine. Tell the team you are doing it and why. That transparency is part of the exercise.

**Step two.** Wait twenty four hours. You need the distance. Listening the same day, you will hear what you meant. Listening the next day, you will hear what you said.

**Step three.** Pull out your team's QA scorecard. The actual one. Score yourself on it as if you were the agent and your team were the customer.

Most scorecards have some version of these categories, and each one translates cleanly:

- **Opening.** Did you greet the team like people, or did you start with a number? Did anyone know where the next fifteen minutes was going? - **Acknowledgment and empathy.** When someone raised a problem, did you label it and validate it, or did you explain why it was not as bad as they thought? Count how many times you said a version of "I know, but." - **Ownership language.** Count your uses of "they," "corporate," "the system," and "apparently." Then count your uses of "I will" and "here is what I am going to do about it." - **Clarity of the answer.** If an agent had to repeat your policy explanation to a customer an hour later, could they? Say the explanation out loud. If it takes you more than three sentences, your team will take five, and the customer will take none of it. - **Expectation setting.** Did you commit to anything with a date attached? Did you close a loop you opened last week? - **The close.** Did you recap? Did you ask the completeness question, the one that goes "what else do you need from me before you get on the floor"? Or did you end with "any questions" and four seconds of silence, which is not a question, it is a door closing? - **Tone and energy.** Play thirty seconds with the volume low enough that you cannot make out the words. What is the emotional read? That is what your team gets.

**Step four.** Write down your two lowest categories. Only two. Same rule you will apply to your agents in Chapter 21: one behavior at a time, two at the absolute most.

**Step five, the one most leaders skip.** Tell your team what you found and what you are changing. Not as a confession, as a demonstration. "I listened to last week's huddle. I open every one of these with a number instead of with you. Starting Monday I am opening with a save from the week. Hold me to it."

That sentence does more for engagement than any activity in Part VI, because it does the thing you are about to ask of them. It accepts feedback without defending, names one behavior, and commits to a change with a date on it. You will have taught the entire coaching model in forty seconds without using the word coaching.

What happened to Dana

She changed two things. She stopped opening the huddle with adherence, and she started reading one customer verbatim out loud every Monday, good or bad, with the agent's name attached when it was good. And when a policy came down that she disagreed with, she stopped saying "apparently corporate decided" and started saying "here is the change, here is the reason as I understand it, here is what I am asking upward about it, and here is exactly how I want you to explain it to a customer."

Her CSAT did not jump. It moved from 74 to 79 over the next quarter, then to 86 over the two quarters after that, alongside the work in Part II of this book. What moved faster was voluntary participation. Agents started sending her calls they were proud of, unprompted. That is the leading indicator. Discretionary effort shows up before the score does, every time.

The Takeaway

Your agents have limited exposure to what this work sounds like when a person with authority does it, so the little they get from you becomes the template. Tone, ownership, patience, and cynicism all transfer downhill faster than policy. The flat delivery you hear on your floor is usually an accurate impression of the last leadership conversation those agents had, and the fastest available fix is not on the agent's scorecard. It is on yours.

Run It This Week

Record one huddle or one on one. Wait a day. Score yourself on your own team's QA form, using the seven translations above. Identify your two weakest categories, change one behavior, and tell your team out loud what you found and what you are changing. Set a date. Ask them to hold you to it.

The One Question

If your team is doing an impression of you, what part of the impression would you least want a customer to hear?