← ccPlanning Academy · Quality track

What quality assurance is for

Deep-dive lesson · about 10 minutes · short quiz at the end

ccPlanning academy · quality · deep dive

What quality assurance is for

Not “did they follow the script?” but “did the customer get what they needed?”

The trap

The 40-box form measures the wrong thing.

Most QA forms grow by accretion: every incident adds a checkbox, until the form rewards saying the right words in the right order. An agent can score 98% — greeting, name check, branding, hold script all perfect — and still leave the customer’s problem unsolved.

A score that high on an unhappy customer is a sign the form is measuring compliance, not quality.

The definition

Quality is the customer outcome.

The only durable definition: did this contact resolve the customer’s need, accurately, in a way they felt good about? Everything on the form should serve that question or come off it.

Script adherence matters only where it changes the outcome — a required regulatory disclosure, yes; the exact wording of the greeting, rarely.

Why it drifts

We score what’s easy to score.

“Did they say the brand name?” is binary and quick. “Did they actually solve it?” takes judgement and time. So forms fill up with the easy, objective, low-value items and skimp on the hard, subjective, high-value one.

The result: a programme that is precise about things that don’t matter and vague about the thing that does.

The two questions

Outcome and experience.

Good QA scores two things. Was it resolved? — correctly, completely, first time. And how did it feel? — did the agent listen, show ownership, make it easy.

Compliance is a third, smaller bucket: the few things you are legally or contractually required to do. Keep it small and ring-fenced.

The test

Could a perfect score sit on an unhappy customer?

Run your form through one question: is it possible to score 100% on a contact the customer hated, or that didn’t resolve? If yes, your form is measuring the wrong thing, and no amount of calibration or sampling will save it.

Fixing the definition comes before fixing the process.

Why it matters to the operation

Quality shapes the work you forecast.

Outcome-based quality isn’t a soft nicety. Contacts that don’t resolve come back as repeats; contacts handled badly become complaints and escalations. So the behaviours QA scores feed straight into the volume and handle time a planner has to forecast.

Score the outcome and you’re improving the very demand drivers the operation runs on.

The takeaway

Define quality as the outcome, then build the form.

Was it resolved, and how did it feel — with a small, ring-fenced compliance bucket. If a perfect score can sit on an unhappy customer, fix the definition first.

Now test yourself ↓

1 / 8

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: scoring outcomes, not scripts

The most common failure in contact-centre quality assurance is a form that measures the wrong thing. It happens for an understandable reason: the items that are easy to score — did the agent use the greeting, say the brand name, follow the hold procedure — are objective and quick, while the item that actually matters — did the customer’s problem get solved, accurately and in a way they felt good about — takes judgement and time. So forms drift towards compliance, and you end up able to score an agent 98% on a contact that left the customer unresolved and annoyed. A score that can do that is not measuring quality.

The definition that holds

The durable definition of quality is the customer outcome: was the need resolved, correctly and completely, and how did the experience feel? Everything on the scorecard should serve one of those two questions. Compliance — the genuinely mandatory disclosures and steps — is a third, deliberately small bucket; it earns its place only where the wording or step actually changes the outcome or carries legal weight. The simplest test of a form is to ask whether a perfect score could sit on an unhappy, unresolved customer. If it could, the form is the problem, and no amount of calibration, sampling or coaching downstream will rescue a programme built on the wrong definition.

Why the planner should care

Outcome-based quality is not a soft HR concern; it is a demand lever. Unresolved contacts return as repeats and inflate volume; badly handled ones become complaints, escalations and longer handle times. The behaviours a good QA programme rewards are the same ones that reduce the work the operation has to forecast and staff. That is why quality belongs in the planner’s field of view, and why the rest of this track keeps returning to the link between the scorecard and the plan.

The principle to remember: quality is the customer outcome — resolved, and how it felt — not compliance with a script. If a perfect score can sit on an unhappy customer, fix the definition before anything else.

Quick quiz

Five questions. Pick an answer to each, then check your score.

1. What is the durable definition of contact quality?

Quality is the outcome — resolved, correctly, in a way the customer felt good about.

2. Why do QA forms drift towards compliance?

We score what’s quick and binary, so the form fills with low-value boxes.

3. What’s the quick test of a flawed QA form?

If 100% can sit on a customer who was failed, the form measures the wrong thing.

4. Where does script adherence belong on the form?

Keep compliance small and only for steps that genuinely matter.

5. Why should a workforce planner care about QA?

Quality shapes the volume and AHT a planner has to forecast.