Customer Service Management Tips | Blog | C2Perform

How to Coach an Agent in a Call Center | C2Perform

Written by Lee Waters | Nov 19, 2026, 10:17:36 AM

Knowing how to coach an agent in a call center starts with a clear purpose: help an employee understand a specific behavior, practice a better approach, and use it on the job. A useful coaching conversation is not a lecture or a score review. It is a repeatable cycle that combines evidence, listening, practice, and follow-up while taking the employee’s wider work context into account.

Explore call center coaching solutions

What should you do before a coaching conversation?

Prepare one focused objective, verify the evidence, check the relevant standard, and decide what the agent should be able to demonstrate by the end of the session.

Preparation makes coaching fairer and more useful. Start with a specific interaction, task, or repeated behavior. Avoid opening with a broad judgment such as “the agent needs to improve.” Instead, identify what happened, where it happened, and what desired behavior would look like in the same situation.

Before the meeting, work through these preparation steps:

  1. Choose the coaching objective. Keep it narrow enough to practice. For example, focus on confirming that a caller understands the next step rather than trying to improve every part of a conversation at once.
  2. Check the source material. Review the interaction, applicable quality criteria, and current process guidance. Confirm that the example has not been taken out of context and that the standard was in effect at the time.
  3. Look for patterns, not assumptions. Consider whether similar observations appear in other work. A single unusual interaction may call for a question or clarification, not a sweeping conclusion about an employee’s ability or effort.
  4. Check for barriers. Ask whether the agent had access to the right information, tools, authority, and time to follow the expected process. A system or policy issue should not be mislabeled as an individual skill gap.
  5. Plan a practice activity. Select a role-play, short response exercise, or guided review that lets the agent try the skill rather than only hear about it.
  6. Prepare questions. Use open prompts that invite the agent to explain what they noticed and what they would try next.

For instance, a supervisor preparing to discuss call closing might note the exact moment when the agent shared a next step but did not check for understanding. The supervisor can then identify the applicable standard and prepare a brief practice scenario. This is more productive than bringing several unrelated scorecard marks and asking the agent to “be more thorough.”

Consider the whole employee, not only quality feedback. Attendance, career development, current performance plans, and any relevant support needs can shape how a conversation should be handled. Keep sensitive information within appropriate organizational processes. When records disagree, pause and resolve the discrepancy before using it as the basis for coaching. A consistent routine for frontline leaders can help supervisors prepare without turning every session into an administrative exercise.

How can you open the session and build trust?

Explain why you are meeting, invite the agent’s account first, and discuss observable behavior and impact without assigning blame.

Set a calm, clear tone. Tell the agent what you want to work on, which example you will review, and why the behavior matters to the customer, the team, or the work. Then make room for the agent’s perspective before offering your interpretation. This helps reveal missing context and signals that the purpose is development, not a surprise verdict.

A practical opening might sound like this: “I’d like us to review how the next step was explained on this call. The process was followed up to that point; I want to look at how we confirmed the customer understood what would happen next. How did the close feel to you?” The question is direct, but it does not label the agent or presume intent.

Use a simple conversation sequence:

  • Ask for self-assessment. Invite the agent to describe what went well and what felt difficult.
  • Listen for context. Let the employee finish, then ask a clarifying question before moving to feedback.
  • Describe the observation. Use neutral language about what was said or done and when.
  • Explain the effect. Connect the behavior to a clear service or process outcome, without exaggerating the impact.
  • Agree on a next step. Ask what the agent will try and what support would make the action easier.

Separate intent from observable action. “You did not confirm the customer understood the next step” describes behavior. “You did not care whether the customer understood” guesses at motive. The first gives the agent something concrete to examine; the second tends to prompt defensiveness and does not define what to practice.

Trust does not mean avoiding difficult feedback. It means being accurate, consistent, and respectful. If the agent disagrees, ask what they see differently and review the interaction and standard together. If the evidence does not support your original interpretation, correct it. If the source is incomplete, gather what is missing before reaching a conclusion. A fair process strengthens the credibility of future feedback.

How do you turn feedback into practice?

Explain the gap, show or describe the expected behavior, let the agent rehearse it, and give feedback on the practice attempt.

Discussion alone may not give an agent enough opportunity to build a new response. Practice makes the expectation tangible. Keep the exercise close to the work, but limit it to the behavior selected for the session. The goal is a useful attempt and a clear next action, not a perfect performance in a meeting room.

