Most contact centres review a small fraction of their calls. A QA analyst picks a handful, scores them, flags what went wrong, and then moves on. It feels like it ticks the box for quality assurance. But for Ofcom-regulated telecoms operations and FCA-regulated financial services firms, it’s not enough, and the consequences of getting it wrong have never been higher.

This article explains why call sampling creates compliance exposure, what always-on monitoring looks like in practice, and what to look for when evaluating your current approach.

What is call quality monitoring?

Call quality monitoring is the process of reviewing agent-customer interactions to assess whether they meet your quality, compliance, and performance standards.

It typically covers:

  • What was said and how the agent handled the conversation
  • Whether compliance scripts and protocols were followed
  • How vulnerable customers were identified and managed
  • Whether the outcome was appropriate for the customer
  • How performance compares against your scoring framework

When call quality monitoring is done consistently, it gives you a documented evidence-base across every call type, agent, and campaign. But when it’s done poorly or too infrequently, it leaves gaps that regulators are increasingly likely to find before you do.

How do most contact centres currently monitor calls?

Sampling is the typical approach many call centres take to monitoring calls. A QA reviewer listens to a set number of calls per agent per month, scores them against a framework, and feeds the results back into coaching. It is time-consuming work, so let’s break down the numbers.

Example:

  • A single reviewer handles 50 calls a month at 30 minutes per call.
  • This amounts to 25 hours of review time.
  • And it is still only a fraction of the total call volume reviewed.

The problem here is not the effort; it's the coverage. On average, contact centres manually evaluate 5% of calls per week, meaning many QA operations are leaving the majority of interactions unreviewed. This means:

  • You don’t know whether your agents are consistently identifying vulnerable customers.
  • You don’t know whether compliance scripts are being followed on the calls you did not pick.
  • You are not building an evidence bse, only a small sample.
Manual call sampling statistics

FCA Consumer Duty: you need evidence across every interaction, not a snapshot

For debt collection, insurance, and other FCA-regulated contact centres, the stakes are different but the problem is the same. Consumer Duty requires firms to demonstrate they are delivering good outcomes for retail customers, not just on the calls they reviewed, but consistently and measurably across their entire operation.

The FCA has shifted decisively from implementation to enforcement. Regulators are no longer asking whether you have a quality monitoring process. They are asking whether you can prove, with documented evidence, that your agents are handling vulnerable customers correctly, following compliant scripts, and not causing foreseeable consumer harm. And that’s for every call, not just the ones you checked.

A sampling approach does not produce that evidence. It produces a snapshot.

For more on what the FCA now expects from contact centres in financial services and debt collection, see our Consumer Duty guide.

The problem with call sampling: A Summary

  • Sampling typically covers around 5% of calls per week, leaving the 95% of interactions unreviewed and unverifiable
  • Compliance drift happens slowly. By the time sampling catches a behaviour, it is already established and harder to coach out
  • Poor agent behaviour on outbound calls can go undetected long enough to trigger carrier blocking or an FCA flag
  • Vulnerable customers may not be identified correctly on calls you never reviewed
  • Good performance goes unrecognised as you cannot replicate what you cannot see
  • A sample tells you what happened on the calls you chose to review. It does not tell you what is happening in your operation

From sampling to monitoring: what's actually required

Moving from sampling to consistent call monitoring is not simply a matter of reviewing more calls. It requires the right infrastructure in place, and historically, that infrastructure was either too expensive, too time-consuming, or both.

At a minimum, always-on monitoring requires:

  • Call recording across all interactions, not just selected campaigns or call types
  • Transcription that converts voice to text accurately enough to be reviewed and searched at scale
  • A platform that connects recording, transcription, scoring, and reporting in one place rather than across multiple disconnected tools

Without all three, monitoring at scale either falls back on human reviewers (which is where the 25-hours-per-50-calls problem comes back in) or produces data too inconsistent to be useful as a compliance evidence base.

MaxContact's Conversation Analytics brings all of this together in a single platform. Call recording, real-time transcription, and reporting sit alongside each other. This gives your QA team a single place to monitor, review, and evidence what is happening across every interaction, without stitching together multiple tools or managing separate systems.

The reason most contact centres have defaulted to sampling is not because they did not want better coverage. It is because the operational cost of achieving it manually was prohibitive. A team large enough to review every call would cost more than most mid-market operations can justify. But that has changed.

How Conversation Analytics makes always-on monitoring feasible

Conversation Analytics is the platform that makes consistent, always-on call monitoring operationally viable for mid-market contact centres.

Rather than relying on a QA team to manually select, listen to, and score calls, Conversation Analytics connects call recording, transcription, scoring, and reporting in a single platform – automating quality assurance. Every interaction is captured, transcribed, and made reviewable, giving your QA team complete visibility across all call types, all agents, and all campaigns without the resourcing overhead of manual review at scale.

The cost comparison is significant. Replicating meaningful call coverage with human reviewers alone would cost an estimated £14,000 per month in analyst time for a mid-sized contact centre. Conversation Analytics delivers that coverage at a fraction of the cost, freeing your QA team to focus on coaching, calibration, and the complex calls that genuinely need a human eye.

How AI call monitoring surfaces insights faster

AI is what makes the insights from always-on call monitoring actionable rather than overwhelming.

Without AI, full call coverage creates a different problem; more data than a QA team can meaningfully review and act on. AI-powered call monitoring solves that by doing the heavy lifting on routine scoring, so your team's attention goes where it matters most.

Benefit What it means for your operation
Structured scorecards answered automatically Every scorecard question is answered using transcript evidence; no manual listening, no reviewer subjectivity.
Transcript-linked evidence Every score links back to the exact exchange that informed it, giving you a defensible audit trail.
Faster review cycles Review time drops from 30 minutes to 5 minutes per call, recovering around 4 days of analyst time every month.
Consistent scoring across your entire operation The same criteria, applied the same way, across every agent, call type, and campaign every time.
Human oversight built in Your QA team reviews outputs, calibrates scoring, and focuses on complex calls. AI handles the routine. Governance stays with your team.

The result is not just faster QA. It is a more reliable, more defensible evidence base built on every call, not a sample of them.

What to look for in your call quality monitoring approach

Is your evidence transcript-linked? Generic summaries are not a defensible evidence base. Scoring decisions need to be traceable back to what was actually said.

Is your scoring consistent? If different reviewers score the same call differently, your evidence has a credibility problem. Consistent scoring logic applied across all interactions removes that subjectivity.

Does your QA sit within your analytics platform? If scoring, feedback, and reporting live in separate tools, you create friction and risk. Everything should be in the same place.

Is human oversight built in? Your QA team should be able to review, challenge, and calibrate outputs. Always-on monitoring supports human-led governance, it does not replace it.

Are you scoring the right calls? Configurable triggers and criteria by call type, queue, campaign, or outcome, mean your monitoring effort goes where the compliance risk is highest.

The question is not whether you can afford to monitor every call

It is whether you can afford not to.

Ofcom and the FCA have both made clear that evidence of compliance needs to be consistent, documented, and demonstrable. A sampling process may satisfy an internal audit. It is unlikely to satisfy a regulator asking for proof of good outcomes across your entire customer base.

Always-on call quality monitoring closes that gap. It gives your QA team better data, gives your compliance function defensible evidence, and gives your operation a consistent view of what is actually happening on the phones across all calls, rather than just the ones you happened to pick.

Download the UK Contact Centre Regulatory Guide 2025–2027 to see how the FCA and Ofcom compliance obligations facing your sector map to your call monitoring approach and what good evidenced practice looks like in both.