You Are Asking the Wrong Question
Every QA leader eventually lands on the same question: how many calls should we evaluate? The debate usually stalls between two extremes. One call per agent per week, because that is all the team can handle. Or 100% coverage, because anything less feels like guessing. Both answers are wrong because they start from the wrong place.
The question is not how many calls to review. The question is what you are trying to learn. Until that is answered, any number you pick is arbitrary.
Two Problems Disguised as One
QA volume conversations collapse because people treat “how many” as a single problem. It is not. There are two distinct purposes that require different approaches to volume.
The first is global trend analysis. When you need to understand what is happening across a contact center, you are looking for patterns at scale. Objection frequency, script adherence, training adoption, common failure points. This is a data problem. Statistical sampling works here, and it works efficiently.
Take a hospitality client handling 300,000 sales calls per month across 700 agents. If the goal is to identify the top objection reasons in order of frequency, standard statistical formulas tell you that roughly 1,800 evaluated calls give you 99% confidence with a 3% margin of error. That is less than 1% of total volume. For center-wide trends, you do not need to listen to everything. You need a sample that is large enough to be reliable.
The second purpose is individual agent development. This is where the math breaks down and the work actually starts.
Where the Math Breaks
Run that same statistical formula at the agent level for someone handling 1,000 calls per month, and it tells you to evaluate roughly 700. That is operationally absurd. But the formula is not wrong. It is answering a question that does not apply.
Statistical significance matters when you are measuring a population. An individual agent is not a population. You are not trying to achieve confidence intervals on their performance. You are trying to see how they work.
Go back to the 300,000 calls. Those 1,800 evaluations that work for global trends only give you about 3 per agent for the month. That is a point-in-time snapshot. It tells you almost nothing about whether an agent is consistent, improving, or falling into a pattern that needs correction.
A BPO I worked with said they needed to audit 30% of all calls for meaningful individual-level sampling. At 300,000 calls, that is 90,000 evaluations, roughly 128 per agent per month. Whether or not that exact number is achievable, the logic is sound. Agent-level insight requires more depth per person than center-level insight requires breadth across the population.
What Agent-Level QA Actually Needs
For individual agents, the goal is behavioral. You are looking for patterns that tell a story. How they build rapport. How they handle objections. How they recover when a customer pushes back. You do not need hundreds of calls to see that. You need enough to recognize consistency or spot a coaching opportunity.
One call per week is not enough. It gives you a single moment with no context around it. You cannot tell if what you heard is typical or an outlier. Every call is not the answer either, unless you have a system that can process that volume and surface what matters. Reviewing everything without a way to act on it is just counting.
The right number lives somewhere in between, and it depends on what you are trying to do with what you find. The volume question only makes sense after you have answered the purpose question.
The Real Divide
This is what most QA programs miss. They set a single evaluation target, apply it uniformly, and wonder why the results feel thin. Three evaluations per agent per month checks a compliance box. It does not drive coaching. It does not reveal behavior change. It does not tell a supervisor what to work on next.
The organizations that get this right separate the two purposes cleanly. They run lean, statistically valid audits for center-wide visibility. And they invest in deeper, more frequent evaluation at the agent level to fuel real development.
Where FiveLumens Fits
This is the problem FiveLumens was built around. Not replacing human judgment with AI-scored volume, but closing the gap between what you can evaluate and what you can act on.
The platform handles the scale problem so teams can focus on the insight problem. It makes higher-volume evaluation operationally realistic without pretending that 100% automated QA replaces the need for human coaching decisions. The data gets you to the conversation. The conversation is still where growth happens.
Math works for audits. Insight works for agents. The question is not how many calls to review. It is what you plan to do with what you find.