Try this coaching loop:

  1. Describe the target behavior. State what the agent should do and when. For example: summarize the agreed next step, then ask the customer to confirm that it is clear.
  2. Model it briefly. Demonstrate the behavior or share a concise example. Keep it natural so the agent can adapt it to their own voice.
  3. Let the agent try. Present a short scenario and ask the agent to respond as they would during a real interaction.
  4. Give focused feedback. Name one thing that worked and one adjustment that would make the behavior clearer or more complete.
  5. Repeat or vary the scenario. Give the agent another opportunity, perhaps with a small change in customer context, to see whether they can apply the skill rather than repeat a memorized phrase.

Suppose the observation concerns a customer who is unsure which document to provide. The supervisor can play the customer, ask the agent to explain the requirement, and then introduce a follow-up question. After the attempt, discuss whether the explanation was accurate, plain, and complete. If the agent is unsure of the procedure, stop the role-play and check the approved guidance; do not reinforce a guess just to keep the exercise moving.

Choose the practice format to match the need. A role-play is useful for phrasing, listening, or call control. A knowledge review can help when the issue is understanding a policy or product detail. A screen walkthrough may fit a task that involves navigating a system. For an experienced agent who understands the skill but applies it inconsistently, ask them to talk through their decision points and rehearse the moment where they tend to skip a step.

Keep feedback specific. “That was clearer because you named the action and when to expect it” reinforces what the agent should repeat. “Good job” is encouraging but offers little direction. Likewise, avoid stacking several corrections at once. Prioritize the behavior that matters most, agree on how to practice it, and return to other opportunities in later sessions.

Structured call center coaching can connect observations with practice activities and follow-up. The process should complement the tools a team already uses rather than treating coaching as a separate conversation with no link to daily work.

How should you document the coaching plan?

Record the evidence, expected behavior, practice and support agreed, and who will follow up, using factual language and the organization’s recordkeeping rules.

A concise record helps the agent and supervisor remember what they agreed to do. It also allows a later check-in to focus on the same behavior instead of relying on memory. Document what was observed and what support was provided; avoid assumptions about attitude, motivation, or character.

A useful coaching note can capture the following:

Plan element What to record Example
Observation The behavior and the source reviewed Agent explained the next step but did not check whether it was understood
Expected behavior The observable action to use next time Summarize the next step and ask the customer to confirm
Agent perspective Relevant context or barrier raised in the discussion Agent reported uncertainty about which approved explanation to use
Practice and support Activity, resource, or assistance agreed Role-play two call endings and review the current knowledge article
Follow-up Owner, review point, and evidence to revisit Supervisor and agent review a relevant interaction at their next check-in

Make the note useful to the employee as well as to a supervisor. Write the agreed action in language the agent can recognize and apply. If the action depends on a resource, identify the resource or the person responsible for providing it. If the agent has not yet had a reasonable chance to use the skill, record that context rather than treating the absence of a new example as proof that coaching failed.

Follow organizational rules for access, retention, and sensitive information. Keep coaching records consistent across leaders, but do not force every situation into identical wording. The standard should make it possible to understand what prompted the conversation, what the agent will try, and how the team will know whether further support is needed. In regulated work, version control is especially important: people should be able to identify who created, changed, and approved the guidance used in coaching.

Quality assurance findings are most useful when they lead to a relevant action. Teams can connect evaluation observations with targeted development through quality assurance practices, then track whether the agent received the appropriate coaching, learning, or refresher information. The record should reflect that connection without suggesting that an evaluation score alone tells the full story.

How can you follow up and reinforce progress?

Set a check-in that gives the agent a fair chance to practice, review evidence tied to the agreed behavior, and adjust support according to what you learn.

Coaching is a cycle, not a one-time meeting. Agree on when to revisit the skill and what evidence would make the check-in useful. The interval should reflect the work pattern and the agent’s opportunity to use the behavior. A follow-up that is too soon may produce no meaningful example; a vague promise to “check back later” can cause the plan to disappear.

At the check-in, ask the agent how the practice went before sharing your own observation. Review a relevant example against the same standard and look for the specific behavior discussed. Recognize progress in concrete terms. If the agent now checks for understanding consistently, say what changed and why it matters. Then ask what will help sustain the behavior during busy or unusual interactions.

Use the follow-up to diagnose what remains unresolved:

  • The agent can explain the skill but has not had a chance to use it. Agree on another reasonable opportunity and avoid treating lack of exposure as lack of progress.
  • The agent understands the expectation but is still uncertain in practice. Provide another guided rehearsal, model the step, or break the behavior into smaller decisions.
  • The agent cannot find or interpret the guidance. Check the knowledge resource and involve its owner if the content is hard to locate or ambiguous.
  • The process or tool gets in the way. Route the issue to the appropriate process or system owner while clarifying any approved interim guidance.
  • The same behavior remains inconsistent after support. Review the evidence and broader performance context with the appropriate leader, then decide whether a structured development plan is needed.

