# Conversation Viewer The Conversation Viewer (accessed via the Conversation tab) provides transcript-level inspection of individual conversations. While the Basic Dashboard shows aggregated metrics, this interface enables granular investigation. ### 1. Two-Panel Layout

*Figure 1 — Conversation Viewer: two-panel layout*

### 1.1 Left Panel — Conversation List A scrollable, paginated list (default 30 per page) showing total count (e.g., "0 - 30 of 64,584"), page navigation, and "Goto Index" for direct access. Each entry shows:


Field	Description
Assistant Name	The assistant/service that handled the conversation.
Timestamp	Date and time the conversation started, in local timezone.
Channel	Communication channel tag (e.g., "chat", "phone").
Duration	Total conversation length (e.g., "2m 7s").
Disposition	Termination reason (e.g., "Timeout", "UserDisconnect").

### 1.2 Right Panel — Conversation Details Renders the full conversation as a chat interface with distinct visual treatments:


Message Type	Visual Treatment
Assistant Responses (TTS)	Teal/light-blue bubbles on the left with TTS icon badge and emoji indicators.
User Inputs (Transcript)	Light gray cards on the right, prefixed with "Transcript:" and raw input in quotes.

Every message includes a precise timestamp and a response delta indicator (e.g., "+2s", "+14s", "+1m 18s") showing time elapsed since the previous message. ### 2. Conversation Metadata Header A collapsible header above the conversation flow reveals detailed metadata when expanded.

*Figure 2 — Expanded metadata header with navigation controls*


Field	Description
Conversation ID	Unique UUID with copy-to-clipboard button for cross-referencing.
Channel	Communication channel (e.g., "chat").
Stage	Deployment environment (e.g., "UAT", "PROD"). Critical for distinguishing test vs. production data.
Start/End Date	Exact timestamps for conversation boundaries.
Duration	Total calculated duration (e.g., "2m 7s").

Navigation controls include Prev/Next buttons, position indicator (e.g., "1 of 30"), and an "(all)" filter toggle. ### 3. Expandable Message Detail Accordions Each message bubble can be clicked to expand and reveal technical metadata for debugging and QA.

*Figure 3 — Expanded message accordions with technical metadata*

### 3.1 User Input Details


Field	Description
State Name	UUID of the conversation flow state/node that processed this input.
Record Source	Data pipeline source (e.g., "CDS" for Common Data Schema).
InputType	How the user submitted input (e.g., "text", "voice", "DTMF").

### 3.2 Assistant Response Details Expanded view shows the TTS index number (e.g., "0 TTS") and the full synthesized text in quotes — the exact output delivered to the user. **Business Value:** Essential for debugging conversation flows, verifying correct state/node handling, confirming data pipeline integrity, and auditing TTS output. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ixhello.com/ix-hello-reporting/basic-reporting/conversation-viewer.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.