FREE2026 Call Center Software Comparison|Independent, data-backed — no sales callGet the PDF →

Spotsaas logo
Free PDF · Call Center

Agent Coaching & 1:1 Template

A repeatable structure for one-on-one agent coaching sessions that ties QA scores and operational metrics to specific, observable behaviors and concrete next steps. Use it to run consistent, motivating 1:1s that actually move performance instead of becoming a number-reading exercise.

  • How to run a coaching 1:1 that works
  • Session Structure (the GROW-style flow)
  • Performance Snapshot
  • Coaching Record
★★★★★Trusted by 3,000+ buyers· built from 75 call center software tools· independent
PDF · FreeAgent Coaching & 1:1 Template

Where should we send it? Free · arrives in seconds · no spam.

We email it to you — one-click unsubscribe anytime.

  1. 1Tell us where to send it

    Your name and work email — nothing more.

  2. 2Check your inbox

    Your template arrives in seconds, not days.

  3. 3Use it with your team

    Editable and ready to share — make it your own.

A peek inside

See exactly what you're getting

Free PDF
Spotsaas · 2026
Agent Coaching & 1:1 Template
How to run a coaching 1:1 that works
Session Structure (the GROW-style flow)
Performance Snapshot
Coaching Record
Get the template

What it is

The Agent Coaching & 1:1 Template is a repeatable structure for one-on-one coaching sessions that ties QA scores and operational metrics to specific, observable behaviors and concrete next steps. Its purpose is to rescue coaching from the trap it usually falls into — a number-reading exercise where a supervisor recites the agent’s AHT and QA score, the agent nods, and nothing changes. A good coaching session is the opposite: the agent talks more than the coach, every piece of feedback is tied to a real call, and the agent leaves with no more than two priorities and a written commitment.

The template is built on a GROW-style flow — a structured conversation that moves from goal to reality to options to a way forward — supported by working sections. A Performance Snapshot grounds the session in the data: the QA scores, AHT, FCR, and CSAT for the period under review. A Coaching Record captures the specifics: the agent and coach, the session date and period, the actual call IDs reviewed, the top strength reinforced, and the one or two coaching priorities expressed as observable behaviors. And a Coaching Self-Check helps the supervisor audit their own session afterward.

That self-check is what makes the template more than a form. It asks the supervisor hard questions: Did the agent talk more than I did? Was every piece of feedback tied to a specific, observable behavior on a real call? Did we leave with no more than two priorities and a written commitment? Did I distinguish agent-controllable issues from process or product problems? These questions encode the difference between coaching that moves performance and coaching that just fills a calendar slot, and they hold the coach accountable, not just the agent.

What it's used for

Coaching is the primary lever a supervisor has to improve agent performance, yet it’s routinely done badly — reduced to reading metrics aloud. This template exists to make coaching consistent, specific, and genuinely developmental. Teams use it to:

  • Run consistent, structured 1:1s using a GROW-style flow, so every coaching session follows a proven arc instead of meandering or defaulting to a number recital.
  • Ground feedback in a Performance Snapshot — QA, AHT, FCR, CSAT — so the conversation starts from data the agent can see and trust rather than the coach’s impressions.
  • Tie every piece of feedback to a specific, observable behavior on a real reviewed call (by ID), because “be more empathetic” is useless while “on this call you interrupted the customer twice” is coachable.
  • Limit each session to no more than two priorities and a written commitment, since overloading an agent with ten fixes guarantees none of them stick.
  • Reinforce a top strength deliberately, so coaching builds confidence and isn’t experienced as a relentless list of failures.
  • Distinguish agent-controllable issues from process and product problems before coaching, so agents aren’t coached on things outside their control.
  • Self-audit the session afterward with the supervisor self-check, ensuring the coach drew the agent out rather than lecturing and actually left the conversation actionable.

Who uses it

Coaching is fundamentally a supervisor-agent activity, but the structure and outputs ripple across the operation’s development and quality functions. The roles that rely on this template include:

Team Leads / SupervisorsThey’re the primary users — running the 1:1s, grounding them in the performance snapshot, capturing the coaching record, and using the self-check to keep their own coaching honest and effective.
AgentsThey’re the focus of the session and benefit from a structure that draws them out, ties feedback to real calls, and leaves them with a clear, manageable commitment rather than an overwhelming critique.
QA TeamsThey provide the QA scores and call selections that anchor the coaching, and they benefit when coaching closes the loop on the specific behaviors their evaluations surface.
Operations ManagersThey use consistent coaching records across the team to ensure every agent is actually being developed, and to spot supervisors whose coaching isn’t moving the numbers.
WFM / Training TeamsThey connect coaching to the onboarding ramp — the 30-60-90 targets a new agent worked toward become the ongoing coaching focus, with no cliff at graduation.
HR / People DevelopmentThey draw on the documented coaching record as evidence of structured development, which matters for performance management, promotion decisions, and demonstrating fair process.

Context & good to know

Coaching is consistently identified as one of the highest-leverage activities in a contact center, yet it’s one of the most poorly executed, because the natural failure mode is so easy to fall into. A supervisor under time pressure pulls up the agent’s metrics, reads them out, says “let’s get that AHT down,” and moves on. The agent learns nothing actionable and the score doesn’t move. The GROW-style structure and the insistence on observable behaviors tied to specific calls exist precisely to break this pattern and make the session developmental rather than evaluative.