Do not equate a single successful practice attempt with lasting change, and do not ignore meaningful improvement because the agent is not yet consistent in every situation. Look for evidence that the behavior is being applied in the work and use it to choose the next support. The supervisor’s role is to keep the expectation clear and the follow-up fair, not to promise a result that cannot be guaranteed.

Knowledge management also belongs in this loop. If coaching reveals a missing or outdated answer, route that finding to the people who maintain the content. Accurate, usable knowledge helps agents provide correct information on the first interaction. Teams can connect coaching with knowledge management for support teams and relevant learning management resources, so that a recurring knowledge need can lead to a refresher rather than repeated one-to-one correction.

How can leaders make coaching consistent across a team?

Give supervisors shared standards, calibrated examples, clear documentation expectations, and a way to connect coaching with learning and knowledge updates.

Consistency does not mean every agent receives the same script or identical feedback. It means that supervisors use common criteria, explain decisions with evidence, and complete agreed follow-up. Without shared expectations, one supervisor may treat a small deviation as a major issue while another overlooks a pattern. Calibration helps leaders compare how they interpret a standard and discuss borderline examples before those differences undermine trust.

Leaders can strengthen consistency by establishing a practical operating routine:

  1. Clarify the standard. Make sure supervisors can find the current criteria and know which version applies.
  2. Review examples together. Compare how different leaders interpret the same interaction and explain the reasoning behind the evaluation.
  3. Share coaching prompts. Offer questions and practice formats that help supervisors make sessions participatory without requiring them to use identical language.
  4. Check completion and quality. Review whether sessions took place, whether plans name an action, and whether follow-up is recorded.
  5. Look for system signals. If several agents struggle with the same procedure, examine the process, training, and knowledge content before treating it as a collection of individual shortcomings.

Use quality information with care. A statistically valid sampling approach can provide meaningful insight into work patterns, but automated scores should not replace human review or targeted coaching. A supervisor needs to understand the interaction and the employee’s circumstances before deciding what support fits. The aim is to operationalize useful quality information into coaching, assigned learning, or refreshed knowledge—not to turn a score into a complete account of performance.

Coaching can also support a broader view of employee development. A conversation about a current skill may reveal a career interest, a need for recognition, or an issue that belongs in a separate performance process. Handle those topics through the appropriate channel, and do not use developmental coaching to obscure a formal process that requires different communication. A connected talent management approach can help leaders keep development goals visible alongside day-to-day performance conversations.

Tools should support a clear workflow rather than dictate it. C2Perform complements existing CCaaS, CRM, and WFM systems by bringing together quality assurance, knowledge management, learning, coaching, communications, engagement, and talent management. Leaders assessing their operating model can review how C2Perform integrates with existing systems and its resources for operations leaders. The practical question is whether the workflow helps supervisors move from an observation to an appropriate action and a visible follow-up.

A regular leadership review can ask:

  • Are coaching plans tied to specific observations and current standards?
  • Do agents have access to current guidance and a realistic chance to practice?
  • Are supervisors following up on the actions they agreed?
  • Do repeated gaps point to a process, content, or system issue?
  • Are leaders considering broader performance and development context, not only quality feedback?

These questions help distinguish a coaching opportunity from a larger operational issue. They also give leaders a way to improve the coaching process itself. If meetings repeatedly end without a practical action, simplify the template or help supervisors practice the conversation. If notes are complete but behavior does not change, examine whether the agent had the resources and opportunity needed to apply the skill.

What should a supervisor do when coaching is not working?

Recheck the evidence and the expected behavior, ask the agent what is getting in the way, and choose a different form of support before repeating the same conversation.

When an agreed action does not lead to progress, do not simply repeat the original feedback louder. First confirm that the expectation is clear and still current. Then ask the agent what happened when they tried to use it. The answer may show that the practice was too abstract, the resource was difficult to use, the work situation differed from the example, or the agent needs support beyond the skill being discussed.

