Home/Blog/Every call
QA · 6 min read

From a small QA sample to every call

Reviewing every call is not just more of the same. It changes the job.

In short
  • A small random sample estimates what is typical. It misses rare events such as compliance slips and churn risks.
  • At 1 slip in 200 calls, reviewing 4 calls finds it for a given agent about 2% of the time.
  • Reading every call turns rare events into lists with owners and moves QA from listening to deciding.
  • It only works with evidence for every point and clear rules for when a person reviews.

In most contact centers, quality assurance means listening to a few calls per agent per month. The sample is chosen at random or by hand, scored against a checklist and discussed in a coaching session. Everyone knows the sample is small. It is simply all a QA team has time for.

Analyzing every call with AI removes the time limit. But the real change is not that you review more calls. It is that you stop reasoning from a sample at all.

The arithmetic of small samples

A random sample is a good tool for estimating something common, such as the average handle time or the share of calls about billing. It is a poor tool for finding something rare, and the most important events in a contact center are rare.

Take an illustration. A center with 50 agents handles 20,000 calls a month, and QA reviews 4 calls per agent, 200 calls in total. Suppose a serious compliance slip happens in 1 call out of 200. Across the month, that is about 100 calls with the slip. The QA sample will contain about one of them. For any single agent, the chance that one of their 4 reviewed calls contains the slip is about 2%.

Illustration: 20,000 calls a monthQA sample (200 calls)Every call
Calls with a 1-in-200 compliance slipAbout 1 foundAbout 100 found
Chance of seeing it for a given agentAbout 2%Every occurrence
Time to notice a new issueWeeks, if everThe same day
Chance that one agent's reviewed calls include a 1-in-200 slip For an agent with 400 calls a month and a slip in 1 call out of 200: reviewing 4 calls gives about a 2% chance, 20 calls about 10%, 100 calls about 39%, and all 400 calls about 86%, which is the chance the agent had any slip that month. Chance the reviewed calls include a slip, for one agent 4 calls reviewed2% 20 calls reviewed10% 100 calls reviewed39% All 400 calls86%, every slip found
Illustration: 400 calls per agent per month and 1 slip in 200 calls, so the chance is 1 − 0.995n for n reviewed calls. When every call is read, the remaining 14% are months in which that agent had no slip at all.

The sample is not wrong. It is simply answering a different question: “what is typical?” rather than “what happened?”.

1. Rare events stop being invisible

When every call is read, rare events become lists: every churn risk, every possible defect, every promise to call back, each with the sentence that shows it. The question changes from “did we happen to hear it?” to “who owns this, and by when?”

In VoiceVera's public showcase of 873 calls, full coverage produced 97 possible product defects, 25 churn risks, 15 feature requests and 14 questions the business had no ready answer for. Most of those categories would be close to empty in a typical sample. See Churn signals in customer calls for what to do with one of these lists.

2. QA moves from listening to deciding

If software reads every call, QA analysts no longer spend their days finding calls to listen to. Their time goes to the calls that need a human: findings with thin evidence, decisions where two independent passes disagree, disputed scores and calibration. That is skilled work, and it is a better use of the people who know your standards best.

The team's output changes too. Instead of a monthly score sheet, QA owns the scorecard itself, the rules that decide what goes to review, and the quality of the lists other teams act on.

3. Agents get fairer scores, if they can see why

Agents often distrust QA because a score from three calls can hinge on one bad day. Scoring every call smooths that out, but only if agents can see the reasons. A score with no evidence just moves the argument from “you picked a bad call” to “the machine got it wrong”.

The answer is to tie every point to the moment in the call and let agents dispute it. Score objective behavior, such as whether a required step was taken, and leave mood and personality out of it. Compare agents who take similar calls, not everyone against everyone. Our guide to building a scorecard AI can score fairly goes through this item by item.

4. Coaching gets specific

With every call scored, a team lead can find the three calls this week where an agent missed the same step, and the three where they handled it well, and play the moments side by side. Coaching moves from “try to be more thorough” to “here is the sentence, here is what good sounds like”. Clips from real calls are also better training material than scripted examples.

With every call analyzed, “customers are complaining about delivery” becomes a number by day, by queue and by topic, compared with last month. A spike can be caught the same day instead of in next month's review. And because each number comes from individual calls, any trend can be opened up to the calls behind it.

Contact reasons improve as well. Disposition codes chosen by agents at the end of a call are often rushed or inconsistent. Topics read from the conversation itself are more consistent and can be changed later without re-coding history by hand.

6. You need rules for when to ask a human

Reading every call also means the AI will sometimes be unsure or wrong. A sample hides this; full coverage exposes it. So you need explicit rules for sending calls to review, based on evidence rather than the model's self-reported confidence, and a way to correct results without erasing the original. Our article on evidence for AI findings covers how.

What doesn't change

  • Someone still defines quality. The scorecard and the topics are your decisions, not the software's.
  • Calibration still matters. Now it is calibration between people and the system, done on a labelled sample.
  • Numbers will shift. Full coverage usually shows more issues than the sample did. Prepare leadership for this before the first report, so better visibility is not mistaken for worse performance.

How to start

  1. Start with a few hundred recent calls, not a full rollout.
  2. Agree on your topics and scorecard before you look at results.
  3. Label a small set by hand and compare, to tune the review rules.
  4. Pick two or three lists to act on first, such as follow-ups and churn risks, each with an owner.
  5. Share the evidence with agents from day one.
  6. Keep part of the manual sample for the first month, to compare.

That is how a VoiceVera pilot runs. For a fuller 90-day plan, see Call center quality assurance with AI.

Daily trends of calls by topic and outcome.
VoiceVeraTrends computed by code from every call, not from a sample.