Integrations Overview
RubricHQ tests your conversational agent by running an AI-simulated caller against it. You define a scenario (the caller’s persona, goal, and step-by-step instructions) and a set of metrics, then RubricHQ runs the conversation and evaluates the transcript.
The only thing that changes between integrations is how RubricHQ reaches your agent — the transport. Everything else (scenarios, personas, metrics, results) is shared.
Choose a channel
A RubricHQ agent has up to three channels. You pick which one a test run uses.
Text testing is ~10× faster and far cheaper than voice. Use it for workflow validation, regression testing, and CI. Reserve voice testing for ASR/TTS validation and final pre-prod checks.
Voice vs Text — what’s evaluated
- Voice runs produce an audio recording, so you get transcript metrics and audio metrics (latency, interruptions, words-per-minute, voice clarity, etc.).
- Text runs have no audio, so only transcript metrics apply. Audio-only metrics are automatically skipped for text runs.
Quickstart
- Create an agent and open Channels.
- Configure the channel you want to test (Phone, Web, or Text) — see the per-integration pages.
- Create a scenario for that agent (persona + instructions + outcome) and attach metrics.
- Run it — from the Evaluator / Batch Run page, choose the channel and click Run.
- Review the transcript, metrics, and (for voice) recording in the results.
Next:
- Text Testing — connect your agent over the Custom WebSocket (X-RUBRIC) protocol, with a runnable example.
- Voice Testing — overview of every voice integration (phone + web).
- LiveKit — connect your own bot in a LiveKit room (client- vs RubricHQ-managed rooms), with request/response examples and room-config keys.
- Daily — connect your own bot in a Daily room; same two modes, with Daily room-properties (incl. recording) keys.
- Vapi — test an existing Vapi assistant; sync or paste instructions, auto-fetch calls.
- Retell — test an existing Retell agent; sync or paste instructions, auto-fetch calls.