The principle that the agent should talk more than the coach is grounded in how adults actually change behavior. People commit to conclusions they reach themselves far more than to instructions they’re given. A coach who lectures gets compliance at best; a coach who asks good questions and lets the agent diagnose their own call gets ownership. The self-check question “did the agent talk more than I did?” is a deceptively simple diagnostic for whether real coaching happened or whether the supervisor just delivered a monologue.

Coaching doesn’t live in isolation — it sits at the center of the contact-center performance system. It draws its raw material from QA scorecards (the specific behaviors that lost points) and from operational metrics like AHT, FCR, and CSAT. It connects backward to onboarding, picking up the 30-60-90 ramp targets a new agent worked toward so there’s no development cliff at graduation. And the critical discipline of separating agent-controllable issues from process and product problems ensures coaching improves the right thing: an agent coached repeatedly on a low CSAT caused by a broken billing system will disengage, while the same data routed to process improvement gets the actual problem fixed. The template keeps coaching focused on what the agent can control and what the data genuinely supports.

✓ Independent · vendors can't pay to rank

Built on verified data, not vendor spin

Every Spotsaas resource draws on the Spotsaas Score — a blend of verified review ratings, review volume, and feature depth across 75 call center software tools. Refreshed regularly; data as of June 2026.

FAQ

Questions, answered

What is the GROW model in coaching?

GROW is a coaching framework that structures a conversation in four stages: Goal (what we want to achieve), Reality (what’s actually happening now), Options (what could be done differently), and Will or Way forward (what the agent commits to). It’s widely used because it draws the agent toward their own conclusions rather than dictating them. The template uses a GROW-style flow so coaching sessions have a consistent, proven arc instead of becoming an ad-hoc number review.

Why should the agent talk more than the coach?

Because people commit to conclusions they reach themselves far more than to instructions they’re given. A coach who lectures gets compliance; a coach who asks questions and lets the agent diagnose their own call gets genuine ownership of the change. Coaching is about drawing out, not telling. The supervisor self-check explicitly asks “did the agent talk more than I did?” as a quick test of whether real coaching happened or the session was a monologue.

Why must feedback be tied to a specific, observable behavior?

Because vague feedback can’t be acted on. Telling an agent to “be more empathetic” gives them nothing to do differently, while “on call #4821 you interrupted the customer twice before they finished explaining the issue” points to an exact behavior on a real call they can change. Tying every piece of feedback to an observable behavior on a reviewed call ID is what turns coaching from an opinion into a concrete, improvable action.

Why limit coaching to two priorities per session?

Because overloading an agent with a long list of fixes guarantees none of them stick — attention and behavior change both have limited capacity. Focusing on no more than two priorities, plus a written commitment, makes the change manageable and the follow-up clear. The next session can tackle the next priority. The template caps priorities deliberately so coaching produces real, sequential improvement rather than an overwhelming and ultimately ignored critique.

How do I separate agent-controllable issues from process problems?

Before coaching on a metric, ask whether the agent could actually have changed the outcome. A low CSAT caused by a broken billing system, a long AHT driven by a slow tool, or an escalation forced by inadequate authority are not the agent’s failures. Coaching an agent on something outside their control breeds resentment and fixes nothing. The template stresses this distinction so agent-controllable issues go to coaching and systemic issues go to process improvement.

What should be captured in a coaching record?

The agent and coach, the session date and the period reviewed, the specific call IDs discussed, the top strength reinforced, and the one or two coaching priorities expressed as observable behaviors with a written commitment. This record makes coaching auditable, lets the next session follow up on the prior commitment, and gives operations and HR evidence that structured development is actually happening rather than being assumed.

Why reinforce a strength, not just correct weaknesses?

Because coaching that’s nothing but a list of failures demoralizes agents and breeds defensiveness, which shuts down the learning the session is meant to produce. Deliberately reinforcing a top strength builds confidence and signals that the coach sees the whole performance, not just the gaps. It also reinforces the behaviors you want repeated. The template includes a top-strength field so every session balances correction with genuine recognition.

How does coaching connect to QA scores?

QA scores are a primary input to coaching — the criterion-level breakdown from a QA scorecard tells the supervisor exactly which behaviors to focus on, and the specific scored calls become the calls reviewed in the session. Coaching then closes the loop, turning the QA finding into an observable behavior the agent works on. Without coaching, QA just produces numbers; without QA, coaching lacks the specific evidence that makes it credible. They’re two halves of the same system.

How often should coaching 1:1s happen?

Regular cadence matters more than frequency — many operations run a coaching 1:1 weekly or biweekly per agent, with new agents coached more often during their ramp. Consistency is what builds the trust and momentum that make coaching effective; sporadic sessions that only happen when something’s wrong feel punitive. The template’s repeatable structure is designed to support a regular cadence so coaching becomes a normal, expected rhythm rather than a special event.

How does coaching connect to onboarding?

Directly — the 30-60-90 ramp targets a new agent worked toward during onboarding become the focus of ongoing coaching once they’re fully live, so there’s no development cliff at graduation. The QA scores and metrics that gated nesting graduation are the same ones that anchor the first coaching sessions. Using the same framework across onboarding and coaching means an agent’s development is continuous, with structure that carries them from new hire through tenured performer.

Grow your pipeline with buyers who are already looking for you

254,000+ buyers use Spotsaas every month to evaluate and shortlist software. Get in front of them — for free, or with a managed growth plan built around your category.