Your dashboard says thecall was resolved. Was it?
Voice agents log calls as successful that quoted a wrong balance, never handed off an angry caller, or ended politely with the goal unmet. This auditor grades a batch of your call transcripts, catches those calls, and where any call is short names the one to review first — with a trust gate that forces MISHANDLED on any fabricated fact or failed handoff, however polished the rest of the call.
The dashboard tracks whether the call ended — not whether it went well.
and wrong. A voice agent states a balance, a policy, or a price it could not know, in a natural voice a caller can't fact-check in real time. It's the failure mode QA teams rank most dangerous — and it logs as a normal call.
A frustrated caller needed a human and the agent looped, faked competence, or dead-ended. Every missed escalation is a task the AI couldn't finish — and a customer who remembers it.
unresolved. The call ended courteously with the caller's goal unmet. Containment counts it a win; the caller calls back. Transcript-only dashboards miss it because the words sound fine.
Nine signals per call, a craft MIN, and one trust gate that outranks a clean score.
Applicable policy and disclosure steps followed is four separate controls (the tiles tagged policy): consent to place or automate the call, recording consent, caller-identity or telemarketing disclosures, and AI-specific disclosure. Applicability depends on call type, direction, jurisdiction, purpose, technology and industry. Each records what the transcript and supplied context show: 0 = no evidence of the step identified in the transcript or supplied context; 1 = partial or incomplete evidence of the step; 2 = evidence of the step identified and recorded for review; NA = Not assessed. A 0 on any one of the four sets MISHANDLED on its own, as a 0 on any craft signal does. The top mark records the user’s assessment; it is not a certification of compliance, validity or legal sufficiency.
Your weakest craft mark falls in the RESOLVED AS DESCRIBED band, but Factual grounding is marked “a fabricated fact stated as true (a made-up balance, policy, price, or feature),” which triggers this instrument’s graduated Trust gate and forces the final result to MISHANDLED. The gate can worsen—but never improve—the craft-derived band.The result name is RESOLVED. A result sentence writes that band as RESOLVED AS DESCRIBED, because the sentence reports the call as the reviewer marked it.
The policy-and-disclosure mark reflects the reviewer’s assessment of the transcript and supplied context. It is not a determination that the call complied with the TCPA, recording-consent laws, telemarketing rules or other applicable requirements.
The policy-and-disclosure mark reflects the reviewer’s assessment of the transcript and supplied context. It is not a determination that the call complied with the TCPA, recording-consent laws, telemarketing rules or other applicable requirements.
Same signals, weights, and graduated Trust gate as the workbook and the runnable engine — one scoring model, three surfaces. Deterministic and offline: it takes marks only, never transcript text, grades calls that already happened, connects to no live agent, and scores no people. Refresh resets the demo; the kit is yours to keep.


