Engineering brief

Voice agent evals: from 33% agreement to 92% in regulated fintech

AI Engineer3 min read · saves 14 min

At a glance

The brief is enough

Relevance
Practical value
Radar
Time horizon
Now
Warnings
None

Upstart launched voice verification calls and found LLM-human agreement at 33%. Through structured human review loops, they reached 92%.

Voice agents in regulated industries require evaluation infrastructure as a compliance requirement, not a nice-to-have.

Watch if you are deploying voice agents in regulated environments and need a practical eval loop architecture.

Summary

The problem. Upstart handles thousands of regulated lending calls daily. A voice agent automates verification calls for the 10% of applicants not instantly approved. The agent asks three questions about income, fund use, and obligations. But regulatory constraints make even this simple flow complex: if a borrower mentions medical use, the agent cannot ask for an amount. If they mention travel, the agent must clarify whose graduation it is. Compliance violations are not just poor UX but potential regulatory issues.

Manual chaos. Upstart started with a Google Sheet to track human reviews. Within weeks, five columns became ten, then fifteen people added columns randomly. The process became unmanageable. Teams needed structured data to improve both the agent and the review process itself. This drove them to adopt Coval for structured human review and evaluation infrastructure.

Metric evolution. Shiv's team initially tracked many metrics: call time, accuracy, clarity, completeness, policy alignment, escalation correctness, CSAT. Over time they whittled down to what mattered most for their use case. His advice: don't get attached to metrics. Start with what seems logical, then discard what doesn't drive real outcomes.

The agreement gap. Upstart ran an LLM judge on every call to score compliance adherence. Human reviewers then evaluated the judge's output. Initially, human and LLM agreement was only 33%. Three causes emerged: tribal knowledge not encoded in the agent, disagreement among human reviewers themselves, and judge quality issues. Each was addressed systematically, bringing agreement to 92%.

The continuous loop. Brooke described a complete evaluation cycle: define metrics aligned to product definition, monitor live calls at scale, detect known failures and unknown unknowns via clustering, route failures to the right teams (compliance, engineering, agent), re-simulate fixes before production, and ultimately enable a self-healing loop gated by human approval. Every change is behind a feature flag; compliance changes require compliance team sign-off.

Why this matters for regulated AI. The core insight is that evaluation infrastructure is not a nice-to-have but a regulatory requirement when deploying autonomous voice agents at scale. The loop is not about automation replacing humans but about humans focusing on the calls that matter most. Upstart's blueprint shows how to launch AI safely in regulated environments while continuously improving performance.

My take

I appreciate that Shiv explicitly called out the journey from a Google Sheet to structured evaluation. That's the real story most demos skip. The 33% to 92% agreement jump is impressive, but I'd push back on treating 92% as a success threshold. In regulated lending, even 8% disagreement means hundreds of calls per day with potential compliance exposure. The loop is sound, but the metric that matters isn't agreement rate, it's the regulatory risk from the 8% you're not catching. Teams should budget for continuous human review as an operational cost, not a temporary phase.

What to do with this

  1. Run a human-LLM agreement baseline on your current voice agent call logs before making any changes.
  2. Map your compliance requirements into explicit evaluation criteria that an LLM judge can score automatically.
  3. Design a triage system that routes flagged calls to the right team (compliance vs engineering vs agent) with clear SLAs.

Watch the video

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.