Agent Coaching & Quality Assurance

An effective QA framework has four components. (1) Quality Rubric: a standardized scorecard assessing each customer interaction across 4–6 dimensions with clear behavioral anchors. Typical dimensions: Greeting and tone (professional, warm, appropriately empathetic); Understanding the issue (did the agent correctly identify and restate the customer's actual problem?); Accuracy of response (was the information provided technically correct and current?); Efficiency (was the ticket resolved with appropriate urgency and without unnecessary round-trips?); Resolution quality (was the resolution complete — not just answering the stated question but addressing the underlying need?); and Closing (was the customer left with clear next steps and confidence the issue was resolved?). (2) Sample Size: Support Ops reviews 5–10 tickets per agent per week for small teams; 3–5 per agent per week for larger teams (statistically meaningful without overwhelming the QA resource). (3) Calibration: QA reviewers score the same sample tickets monthly to identify inconsistencies in rubric interpretation. (4) Feedback Delivery: structured weekly or bi-weekly 1:1 coaching sessions where the agent and manager review specific tickets together. The goal is to improve the agent's next ticket, not relitigate a past score.

Effective coaching is specific, timely, and bidirectional — not a one-way performance critique. A productive coaching session structure: (1) Review this week's QA scores in aggregate (did they improve, stagnate, or decline from last week?). (2) Discuss one "highlight" ticket — a ticket the agent handled exceptionally well, with specific identification of what made it excellent. This reinforces good behavior and builds the agent's model of quality. (3) Discuss one "development opportunity" ticket — a ticket where the agent could have approached something differently, with root cause discussion ("Was this a gap in knowledge? A process issue? A judgment call that went the wrong direction?"). (4) Agree on one improvement action for the next week — specific and measurable: "This week, before sending a resolution, restate the customer's original question in your response to confirm you addressed it accurately." (5) Agent shares their feedback — what process, tool, or knowledge barriers are affecting their ability to deliver quality? The agent's voice surfaces systemic issues that coaching cannot solve individually.

Manual QA does not scale linearly — a 50-agent team cannot be reviewed at 5 tickets/agent/week by a single QA analyst without overwhelming that resource. Scaling strategies: QA Specialist role: hire a dedicated QA specialist (often a senior agent who demonstrates strong review skills and is interested in coaching) at every 20–25 agent headcount increase. Each QA specialist manages their own coaching portfolio of 20 agents. AI-assisted QA: tools like Zendesk QA (formerly Klaus), Scorebuddy, and MaestroQA use machine learning to auto-score 100% of tickets on defined dimensions (sentiment, resolution, empathy signals), routing only the lowest-scored and highest-scored tickets for human review. This dramatically increases QA coverage without proportional QA headcount growth. Peer review programs: senior agents review a subset of junior agent tickets weekly, developing their coaching skills while extending QA coverage. All peer reviews are calibrated against the benchmark rubric by the QA specialist to prevent inconsistency. Support Ops tracks QA program health with three metrics: QA coverage rate (% of tickets reviewed), score trend by agent, and correlation between QA scores and CSAT — a QA program that does not predict CSAT is measuring the wrong things.