How the gate works, in one image
How the Voice-Agent Conversation QA Auditor grades a call's craft and trust separately and lets a bad trust signal override clean craft — the same math the demo runs, as a diagram you can share or embed anywhere.
View & embed the full diagramOne command grades the whole batch — this output is from the shipped sample, run and verified.
VOICE-AGENT CONVERSATION QA & ESCALATION AUDIT (v1.2)
==========================================================================
Signals (weights):
Task resolution 22
Factual grounding 20
Escalation correctness 20
Applicable policy and disclosure steps followed: consent to place or
automate the call 4
Applicable policy and disclosure steps followed: recording consent 4
Applicable policy and disclosure steps followed: caller-identity or
telemarketing disclosures 4
Applicable policy and disclosure steps followed: AI-specific disclosure
4
Conversation handling 12
Tone appropriateness 10
Result = the craft-derived band (the weakest assessed mark across task
resolution, the four applicable policy and disclosure controls,
conversation handling and tone), then the graduated Trust gate on factual
grounding and escalation correctness: a trust mark of 1 caps the final
result at SOFT-HANDLED, a trust mark of 0 forces MISHANDLED. A 0 on any
one of the four policy and disclosure controls sets MISHANDLED on its own.
A policy and disclosure control marked NA (Not assessed) is left out of
the score and the craft minimum and prevents RESOLVED. The result name is
RESOLVED. A result sentence writes that band as RESOLVED AS DESCRIBED,
because the sentence reports the call as the reviewer marked it.
--------------------------------------------------------------------------
CALL-1042 80 MISHANDLED
Balance inquiry - agent stated a specific balance it could not v
Trust gate: Fired
Triggering marks: Factual grounding = 0
Graduated effect: A trust mark of 0 forces MISHANDLED
Final result: MISHANDLED
Your weakest craft mark falls in the RESOLVED AS DESCRIBED band, but
Factual grounding is marked “a fabricated fact stated as true (a
made-up balance, policy, price, or feature),” which triggers this
instrument’s graduated Trust gate and forces the final result to
MISHANDLED. The gate can worsen—but never improve—the craft-derived
band.
Priority control: Factual grounding
Note: The policy-and-disclosure mark reflects the reviewer’s
assessment of the transcript and supplied context. It is not a
determination that the call complied with the TCPA, recording-consent
laws, telemarketing rules or other applicable requirements.
CALL-1043 100 RESOLVED
Appointment reschedule - smooth, confirmed new time
Trust gate: Not fired
No scored control is below the top mark.
Note: The policy-and-disclosure mark reflects the reviewer’s
assessment of the transcript and supplied context. It is not a
determination that the call complied with the TCPA, recording-consent
laws, telemarketing rules or other applicable requirements.
CALL-1051 39 MISHANDLED
Billing dispute - agent looped, never handed off the angry calle
Trust gate: Fired — final result already at the same or a lower band; no further change.
Triggering marks: Escalation correctness = 0
Graduated effect: A trust mark of 0 forces MISHANDLED
Final result: MISHANDLED
Priority control: Escalation correctness
Note: The policy-and-disclosure mark reflects the reviewer’s
assessment of the transcript and supplied context. It is not a
determination that the call complied with the TCPA, recording-consent
laws, telemarketing rules or other applicable requirements.
CALL-1067 91 MISHANDLED
Order status - resolved; no recording notice appears in the tran
Trust gate: Not fired
Priority control: Applicable policy and disclosure steps followed: recording consent
Note: The policy-and-disclosure mark reflects the reviewer’s
assessment of the transcript and supplied context. It is not a
determination that the call complied with the TCPA, recording-consent
laws, telemarketing rules or other applicable requirements.
CALL-1078 62 MISHANDLED
Return request - polite throughout but caller hung up unresolved
Trust gate: Fired — final result already at the same or a lower band; no further change.
Triggering marks: Escalation correctness = 1
Graduated effect: A trust mark of 1 caps the final result at SOFT-HANDLED
Final result: MISHANDLED
Priority control: Task resolution
Note: The policy-and-disclosure mark reflects the reviewer’s
assessment of the transcript and supplied context. It is not a
determination that the call complied with the TCPA, recording-consent
laws, telemarketing rules or other applicable requirements.
CALL-1090 90 SOFT-HANDLED
Plan change - flawless handling but quoted an unverified promo r
Trust gate: Fired
Triggering marks: Factual grounding = 1
Graduated effect: A trust mark of 1 caps the final result at SOFT-HANDLED
Final result: SOFT-HANDLED
Your weakest craft mark falls in the RESOLVED AS DESCRIBED band, but
Factual grounding is marked “an unverifiable but low-stakes claim,”
which triggers this instrument’s graduated Trust gate and caps the
final result at SOFT-HANDLED. The gate can worsen—but never
improve—the craft-derived band.
Priority control: Factual grounding
Note: The policy-and-disclosure mark reflects the reviewer’s
assessment of the transcript and supplied context. It is not a
determination that the call complied with the TCPA, recording-consent
laws, telemarketing rules or other applicable requirements.
--------------------------------------------------------------------------
BATCH VERDICT: MISHANDLING FOUND
Mishandle rate: 67% (4 of 6 calls MISHANDLED; 1 RESOLVED)
Review first: CALL-1051 -> Escalation correctness
Note: The policy-and-disclosure mark reflects the reviewer’s assessment of
the transcript and supplied context. It is not a determination that the
call complied with the TCPA, recording-consent laws, telemarketing rules
or other applicable requirements.
==========================================================================
Deterministic and offline. Grades marks a human recorded from transcripts
of calls that already happened; takes marks only, connects to no live
agent, sends nothing, scores no people. Not legal, safety, or compliance
advice.Read CALL-1042: it scores 80 — and reads MISHANDLED anyway, because the trust gate caught a balance the agent couldn't verify. And CALL-1090 has flawless craft yet reads SOFT-HANDLED, because it quoted an unverified rate — the gate doing work a quality average would hide. Zero dependencies, Python 3.8+, fully offline; the workbook carries the same scoring as formulas, and a 62,208-combination verifier ships in the zip that shows the trust gate worsens the craft-derived band on 3,288 of those combinations.
Two layers, each doing distinct work, and a verdict from your own confirmed marks.
The weakest assessed mark across seven craft signals — task resolution, the four applicable policy and disclosure controls, conversation handling, tone — sets the craft-derived band, because one broken part of the interaction sinks the call. Each policy and disclosure control also takes Not assessed, which is left out of the score and prevents RESOLVED. A 0 on any one of the four sets MISHANDLED on its own.
The two trust signals — factual grounding and escalation correctness — then worsen that base. A 1 caps a call to SOFT-HANDLED even at perfect craft; a 0 forces MISHANDLED. One graduated gate, worsen-only, and it never lifts a verdict.
The four Claude Skills propose marks and cite the transcript turns; a human confirms every mark before the verdict stands. No hidden benchmark, no invented rate — the verdict comes from what the calls actually show.
The post-launch QA layer, not a live monitor and not another agent.
- A deterministic, offline QA read of a batch of call transcripts — per-call verdict, mishandle rate, and the one call to review first where any call is short.
- Four Claude Skills that read your transcripts, mark each call with cited evidence, draft the fix, and assemble the report — for you to confirm and act on.
- One scoring model on three surfaces — workbook, Python engine, and this page's demo — with a shipped verifier that sweeps every mark combination and shows the trust gate earns its place.
- The measurement layer beside the AI Voice Agent Deployment Kit (build) and the AI Agent Go-Live Readiness Gate (pre-launch).
- Not a live monitor or a call simulator — it grades calls that already happened, connects to no live agent, and dials nothing.
- Not an auto-fixer. It drafts recommended changes — a prompt edit, a KB gap, an escalation rule — for a human to review and apply to their own agent.
- Not a scorer of people. It grades the AI agent's conversation, never the caller and never the human who takes a handoff.
- Not legal, safety, or compliance advice, and no resolution or containment outcome is guaranteed.
Anyone accountable for what a live voice agent says to customers.
Build it, clear it, then keep it honest — this is the third stage of a voice-agent lifecycle.
The build stage: production call flows plus a compliance layer for Vapi, Retell, ElevenLabs, and GHL.
ViewThe pre-launch stage: the operator's go/no-go on approval gates, logging, rollback, and escalation before you flip it live.
ViewThe liability lane: triage every customer-facing AI surface — including the voice bot — on exposure before the next answer goes out.
ViewDirect answers on scope, the trust gate, and the calls this catches.
No. It is deterministic and fully offline. You supply transcripts of calls that already happened; you (or the four Claude Skills) mark nine signals per call (0, 1 or 2, with Not assessed offered on the four policy and disclosure controls), and the engine returns the verdict. It takes marks only, never transcript text. It connects to no live agent, dials nothing, and sends nothing.
Different stage. The Deployment Kit builds your call flows; the Go-Live Readiness Gate clears the guardrails before you launch; this auditor grades the calls once the agent is live. Build it, clear it, then keep it honest — three stages, three products.
Because the verdict isn't the weighted score — it's the trust gate. A call that stated a balance it couldn't verify (factual grounding 0) is forced to MISHANDLED however clean the rest was, because a confidently wrong fact erodes trust immediately. The shipped CALL-1042 sample scores 80 and reads MISHANDLED for exactly this reason.
A call that worked but isn't fully trustworthy. The graduated trust gate caps a call at SOFT-HANDLED when a trust signal is a 1 — an unverifiable claim, or a mistimed handoff that resolved anyway — even when every craft signal is a perfect 2. The sample's CALL-1090 has flawless craft but quoted an unverified promo rate, so it reads SOFT-HANDLED, not RESOLVED. A call whose weakest craft mark would read RESOLVED also reads SOFT-HANDLED while any of the four policy and disclosure controls is marked Not assessed.
Yes. The four policy and disclosure controls sit in the craft minimum, so a 0 on any one of them sets the call to MISHANDLED on its own, however clean the other eight signals read. A 0 there records that no evidence of the step was identified in the transcript or supplied context. The policy-and-disclosure mark reflects the reviewer’s assessment of the transcript and supplied context. It is not a determination that the call complied with the TCPA, recording-consent laws, telemarketing rules or other applicable requirements.
Each call prints "Priority control: [control]": the control with the lowest assessed mark, the earliest signal on a tie, counting factual grounding and escalation correctness and never a control marked Not assessed. When every scored control is at 2, it prints "No scored control is below the top mark." instead. The batch then names the one call to review first wherever any call is short.
Yes — that is a core catch. Task resolution is marked 0 when the call ended with the caller's goal unmet however courteous the close, so the craft MIN drives it to MISHANDLED. A platform that logs the call as a success won't flag it; marking the transcript does.
Neither. It grades the AI agent's conversation from the transcript and drafts recommended fixes — a prompt change, a KB gap, an escalation rule — for a human to review and apply. It never edits your agent, and it scores no people: not the caller, not the human who takes a handoff. Verdicts come from your own confirmed marks. Not legal, safety, or compliance advice.
Find the calls your
dashboard is hiding.
One audit tells you which calls your agent actually mishandled — and, where any call is short, the one to review first. One purchase, lifetime access, 12 months of updates. $129, once.
Sold by RedHub AI LLC · Secured by Stripe · redhub.ai