TL;DR: Quality assurance (QA) and quality control (QC) are two halves of one quality program. QA is proactive: it sets the standards, processes, and training that prevent problems before they reach a customer. QC is reactive: it inspects the actual work, calls, chats, and emails, to catch problems that slipped through. QA builds the system; QC checks the output. You need both, and in customer service the hard part is QC coverage, because manual inspection only reviews a tiny sample of conversations.
People use “quality assurance” and “quality control” as if they were the same thing. They are not. They answer two different questions. QA asks, “Have we set things up so quality happens by default?” QC asks, “Did quality actually happen in this specific interaction?” One is prevention, the other is inspection.
Below is the difference at a glance, then a deeper breakdown, and finally what QA and QC look like inside a real customer support team, where the gap between the two is widest.
Quality assurance vs quality control: comparison table
| Dimension | Quality assurance (QA) | Quality control (QC) |
|---|---|---|
| Goal | Prevent defects before they happen | Detect defects after work is done |
| Approach | Proactive, preventive | Reactive, corrective |
| Focus | The process and system | The output and result |
| Question it answers | “Is the process set up to produce quality?” | “Does this specific interaction meet the standard?” |
| When it happens | Before and during delivery | During and after delivery |
| Typical activities | Setting guidelines, designing scorecards, training, process design | Reviewing conversations, scoring against the standard, flagging misses, coaching |
| Owner | Cross-functional (ops, training, QA leads) | QA reviewers and team leads/supervisors |
| In customer service | Writing the QA standard and communication playbook | Evaluating tickets and calls against that standard |
The short version: QA is the recipe and the kitchen setup, QC is tasting the dish before it goes out. Now the detail.
What is quality assurance?
Quality assurance is the proactive side of quality management. It is everything you do up front to make good outcomes likely, before a single customer is served. QA is about the process, not the individual result.
In a customer support context, QA activities include:
- Defining clear communication guidelines and tone-of-voice standards for agents.
- Identifying where service is likely to fall short and designing the process to prevent it.
- Building the evaluation framework, the QA scorecard, that defines what “good” looks like.
- Running onboarding and continuous training so agents have the skills to meet the standard.
- Reviewing and updating processes as products and policies change.
Get QA right and quality is designed into the work. Agents know the standard, have the tools to hit it, and the process itself steers them toward the right outcome. QA is preventive by definition: it stops problems from being created in the first place.
What is quality control?
Quality control is the reactive side. Once service is being delivered, QC inspects the actual output to confirm it meets the standard QA defined, and flags the cases that miss. QC is about the result, the specific conversation, not the process.
QC activities in customer service include:
- Regularly evaluating real customer interactions across calls, email, chat, and messaging.
- Scoring each one against the agreed standard and identifying where it fell short.
- Providing feedback and coaching to the agents who need it.
- Tracking quality and satisfaction metrics to measure whether the program is working.
If QA is laying the foundation and writing the requirements, QC is checking that the finished product, the interaction the customer actually experienced, meets those requirements. QA prevents; QC verifies.
The key differences, dimension by dimension
The table above is the fast answer. Here is where the distinction actually matters in practice.
Approach: preventive vs reactive
QA is a preventive approach aimed at anticipating and stopping issues before they arise. By analyzing recurring problems, QA experts fix the process so those problems stop reaching customers at all.
QC is a reactive approach focused on identifying and correcting issues in work that has already happened. Monitoring interactions in real time lets QC catch a miss quickly and course-correct, but the interaction has already occurred. This is the single cleanest way to remember the difference: QA changes the process, QC inspects the product.
Focus: the system vs the output
QA looks at the system that produces quality, the guidelines, the training, the workflow, the scorecard. Improve the system and every future interaction improves. QC looks at individual outputs, one conversation at a time, and asks whether each one hit the mark. Improve via QC and you fix the specific case and coach the specific agent.
Who is responsible?
A common misconception is that one department “owns” quality. It does not work that way.
Quality assurance is a shared, cross-functional responsibility. The standard is shaped by support leadership, operations, training, and often product and policy teams, because quality extends well beyond the front line: an unclear return policy or a confusing product creates bad interactions no agent can fully rescue.
Quality control is usually more concentrated. Many teams have a dedicated QC or QA-reviewer function, and team leads or supervisors frequently run the evaluations day to day. Both functions cost real time and budget, which is exactly why coverage becomes the pressure point (more on that below).
Where each one sits in the customer journey
QA operates across the entire journey:
- Before delivery: creating communication policies, service procedures, and agent training.
- During delivery: observing interactions to spot issues and improvement opportunities early.
- After delivery: analyzing feedback and data to find trends and refine the process for next time.
QC concentrates on the delivery and post-delivery moment: reviewing interactions against the standard, pinpointing where they fell short, and feeding that back into coaching. QA sets the loop up; QC is where the loop is measured.
The metrics each one uses
QA and QC share a measurement layer. The core metrics for a support team, covered in depth in our guide to customer service metrics and KPIs, include:
- QA score / Internal Quality Score (IQS): the percentage of quality points an interaction earns against your scorecard. It is the headline number for both the agent’s performance and the health of the QA/QC system itself. See how the Internal Quality Score works for the calculation.
- CSAT (Customer Satisfaction Score): the customer’s own verdict on whether the interaction met their expectations. Pair it with your QA score to separate “the customer was unhappy” from “we performed below standard.”
- Dispute rate: how often agents contest evaluations, a signal of both scorecard fairness and reviewer consistency.
- Average resolution time: whether the speed-versus-quality balance is right, watched alongside reopen rate so fast-but-poor answers get caught.
QA vs QC beyond the factory floor
Most explainers define QA and QC using manufacturing: QA designs the assembly line, QC inspects the widgets coming off it. The logic transfers cleanly to customer service, with one important twist. A widget is a physical object you can pull off the line and inspect. A customer conversation is an event that happened once, in the moment, and then it is gone unless you capture and review it.
That twist is why QC is the harder half in support. In a factory you can inspect every unit if you are willing to pay for it. In customer service, “inspecting the units” means reading and scoring conversations, and that is where the traditional model quietly breaks down.
How QA and QC work together in a support team
QA and QC are not competing approaches, they are a loop. QA defines the standard and equips the team. QC measures reality against that standard. The findings from QC feed back into QA, which updates the process, retrains, and adjusts the scorecard. Round and round.
The loop only works if QC actually sees what is happening. And here is the uncomfortable math: a typical QC process reviews three to five tickets per agent per week, under 5% of all conversations. Your quality score, the number leadership sees, describes that thin slice. The other 95% is never inspected.
Small samples fail in two ways. They are statistically noisy, one bad conversation can swing an agent’s score, and they are biased, because reviewers tend to pull easy-to-find or already-flagged tickets, so quiet failures never enter the sample. You end up coaching variance instead of performance, and QA never learns about the process gaps hiding in the unreviewed 95%.
Closing the QC coverage gap with AI auto-QA
The structural fix is to stop sampling. AI-based auto-QA evaluates every conversation against your scorecard instead of a handful. Kaizo’s AutoQA scores conversations automatically, and its Autopilot mode runs continuously in the background, so QC coverage stays at 100% without anyone triggering reviews. QC stops being a sample and becomes a census. That turns your quality score from an estimate into a measurement, and it gives QA a complete, unbiased view of where the process actually breaks.
The results at real accounts are concrete. UiPath reached near-100% QA automation and cut its QA team size by 82% while quality scores climbed roughly 8% per quarter. EverHelp automates about a third of its scorecards across 16 support domains and cut coaching-prep time by 75%. Automation is a dial you turn up over time, not an all-or-nothing switch: teams keep human review where genuine judgment is required, and let the engine handle the volume. Purpose-built QA software is what makes 100% coverage practical rather than aspirational.
Neutral by design: QC in the AI-agent era
There is a new wrinkle. As support teams deploy AI agents to handle conversations, someone has to run QC on those AI agents too. Most QA vendors now sell their own AI agents, which means grading their own homework. Kaizo does not sell AI agents, so it can evaluate any conversation, human or AI, without that conflict of interest. As your center becomes a mix of human and AI agents, a neutral quality-control layer is the only one you can trust to score both honestly.
How to build a QA and QC system for customer service
You do not need a heavy program to start. You need the loop, running reliably.
- Define roles and quality gates. Write down who owns the QA standard and who runs QC evaluations, and set checkpoints at the key stages of service delivery so quality is checked, not assumed.
- Define what “good” means, concretely. Turn your business goals into a measurable standard. A customer service QA checklist is the fastest way to draft the criteria, grouped into case handling, communication, compliance, and resolution.
- Build the scorecard and weight it. Not every miss is equal: a typo costs a point, a data-privacy breach should fail the whole evaluation. Build the weighting into your QA scorecard so the score reflects real risk.
- Evaluate consistently and calibrate. Two reviewers scoring the same conversation should land on the same result. Regular calibration is what turns QC from opinion into measurement.
- Turn findings into coaching. Scores do not improve anyone, coaching does. Tie every evaluation to specific conversations and feed it into a steady customer service coaching rhythm. Kaizo generates coaching cards straight from QA data, so managers coach from evidence instead of compiling reports.
- Push coverage up. Start where you are, then raise QC coverage toward 100% with automation so your quality score reflects reality, not a sample.
Frequently asked questions
What is the difference between quality assurance and quality control?
Quality assurance is proactive and process-focused: it sets the standards, training, and workflows that prevent problems before they happen. Quality control is reactive and output-focused: it inspects the actual work, the conversations, to catch problems that got through. QA builds the system; QC checks the result. You need both.
Is quality assurance the same as quality control?
No. They are complementary but distinct. QA prevents defects by improving the process; QC detects defects by inspecting the output. A helpful shorthand: QA is “are we doing the right things?”, QC is “did we do them right this time?”
What is an example of quality assurance vs quality control in customer service?
QA is writing the communication playbook, building the scorecard, and training agents on how to handle a refund request. QC is reviewing a specific refund conversation afterward, scoring it against that standard, and coaching the agent if it fell short. QA sets the expectation; QC verifies it was met.
Which comes first, QA or QC?
QA comes first. You cannot control quality against a standard that does not exist yet. QA defines the standard and sets up the process, then QC measures real interactions against it. The findings from QC then loop back to improve QA.
How do you measure QA and QC in a support team?
Track an Internal Quality Score (the percentage of quality points earned against your scorecard) as the core measure, paired with CSAT for the customer’s view, plus dispute rate and resolution time. The most honest number of all is your coverage rate: the share of conversations QC actually reviews. Manual review rarely clears 5%; AI auto-QA pushes it to 100%.
The bottom line
Quality assurance and quality control are not rivals or synonyms, they are the two halves of one loop. QA prevents problems by designing the system; QC catches them by inspecting the work. Great customer service comes from running both continuously and honestly, which means being clear-eyed about the one place the model usually breaks: QC coverage. A quality score built on 5% of conversations is a guess. Built on 100%, it is the truth.
If you want to see quality control at 100% coverage, scored automatically and turned into coaching, book a demo and we will run it on your own conversations.
