All system metrics listed below are powered by specialized models purpose-built for voice AI analysis. This means they are faster, more consistent, and more cost-effective than general-purpose LLM evaluation.
Metric Types Overview
Roark supports four ways to define metrics. System metrics use the first type, and you can create your own using any of the four:LLM as Judge
Define a metric with a natural-language prompt. Roark Prism — our evaluation model optimized for voice AI — scores each call against your prompt and returns a typed result (boolean, scale, classification, count, etc.).Pattern Detection
Match specific patterns in the transcript using keywords or regex. Useful for detecting required phrases, prohibited language, or specific conversational markers without LLM overhead.Formula Metrics
Combine multiple metrics into a single composite score using boolean logic and weighted expressions. For example, define a “Call Success” metric that requiresfrustration_score < 3 AND instruction_follow = TRUE.

System Metrics Reference
All system metrics below are collected automatically when included in an analysis package. Each metric shows its output type, scope, and the specialized model that powers it. Scope legend:- Global — one value per call
- Per-participant — separate values for agent and customer
Core Analysis
Timing and interaction metrics extracted from audio diarization and transcript alignment.Powered by Roark Vibe — our core voice analysis model.
Sentiment & Emotion
Emotion and sentiment analysis from vocal features and acoustic signals.Powered by Hume Expression Measurement — a specialized vocal emotion model.
Interruptions
Detailed interruption and overlap analysis from speaker diarization.Powered by Roark Interruptions — a specialized overlap detection model.
Quality
Experience quality scoring from conversational signals.Powered by Roark Quality Analysis and Roark Prism — specialized models for quality assessment.
Repetition Detection
Conversational loop and repetition analysis.Powered by Roark Prism — our evaluation model optimized for voice AI.
Tool Invocations
Analysis of function/tool calling behavior during conversations.Powered by Roark Vibe and Roark Prism.
Compliance
Regulatory and safety evaluation metrics for AI agent conversations.Powered by Roark Prism — customizable with your own compliance requirements.
Voicemail Detection
Voicemail detection and handling quality assessment.Powered by Roark Prism.
Call Screening
Detects when a screener answers an outbound call instead of the person being called: a receptionist, an assistant, a household gatekeeper, or an automated screen.Powered by Roark Prism.
Accent Detection
English accent identification from audio signals.Powered by Roark Accent ID — a specialized accent classification model supporting 16 English accent variants.
For a detailed walkthrough on using accent metrics, see the Accent Detection recipe.
Call Quality (DNSMOS)
Speech quality assessment using the ITU-T P.808/P.835 Mean Opinion Score (MOS) scale.Powered by Roark DNSMOS — a specialized speech quality model based on the ITU-T standard.
Voice Naturalness
Acoustic naturalness of the agent’s synthesized voice.Powered by Roark UTMOS, a specialized naturalness model producing a mean opinion score.
Voice Human-Likeness
Perceptual human-likeness judged from the agent’s own audio.Powered by an audio-input evaluation model listening to the agent’s actual speech.
Call Environment
Zero-shot acoustic classification of the caller’s environment.Powered by a specialized audio classification model.
Pronunciation Analysis
Per-word pronunciation checking against expected pronunciations you configure.Powered by Roark Phoneme, a wav2vec2-based phoneme recognition model. Configure the word list and strictness per project.
Property Verification
Checks the call properties you send at ingest (customer name, account number, appointment time, and so on) against what was actually said on the call, and flags values that conflict. Useful for catching stale CRM data, transcription errors, and callers who are not who the metadata says they are.Powered by Roark Prism. Requires custom properties on the call; system-generated properties are never checked.
Every property is judged with a three-way verdict:
- MATCH: the conversation referred to this property and agrees with the value you sent, allowing for formatting differences, nicknames, partial references, and transcription noise.
- MISMATCH: the conversation states a genuinely different value.
- NOT_MENTIONED: the subject never came up. This is the most common outcome and is not counted as a mismatch.
propertyVerdicts array on the metric value: each entry carries the property name, the expected value, the verdict, the observed value for mismatches, the judge’s reasoning, and the transcript segment where the property was referred to. The same breakdown renders on the call detail page in the platform.
What’s Next
Custom Metrics
Create custom LLM as Judge, Pattern, and Formula metrics
Studio
Test metrics interactively against real calls
Collectors
Automate metric collection with conditions-based rules
Thresholds
Define pass/fail criteria for your metrics