Export conversations
When you need to analyze Atom conversations outside Atomicwork, export them from the Conversations page in Analytics. The export includes the knowledge Atom cited, the forms it started and how they ended, the tickets it filed, and a full transcript that also covers activity on those tickets.
To open this page, go to Analytics > Atom > Conversations. Each row shows the Conversation, Deflection, Conversation rating, and Source.
Organization owners, organization admins, workspace admins, and workspace analysts can export conversations. Organization owners and organization admins can export across workspaces. Workspace admins and workspace analysts can export only from the workspaces they have access to.
Filter the conversations you want to export
The export includes conversations that match the Workspace and Duration filters, Search, and any filters you add, such as Channel, User segment, Deflection, Conversation rating, or Subtheme. You can filter to specific workspaces or include all workspaces you have access to. There is no maximum date range.
Each selected conversation is exported in full: every message, plus all activity on tickets created from it, up to the time of the export, whatever the date of that activity.
Export the files
- Go to Analytics > Atom > Conversations.
- Set the Workspace and Duration filters, enter any Search text, and add any other filters you need.
- Click Export.
Atomicwork emails you a download link when the export is ready. The link expires in 7 days. The download is a ZIP file that contains:
- README.txt: A description of the files, how they join, and what each column means.
- conversations.csv: One row per conversation that matches your search and filters.
- messages.csv: One row per message in those conversations, including activity on tickets filed from them. Rows are grouped by conversation and sorted by time.
Join the two CSV files on conversation_id. Every conversation_id in messages.csv matches a row in conversations.csv.
Note
Re-exporting the same date range later can add rows, because ticket activity is included up to the time of the export.
What’s in conversations.csv
What’s in messages.csv
messages.csv is the full transcript of each exported conversation: every message with Atom, plus all activity on tickets filed from the conversation, including private notes and internal ticket updates. Rows are grouped by conversation and sorted by timestamp.
Labels used in the files
No cell is left blank. These labels have fixed meanings:
Cells that hold several values list one value per line. Labels match those shown in the product.
theme, subtheme, conversation_outcome, deflected, and judge_reasoning come from an evaluation that runs once every 24 hours. Conversations that started after the last evaluation run show Evaluation pending until the next run. A ticket can already appear in messages.csv while conversation_outcome still says Evaluation pending.
Example: reviewing a cab opt-out conversation
An employee in the IT workspace messages Atom in Slack to opt out of the office cab service. Atom shows the Cab opt-out form, the employee submits it, and ticket ITSR-25707 is created for the travel desk.
In conversations.csv you’d see channel as Slack, form_surfaced as true, forms as Cab opt-out: Request created, ticket_created as true, ticket_id as ITSR-25707, and ticket_types as ITSR-25707: Service request. After evaluation, conversation_outcome is Request created and deflected is false.
In messages.csv, rows in time order include the employee’s request (Employee, Public, Conversation), Atom offering the form (AI Agent, with form_event Offered), the request-created notification (System notification, Ticket, with form_event Request created), and later public replies and private notes from the travel desk agent.
If you export before evaluation runs, theme, subtheme, conversation_outcome, deflected, and judge_reasoning show Evaluation pending, even though messages.csv already shows the ticket.
