CX managers who run 1:1 coaching sessions without a structured template spend the first ten minutes of every meeting figuring out what to talk about. A good coaching template fixes that by capturing the right data before the conversation starts and giving both manager and agent a shared structure for what comes next.

This guide walks through the seven fields every CX coaching template needs, and shows where AI tools can pre-populate the data-heavy sections so managers spend their time on actual coaching rather than call retrieval.

Methodology

A 1:1 coaching template should do two things: anchor the conversation in evidence from real calls, and convert that evidence into a specific commitment from the agent. The seven fields below move in sequence from evidence to diagnosis to action. Fields 1 through 3 are data-entry tasks that can be automated. Fields 4 through 7 require manager judgment and cannot be automated.

What is a good 1 on 1 agenda?

A good 1:1 coaching agenda follows a simple logic: start with what happened (evidence from calls), move to why it happened (root cause), then finish with what changes (commitment and follow-up). The most common mistake is spending the session on the evidence phase because the manager had to pull and review calls manually before or during the meeting. When fields 1 through 3 are pre-populated from your QA system, the conversation can start at the diagnosis stage, which is where coaching actually happens.

Field 1: Call and Interaction Reference

Every coaching session should be tied to specific calls, not a general impression of the agent's recent performance. This field captures the date of the call, the call ID or recording link, and any relevant context (inbound vs. outbound, call type, queue).

What to include:

  • Date and time of the call
  • Call ID or direct link to the recording
  • Call type and queue context
  • QA evaluation date if different from call date

Without a specific call reference, agents cannot replay the moment being discussed and managers cannot verify their own recall. General impressions of "how you've been doing lately" are not coachable. Specific calls are.

Insight7 populates this field automatically. Every scored call is stored with its transcript, recording link, and metadata. Managers open the agent scorecard, select the calls they want to discuss, and the reference data is already there.

Field 2: Criteria Scores with Evidence

This field captures the numerical or weighted score on each evaluation criterion, and the specific transcript quote or interaction moment that supports it. The score alone is not enough. An agent who scored 60% on empathy cannot improve without knowing exactly which moment in which call produced that result.

What to include:

  • Score per criterion (on your standard scorecard)
  • Direct transcript quote or timestamped recording clip
  • Whether the score was above or below the agent's average

Avoid this common mistake: recording only summary scores without evidence. "Empathy: 3/5" tells an agent what their score is but not what behavior created it. The coaching conversation stalls because the agent has no reference point for what they did differently in this call versus a higher-scoring one.

Insight7 links every criterion score to the exact quote and location in the transcript. Managers can click through to verify any score, and agents can see the same evidence during the 1:1. This replaces a 15-minute call review exercise with a 30-second reference lookup.

Field 3: Behavioral Gap Description

A behavioral gap is the difference between what the agent did and what good performance looks like for that criterion. This is distinct from the score: the score tells you the gap exists; the behavioral description tells you what the gap looks like in practice.

What to include:

  • What the agent did (tied to the transcript evidence from Field 2)
  • What good performance looks like on this criterion
  • Whether the gap is a pattern across multiple calls or an isolated instance

Good behavioral gap descriptions are specific and observable. "You interrupted the customer three times in the first two minutes" is coachable. "Your listening skills need work" is not.

Insight7 pre-generates criterion context based on how your scorecard is configured, including descriptions of what good and poor look like for each item. When a score falls below threshold, the system surfaces the relevant gap description alongside the evidence. Managers can edit or add context before the 1:1.

What is a customer experience playbook?

A customer experience playbook is a set of documented behaviors, scripts, and decision rules that define how agents should handle each interaction type. A CX coaching template is the session-level tool that connects actual call data to the behaviors defined in the playbook. Without call evidence (Fields 1 through 3), a coaching session is just a re-read of the playbook. With evidence, it is a targeted intervention tied to a specific deviation from the expected behavior.

Field 4: Root Cause

