Skip to content
Talk to an engineer

Agent Studio

Conversations (HITL)

flowchart LR
  A["Filter conversations<br/>status, sentiment, gaps"] --> B["Inspect detail<br/>timeline, actions, analysis"]
  B --> C{"Issue found?"}
  C -->|"Knowledge gap"| D["Add to Knowledge Base"]
  C -->|"Action bug"| E["Debug handler"]
  C -->|"Looks good"| F["No action needed"]
  style A fill:#e8ecff,stroke:#1842ef,color:#0a0e1a
  style B fill:#e8ecff,stroke:#1842ef,color:#0a0e1a
  style C fill:#e8ecff,stroke:#1842ef,color:#0a0e1a
  style D fill:#dbe2ff,stroke:#1842ef,color:#0a0e1a
  style E fill:#fef3c7,stroke:#d97706,color:#0a0e1a
  style F fill:#d1fae5,stroke:#059669,color:#0a0e1a

Path: Agent Studio → Conversations

Conversations shows every real interaction users have had with your agent. It’s your primary tool for quality review and debugging.

The top bar summarizes activity across all conversations:

MetricWhat it means
Total ConversationsAll sessions where a user interacted with the agent
Questions AskedTotal user messages sent
Conversation HandoffsTimes the agent escalated to a human
ActionsTotal action calls executed by the agent

The left panel lists conversations sorted by recency. Each row shows the user’s name, the auto-generated conversation topic, and the time. Click a row to open the full conversation.

Use the filter bar to narrow the list by:

  • Resolution status — resolved, unresolved, or escalated.
  • User Feedback — thumbs up/down ratings from users.
  • Actions — conversations where a specific action was triggered. Use this to see how a published action behaves in the wild, then open The action lifecycle to iterate. Connected A2A agents appear in the same dropdown by name, tagged with an A2A badge — select one and click Apply to see every conversation that delegated to it.
  • Conversation Signals — auto-detected tags on each conversation. Values include User Sentiment, Information Request, Action Request, and Reported Issue — plus the two that drive your improvement worklist:
    • Agent Knowledge Gap — the agent lacked the content to answer. Each one points to a Knowledge Base article to add or refresh.
    • Agent Action Gap — the user asked for something the agent had no action for. Each one is a candidate for a new action.
  • Source — where the conversation came from: Live Agent, Slack, Trust Lab, or SDK Test. Select SDK Test to surface test mode sessions, which are hidden by default so real user activity stays clean.

The right panel shows the full message-by-message exchange. At the bottom of each agent message there’s a View Analysis link — click it to see how the agent interpreted the request, which knowledge it used, and which actions it called.

Conversation timeline showing message flow with scores and actions U "How do I upgrade?" 10:02 AM A Explains tiers Score: 92 10:02 AM navigate /pricing 10:02 AM U "Thanks, I'll go with Pro" 10:03 AM A Resolved 😊 Great 10:03 AM User Agent Action

The right-side panel shows User Details (name, email, product) along with any Session Replay recording associated with the conversation.

When you spot a problem, the fix usually lives elsewhere: add missing content in the Knowledge Base, or correct a capability in Actions.