For GHL & ElevenLabs voice operators

Your dashboard says the call went fine.This catches the phantom booking it missed.

Run a whole week of voice-agent calls through one deterministic pipeline. It scores every call from your own marks, forces the polished call built on a false confirmation to ESCALATE NOW, rolls up your containment and booking, names the one call to review first where any call is short, and exports the flags straight into GoHighLevel.

Get the Pipeline — $129one-time · instant download · yours to keep
Five deliverables · runnable
Runnable Python pipeline
stdlib
Workbook that reproduces it
xlsx
GoHighLevel field export
csv
QA marking playbook
docx
Fix & re-audit runbook
docx
Works alongside
Conversation QA Auditor · Voice Agent Deployment Kit · Chat & SMS Concierge
01.The Problem

The worst voice-agent call looks great on the dashboard.

TCPA
The TCPA permits statutory damages of up to $500 per violation, and a court may increase damages to as much as $1,500 for a willful or knowing violation. Whether a particular call involves one or more violations depends on the facts and claims.
95/100
the sample call that still reads ESCALATE NOW — a false confirmation
1 gate
false confirmation or dropped handoff, dispositive, worsen-only
02.See It Work

Grade a call. Watch the keystone gate override the score.

Grade one call · CALL-3002
Call-quality signals · 0 failed / absent · 1 partial / weak · 2 clean / correct
Grounded answeringkeystone
Escalation correctnesskeystone
Task resolution
Conversation handling
Tone
Call-record controls · mark what the call record shows · NA = not assessed
Permission or other basis to place the callEvidence identified and recorded for review
Recording consent or recording-law assessmentEvidence identified and recorded for review
Caller or business identity disclosureApplicability documented, and applicable disclosure content, timing, and delivery evidence are recorded
AI-generated/artificial-voice disclosure, where applicableApplicability documented, and applicable disclosure content, timing, and delivery evidence are recorded

Each of the four call-record controls is marked on its own evidence. A mark on one says nothing about the other three. A control marked NA is left out of the score and is never counted as a failed control. While any of the four is NA, a call cannot read CALL RECORD CONTROLS PRESENT AS DESCRIBED; it reads NEEDS EYES. The top result also requires that none of the four call-record controls is marked 0; with one at 0 the result is NEEDS EYES. A top mark records the user’s assessment; it does not certify compliance with TCPA, recording-consent, AI-disclosure, or sector-specific law.

95/100
ESCALATE NOW
Keystone gate · Fired—changed result
Trigger checks · False confirmation detected: yes; Required escalation did not fire: no

Your score falls in the CALL RECORD CONTROLS PRESENT AS DESCRIBED band, but False confirmation is marked On, which triggers this instrument’s Keystone gate and forces the final result to ESCALATE NOW. The gate can worsen—but never improve—the score-derived band.

This result is based only on user-supplied marks. RedHub did not review the recording, transcript, consent evidence, disclosure, or applicable law. The result does not determine whether the call was lawful or whether any notice or consent requirement was satisfied.

This week · 3/8 escalate · escalate share 37.5%CONTROL GAPS OPEN

Toggle “False confirmation” on this 95/100 call: a call your dashboard loved is forced to ESCALATE NOW, because it told the caller something before verifying it. The score never earns its way out of the gate.

Diagram of the Post-Call Intelligence Pipeline: nine signals and a 95/100 call forced to ESCALATE NOW by the keystone gate.
Shareable diagram

How the gate works, in one image

How the Post-Call Intelligence Pipeline turns 9 signals (5 call-quality signals and 4 call-record controls) and one keystone gate into one verdict — the same math the demo runs, as a diagram you can share or embed anywhere.

View & embed the full diagram
03.The Runnable Engine

One command grades the week and writes the GHL export.

The same verdicts you see in the demo come from a zero-dependency Python pipeline you run on your own call log. Here is its actual output on the shipped eight-call sample:

POST-CALL INTELLIGENCE PIPELINE - WEEKLY RUN  (v1.1.0)
============================================================================

PER-CALL VERDICTS
----------------------------------------------------------------------------
CALL-3001   100/100  CALL RECORD CONTROLS PRESENT AS DESCRIBED
            Keystone gate: Clear
CALL-3002    95/100  ESCALATE NOW
            Keystone gate: Fired—changed result
            Trigger checks: False confirmation detected: yes; Required
            escalation did not fire: no
            Your score falls in the CALL RECORD CONTROLS PRESENT AS
            DESCRIBED band, but False confirmation is marked On, which
            triggers this instrument’s Keystone gate and forces the final
            result to ESCALATE NOW. The gate can worsen—but never
            improve—the score-derived band.
CALL-3003    95/100  CALL RECORD CONTROLS PRESENT AS DESCRIBED
            Keystone gate: Clear
CALL-3004    85/100  ESCALATE NOW
            Keystone gate: Fired—changed result
            Trigger checks: False confirmation detected: no; Required
            escalation did not fire: yes
            Your score falls in the CALL RECORD CONTROLS PRESENT AS
            DESCRIBED band, but Escalation required is marked On and
            Escalation fired is marked Off, which triggers this instrument’s
            Keystone gate and forces the final result to ESCALATE NOW. The
            gate can worsen—but never improve—the score-derived band.