This is the first field that requires manager judgment. Root cause identifies why the behavioral gap exists. The three categories most relevant to contact center coaching are:

  • Skill gap: The agent knows what good looks like but cannot execute it consistently. Needs practice.
  • Knowledge gap: The agent does not know the correct behavior, policy, or product information. Needs training or information.
  • Motivation or environment factor: The agent knows and is capable but is not applying the behavior. Needs a different conversation.

Getting root cause wrong leads to the wrong intervention. An agent with a knowledge gap who gets assigned a role-play practice session will practice the wrong behavior. An agent with a skill gap who gets sent to a training module will not develop the muscle memory needed to change their call behavior.

Field 5: Coaching Assignment

Based on the root cause identified in Field 4, this field records the specific action the agent will take before the next 1:1. The assignment should be concrete and verifiable.

Examples by root cause:

  • Skill gap: Complete two role-play practice sessions on [objection handling] using the AI coaching module and retake until scoring above threshold
  • Knowledge gap: Review the updated policy on [topic] and send manager a three-sentence summary of the key change
  • Motivation factor: Manager and agent agree on a specific call to re-listen to together in next session

Vague assignments like "work on empathy" do not produce change. Specific assignments with a completion criterion do.

Field 6: Agent Commitment

This field records what the agent says they will do differently, in their own words. The distinction from Field 5 is that Field 5 is the assigned practice task; Field 6 is the behavioral commitment for live calls.

What to capture:

  • The specific behavior the agent commits to changing
  • The call situations where they will apply it
  • Any self-identified obstacles (note these: they often reveal the real root cause)

Agent-authored commitments outperform manager-authored ones because they require the agent to internalize the behavioral change rather than just receive it. Ask the agent to state the commitment aloud, then record it verbatim.

Field 7: Follow-Up Date and Measurement Criteria

A coaching session without a follow-up date is a monologue. This field sets the measurement checkpoint: when will you review whether the commitment from Field 6 produced a change in the scores from Field 2?

What to include:

  • Date of the next coaching check-in (typically 1 to 2 weeks out)
  • Which specific criteria you will review at that check-in
  • The score target that would indicate progress

Measurement criteria prevent follow-up sessions from defaulting to general check-ins. "We will look at your empathy score on the next five calls scored between now and May 15, with a target of moving from 62% to above 70%" is a measurable commitment. "Let's see how it goes" is not.

How Insight7 Automates Fields 1 Through 3

Insight7 covers the data-entry portion of a coaching template automatically. When a supervisor opens an agent scorecard in Insight7, the call reference (Field 1), criteria scores with transcript evidence (Field 2), and pre-generated behavioral gap descriptions (Field 3) are already populated. The manager enters the coaching session with the evidence layer complete and spends the full session on root cause, assignment, commitment, and follow-up.

For teams managing 10 or more agents, this is the difference between running 1:1s that produce change and running 1:1s that produce paperwork. See how Insight7 supports coaching workflows.

FAQ

What is a good 1 on 1 agenda?

A good 1:1 agenda for CX coaching sessions covers three zones: evidence review (10 minutes, using pre-populated call data from your QA system), diagnosis and assignment (15 minutes, focused on root cause and the specific practice task), and commitment and follow-up scheduling (5 minutes). The session should end with both parties knowing exactly what changes before the next check-in and when that check-in happens.

How many calls should I review in a 1:1 coaching session?

Reviewing one to two calls in depth is more effective than skimming five. One well-chosen call with strong transcript evidence gives you enough to anchor the behavioral gap description, confirm or rule out the root cause, and generate a specific assignment. More calls without depth produces a list of problems with no clear priority. Use your QA scorecard to select the call that best represents the pattern you want to address.

How often should 1:1 coaching sessions happen for contact center agents?

Most contact center research points to weekly or bi-weekly 1:1s as the minimum for meaningful skill development. ICMI guidelines on contact center coaching recommend that supervisors hold structured coaching sessions at least twice per month per agent. With automated QA pre-populating the evidence fields, a structured 30-minute 1:1 is achievable at that frequency without adding to the manager's preparation time.