Skip to main content
When one agent looks off, this is how you dig in — from its activity trends down to the calls and findings behind them.

1. Open the agent

From Agents, open the agent. The detail page shows a call-volume trend chart and an hour-by-day heatmap, so you can tell whether today’s dip is a blip or a trend.

2. Drill into the calls

The detail page lists the agent’s most recent conversations. Open a call to read the transcript next to the system prompt and listen to the recording. To narrow in, filter the conversations by ended reason, has-audio, or date range. The agent’s system prompt (and its flow) are on the detail tabs too, so you can check its behavior against what it was actually told to do.

3. Work the findings

When open findings for an agent pile up, the agent surfaces a prompt to review them. From there, triage the findings and capture a solution for the fix.

Audit programmatically

  • MCPget_agent, list_conversations, and query_database for ad-hoc aggregations over the agent’s calls (e.g. failure counts by ended reason).
  • Agents — the concepts behind an audit.
  • Conversations — the calls you’re drilling into.
  • Findings — the recurring issues you promote and fix.