The Conversation review page is a drill-down into a single production session. It shows the session's tags, its summary, the full transcript with the user's feedback, and the execution trace behind every answer — everything you need to understand what happened and decide what to do about it.
To open it, click a row in the Conversation Details table of the Observation Dashboard. Each review has its own URL (.../observation/conversation/<sessionId>), so you can share a link to a specific conversation.
From top to bottom:
When you open a conversation from the dashboard, the header shows where you are in the dashboard's list, for example Conversation 3 of 42, with Prev and Next buttons. They step through the same list the dashboard showed — the same scope, time range and filter, in the same order — so you can review all the unresolved or high-risk conversations one after another without returning to the dashboard.
If you open a review from a shared link, the page rebuilds the list from the dashboard settings saved in your browser.
Below the title, the header shows:
The tags strip shows every tag the analysis stored for the session, as
Observation/signals.yaml, for example Urgency Level or Customer Lifetime Value RiskA session that has not been analyzed yet has no tags. See Configuring Observation for how to run the analysis.
The Conversation Summary panel shows the short LLM-generated summary written by the analysis process, so you can grasp the session's content and outcome before reading it.
Next to it, the transcript renders the full exchange of user and assistant messages, in the same format the user saw. The transcript is read-only.
Where the user rated an answer, the rating is shown on that assistant turn: thumbs up or thumbs down, and a note indicator when the user also wrote a comment. Open the note indicator to read the comment. Feedback is read-only here; see Collecting Feedback for how users and applications submit it.
The trace panel shows the execution behind each assistant answer: the agent and sub-agent executions, the LLM calls with their responses and token usage (including cached tokens), and the tool calls with their inputs and outputs. It is the same trace view used by the Studio Preview; see Preview and Trace.
Use it to diagnose why an answer was wrong or slow — for example, a tool that returned unexpected data, a sub-agent that was not called, or a step that consumed far more tokens than expected.
Click the export button in the header to open the Export Chat dialog, then click Export to download the conversation as a ZIP file.
Select Export with snap to include the data snapshots of the session's LU instances that were recorded during the session, so the conversation can be replayed against the same data state it originally ran on. Snapshots are recorded only when the agent's snap_session_mode setting is not none (see agent.yaml Reference).
| Export option | Use case |
| Without snap | Share the transcript for review; lightweight |
| Export with snap | Reproduce the conversation on the exact data it saw, for debugging or as a regression test |
The ZIP also records the agent and the session's LU instances.
A production conversation can become an evaluation test case:
This closes the quality loop: a real production failure becomes a regression test, so the same issue cannot return unnoticed. See Snapshots and Production Import for the full workflow.
Next article: Configuring Observation
The Conversation review page is a drill-down into a single production session. It shows the session's tags, its summary, the full transcript with the user's feedback, and the execution trace behind every answer — everything you need to understand what happened and decide what to do about it.
To open it, click a row in the Conversation Details table of the Observation Dashboard. Each review has its own URL (.../observation/conversation/<sessionId>), so you can share a link to a specific conversation.
From top to bottom:
When you open a conversation from the dashboard, the header shows where you are in the dashboard's list, for example Conversation 3 of 42, with Prev and Next buttons. They step through the same list the dashboard showed — the same scope, time range and filter, in the same order — so you can review all the unresolved or high-risk conversations one after another without returning to the dashboard.
If you open a review from a shared link, the page rebuilds the list from the dashboard settings saved in your browser.
Below the title, the header shows:
The tags strip shows every tag the analysis stored for the session, as
Observation/signals.yaml, for example Urgency Level or Customer Lifetime Value RiskA session that has not been analyzed yet has no tags. See Configuring Observation for how to run the analysis.
The Conversation Summary panel shows the short LLM-generated summary written by the analysis process, so you can grasp the session's content and outcome before reading it.
Next to it, the transcript renders the full exchange of user and assistant messages, in the same format the user saw. The transcript is read-only.
Where the user rated an answer, the rating is shown on that assistant turn: thumbs up or thumbs down, and a note indicator when the user also wrote a comment. Open the note indicator to read the comment. Feedback is read-only here; see Collecting Feedback for how users and applications submit it.
The trace panel shows the execution behind each assistant answer: the agent and sub-agent executions, the LLM calls with their responses and token usage (including cached tokens), and the tool calls with their inputs and outputs. It is the same trace view used by the Studio Preview; see Preview and Trace.
Use it to diagnose why an answer was wrong or slow — for example, a tool that returned unexpected data, a sub-agent that was not called, or a step that consumed far more tokens than expected.
Click the export button in the header to open the Export Chat dialog, then click Export to download the conversation as a ZIP file.
Select Export with snap to include the data snapshots of the session's LU instances that were recorded during the session, so the conversation can be replayed against the same data state it originally ran on. Snapshots are recorded only when the agent's snap_session_mode setting is not none (see agent.yaml Reference).
| Export option | Use case |
| Without snap | Share the transcript for review; lightweight |
| Export with snap | Reproduce the conversation on the exact data it saw, for debugging or as a regression test |
The ZIP also records the agent and the session's LU instances.
A production conversation can become an evaluation test case:
This closes the quality loop: a real production failure becomes a regression test, so the same issue cannot return unnoticed. See Snapshots and Production Import for the full workflow.
Next article: Configuring Observation