Use a short diagnostic sequence:

  1. Revisit the evidence. Confirm that the example still illustrates the behavior under discussion and that the relevant standard has not changed.
  2. Ask what the agent tried. Invite a specific account of when the agent used the skill and what happened next.
  3. Check access and opportunity. Determine whether the employee had the tools, information, authority, and appropriate work examples needed to apply the behavior.
  4. Adjust the learning method. Use demonstration, guided practice, a job aid, a knowledge review, or observation, depending on the barrier.
  5. Set a new review point. Agree on what both parties will do and how the next conversation will evaluate progress.

For example, an agent may understand the call-closing technique in a role-play but struggle when a customer introduces a new question at the end of a real call. The next session can practice how to acknowledge the question, resolve or route it appropriately, and then return to confirming the next step. If the difficulty stems from unclear routing guidance, address that resource rather than asking the agent to memorize an improvised response.

Sometimes coaching is not the right or only response. A formal performance matter, conduct concern, or accommodation need may require a different process and the involvement of the right organizational partner. Supervisors should follow company policy and avoid making promises outside their role. Clear boundaries protect the agent and help ensure that a development conversation is not confused with a formal decision.

Leaders can also help supervisors refine their practice. Peer observation, review of anonymized coaching examples, and shared reflection can reveal whether a supervisor is giving too much advice, asking leading questions, or failing to confirm a concrete next step. A brief review of the coaching conversation itself can be as valuable as reviewing the original interaction. The desired result is a repeatable, respectful process that makes the agent’s next action clear.

Consider a worked example. A supervisor notices that an agent gives accurate information about a claim document but does not explain what the customer should do if the document is unavailable. The supervisor first checks the current procedure and confirms that an approved alternative exists. In the session, the agent explains that the guide is difficult to find while handling a live conversation. The supervisor does not treat the omission as a failure to learn. They review the approved alternative together, practice a short explanation, and agree that the agent will use the knowledge article during the next relevant interaction. The supervisor also routes the findability issue to the knowledge owner. At follow-up, they review a relevant example and ask whether the resource was easy to locate. This plan addresses both the agent’s practice need and a system barrier.

The example shows why a coaching plan should name more than a target behavior. It should make the support visible, identify any dependency on another team, and distinguish what the agent controls from what a leader or content owner must change. If the agent applies the updated explanation but still cannot locate the answer quickly, the next action should address search or content organization rather than repeat the same instruction. If the article is revised, supervisors should make sure everyone uses the approved current version.

A brief coaching calibration can help leaders apply this approach. Supervisors can review a sample scenario, independently identify the observed behavior and appropriate next step, then discuss where their interpretations differ. The aim is not to force identical wording. It is to align on the standard, separate evidence from inference, and agree when a knowledge or process issue should be escalated. Leaders can also compare coaching notes to see whether plans give agents a clear action and a fair follow-up. Use anonymized examples where appropriate and follow internal rules for sharing employee information.

Organizations that combine quality findings with learning and content ownership can avoid asking frontline supervisors to solve every systemic issue alone. A supervisor may identify the need, while a knowledge manager corrects a source, a learning professional creates targeted practice, or an operations leader resolves a workflow barrier. That division of responsibility helps coaching remain focused while still addressing causes that affect the wider team.

For broader context on professional coaching principles and resources, consult the International Coaching Federation. In a contact center, leaders should adapt coaching to the organization’s role expectations, quality standards, and employee-support practices.

Schedule a conversation about supporting your coaching workflow

Frequently Asked Questions

How often should a supervisor coach an agent?

Choose a cadence that fits the team’s operating rhythm, the agent’s needs, and the opportunity to practice. Set the next check-in while the action is clear, then revisit the plan when new evidence or support needs emerge.

What should a supervisor do when an agent disagrees with feedback?

Listen to the agent’s perspective and review the interaction and applicable standard together. Correct any misunderstanding, and pause the conclusion if evidence is incomplete or unclear.

Should coaching focus only on quality scores?

No. Quality observations can be useful inputs, but coaching should also consider context such as attendance, career development, relevant performance plans, access to current guidance, and the agent’s opportunity to practice.

How can supervisors coach when a knowledge article is wrong?

Do not ask the agent to learn an inaccurate procedure. Escalate the content for review, follow approved interim guidance where applicable, and return to skill practice once the source is reliable.

What makes a coaching goal practical?

A practical goal describes an observable action, identifies when the agent should use it, and can be rehearsed or reviewed in the work. “Improve communication” is broad; “summarize the next step and confirm the customer understands it before closing” gives both people a clear behavior to discuss.

Effective call center coaching turns a fair observation into a specific action, supported practice, and a meaningful follow-up. Prepare with care, listen before deciding, address process and knowledge barriers, and keep the employee’s broader development in view.