Gen3 Chat Reviewing Conversations

Reviewing and Exporting Conversations

Start Here

1. Use the chat sidebar for recent thread switching during live work.
2. Open Conversations for search, filters, and exports across history.
3. Select a thread to reopen or export supported formats.
4. Use message-level copy/download/report while still in chat when appropriate.

Why this matters

Separating live chat from history search keeps day-to-day work fast while preserving audit and export paths for compliance reviews.

Details

Gen 3 keeps the difference between live work and history review explicit.

Use GT Chat for live review

Stay in GT Chat when you want to:

• read the current transcript while work is still in progress
• watch responses stream
• copy, download, or report the latest assistant message
• continue the same conversation immediately

Use Conversations for history review

Move to Conversations when you need to:

• search across many stored threads
• filter by agent, dataset, or time range
• export filtered history
• review a conversation outside the live chat flow

Export choices in active GT3

Gen 3 currently exposes export actions in both places:

• message- and conversation-level export actions in chat
• filtered-history and single-conversation exports on the conversations page

Use chat exports for immediate handoff of the current thread. Use the conversations page for broader historical review and reporting.

Single-response export shape

When you download only the current assistant response from GT Chat (response mode in the download menu), the export contains the answer text and optional preceding user prompt—not Conversation Title lines, per-message timestamps, or full-thread labels. Choose conversation mode (or export from Conversations) when you need titles, connected-dataset sections, and labeled transcript rows for audit packets.

Recommended review pattern

1. Finish the live exchange in GT Chat.
2. Use chat actions if you only need the current conversation right away.
3. Move to Conversations if you need search, filters, or bulk export.

When to use JSON vs DOCX

Format	Best use
JSON	Machine-readable archive, scripting, downstream processing
DOCX	Human-readable handoff, reports, review packets

Best practices

• Export from the narrowest scope that answers the need.
• Reopen the exact thread instead of duplicating work when continuity matters.
• Use the Report action from chat for support incidents and the conversations export flow for business review or audit use cases.

Related pages

• GT Chat
• Conversations
• Support