Comparison
EchoDepth vs Manual QA
for vulnerable customer identification.
Manual QA is a sampling process. FCA Consumer Duty requires proactive identification. These two things are not compatible — and the FCA knows it.
of interactions reviewed by
manual QA processes
of interactions assessed
by EchoDepth
Head to head
| Capability | Manual QA | EchoDepth |
|---|---|---|
| Interaction coverage | 2–3% (sample) | 100% |
| Vulnerability flag timing | Hours or days post-interaction | Real-time, during interaction |
| Detects suppressed distress | Rarely — reviewer sees surface | Yes — involuntary signal |
| Consistency | Variable — reviewer dependent | Consistent signal thresholds |
| FCA audit trail | Incomplete (97% unreviewed) | Full interaction-level log |
| Outcomes monitoring MI | Manual compilation | Automated, continuous |
| Scales with interaction volume | Requires proportional headcount | Linear API cost only |
| FCA proactive ID requirement | Does not satisfy | Satisfies |
EchoDepth doesn't replace compliance staff. It changes what they do.
Manual QA reviewers are skilled professionals. The problem isn't their capability — it's the coverage constraint. A team of five reviewers cannot listen to 50,000 calls a month. They review 1,500 and call it QA.
EchoDepth screens all 50,000. It flags the 800 that show vulnerability signals requiring review. Your five reviewers now spend their time on the interactions that matter — with full context from the signal data — rather than sampling randomly and hoping the vulnerable interactions are in the 3%.
The compliance team gets better, more targeted work. Coverage goes to 100%. The FCA gets a complete audit trail. The outcome is better for everyone — including the customers who were in the 97% that manual QA never reached.