CALL-3005    73/100  NEEDS EYES
            Keystone gate: Clear
CALL-3006    85/100  NEEDS EYES
            Keystone gate: Clear
            Your score falls in the CALL RECORD CONTROLS PRESENT AS
            DESCRIBED band. However, AI-generated/artificial-voice
            disclosure, where applicable is marked Not assessed. Under this
            instrument’s stated rule, an applicability question that is not
            assessed prevents the top result. Final result: NEEDS EYES.
            Not assessed: AI-generated/artificial-voice disclosure, where
            applicable
            Applicability not assessed — no legal conclusion drawn.
CALL-3007   100/100  CALL RECORD CONTROLS PRESENT AS DESCRIBED
            Keystone gate: Clear
CALL-3008    45/100  ESCALATE NOW
            Keystone gate: Clear

WEEKLY ROLLUP
----------------------------------------------------------------------------
Calls graded ............ 8
ESCALATE NOW ............ 3  (escalate share 37.5%)
Contained end-to-end .... 5 / 8
Booked .................. 4 / 8
Dead-air flags .......... 2
Interruption flags ...... 2
False confirmations ..... 1
Failed handoffs ......... 1
Top coaching theme ...... verify before confirming
Review first ............ CALL-3008

BATCH VERDICT: CONTROL GAPS OPEN

RESULT NOTES
----------------------------------------------------------------------------
On every result above, per call and batch:
  This result is based only on user-supplied marks. RedHub did not review
  the recording, transcript, consent evidence, disclosure, or applicable
  law. The result does not determine whether the call was lawful or whether
  any notice or consent requirement was satisfied.
On every CALL RECORD CONTROLS PRESENT AS DESCRIBED result:
  This result reflects the records and marks supplied by the user. It does
  not determine that the call, recording, disclosure or outreach complied
  with the TCPA, state recording laws or other applicable requirements.
How the top result is reached:
  A score of 75 or more with the keystone gate clear and no call-record
  control Not assessed. The top result also requires that none of the four
  call-record controls is marked 0; with one at 0 the result is NEEDS EYES.

Not legal advice. Voice-agent calling and recording touch TCPA, state
AI-disclosure, and recording-consent rules that vary by state and vertical.
This pipeline grades completed calls from your own marks as an operational
artifact — it scores no person, connects to nothing, and confirms no
compliance status. Confirm your obligations with counsel.
04.The Standard

Three rules the pipeline enforces on every call.

The dashboard grades what it can measure

Your platform marks a call ‘resolved’ when it ends cleanly. It cannot see that the agent confirmed a booking the tool never made. This grades resolution the way a human would — did the caller get what they came for, without being told anything untrue.

One keystone can’t be averaged away

A single false confirmation or a dropped handoff forces ESCALATE NOW regardless of score, because the harm is local and a high average hides it. A 95/100 call still escalates — the number never earns its way out of the gate.

A pipeline, not a spot-check

It runs on your whole week: per-call verdicts, escalate-share rollup, containment and booking counts, the one call to review first where any call is short, and a field export that lands the flags back on the contact record in GoHighLevel.

05.What This Is — And Isn’t

A grading pipeline. Not a live monitor, not a certifier.

It is
  • A deterministic pipeline that scores completed calls from your own marks.
  • A keystone gate that catches false confirmations and failed handoffs.
  • A weekly rollup and a GoHighLevel-importable field export.
  • Fully editable — weights, bands, and thresholds are yours to tune.
It isn’t
  • A live monitor — it connects to no agent and reads no live call.
  • A transcript reader on its own — you supply the marks.
  • A compliance certification or a legal opinion.
  • A tool that scores, ranks, or rates any person.

Not legal advice. Voice-agent calling and recording touch TCPA, state AI-disclosure, and recording-consent rules that vary by state and vertical. This pipeline grades completed calls from your own marks as an operational artifact — it scores no person, connects to nothing, and confirms no compliance status. Confirm your obligations with counsel.

06.Who It’s For

Operators who put an AI on the phone and now own the calls it makes.

GHL & ElevenLabs agencies running voice AI across client sub-accounts
Med-spa, dental, and home-services owners with a booking line on autopilot
RevOps leads who need a weekly QA story before a client asks for one
Anyone who has watched an AI ‘confirm’ an appointment that doesn’t exist
08.Common Questions

The parts worth pinning down before you buy.

A QA auditor grades a spot-check batch and hands you a craft verdict. This is the weekly pipeline that runs on your whole call log: it scores every call, rolls up your containment, booking, dead-air and interruption counts, names the one call to review first where any call is short, and emits a GoHighLevel-importable custom-field CSV so the flags land back on the contact record. It's the operational loop (the guide's WF-6), not a one-off review.

The call that ends politely
with a promise you can’t keep.

Find it every Friday, before the caller shows up to an appointment that isn’t there. One purchase, lifetime access, 12 months of updates. $129, once.

Not legal advice. Voice-agent calling and recording touch TCPA, state AI-disclosure, and recording-consent rules that vary by state and vertical. This pipeline grades completed calls from your own marks as an operational artifact — it scores no person, connects to nothing, and confirms no compliance status. Confirm your obligations with counsel.

Sold by RedHub AI LLC · Secured by Stripe · redhub.ai