Did the agent do its job? (task resolution & correctness)
Was it fast and responsive? (latency & reliability)
Does it sound natural? (voice quality — voice agents)
Does the audio have signal artifacts? (voice agents)
These metrics flag different audio patterns; their scores do not identify a technical cause. A low clipping score can miss distortion after rescaling, and natural speech gaps can resemble dropouts. See the Statistical metrics page for each metric’s scope and interpretation.
How did the customer feel? (sentiment & experience)
Did it follow the rules? (compliance & scripting)
Did it do the right things behind the scenes? (tools & traces)
Was the audio transcribed accurately? (STT accuracy)
What did it cost? (usage)
Need a measurement specific to your agent?
Use a SQL metric when you can define an exact rule over recorded conversation data: count calls to a particular tool, measure speaking-segment durations, or count messages matching a text rule. SQL produces a numeric score without an LLM judge. For questions that need interpretation, such as whether a response was helpful, choose an LLM Judge.Once you know which metrics you want, add them to a run. For anything custom, see Write judge prompts and Configure metrics.