QA is coaching, not surveillance
Quality assurance goes wrong the moment it feels like a hunt for mistakes. Agents who believe QA exists to catch them get defensive, game the scorecard, and stop taking the small risks that make chat feel human. Done right, QA is a shared vocabulary for what good looks like and a steady stream of specific, kind feedback. Frame it that way or it will backfire.
Keep the scorecard small
A rubric with twenty criteria gets filled in mechanically and teaches nothing. Pick the handful of things that actually define a good conversation on your team — did we solve it, was the tone right, was it accurate, did we set clear expectations — and score those. A short scorecard you use every week beats a comprehensive one you abandon in a month.
Sample, don't audit everything
- Review a handful per agent per week, chosen to include a mix — not just the disasters or the wins.
- Deliberately sample low-rated chats, where the lessons are richest, alongside random ones.
- Rotate who reviews, so the standard is shared rather than one person's taste.
Score the conversation, coach the person
The scorecard rates the transcript; the conversation with the agent is where improvement happens. Lead with what went well — specifically, not as a throat-clearing before the criticism — then pick one thing to work on. One concrete, improvable habit per session sticks; a list of ten faults just demoralizes.
Look for system problems, not just agent problems
When the same issue shows up across agents, it is not an agent problem — it is a missing canned response, an unclear help article, a product rough edge, or a policy with no fast path. QA that only ever produces "the agent should have…" is missing half its value. Feed the patterns back into your content and process, not just your coaching.
Make good work visible
Share great transcripts with the team, with names on them and permission asked. Nothing teaches "this is our standard" faster than a real example everyone can see. In MyLiveChat, transcripts are searchable and reviewable, so building a small library of exemplars — and the conversations to learn from — costs attention, not tooling.