AtlasCustomer portalAPI DocumentationGo to Atlas
Help Center›Zeus AI›Zeus AI: QA ›How to manage Zeus AI QA Run history

How to manage Zeus AI QA Run history

Last updated October 26, 2026

Who can use this feature?
Admins and Agents can view and edit. Viewers can't open Zeus AI.
Zeus AI is a paid add-on available for any Atlas plan.

Overview

The Run history interface serves as an auditing and quality assurance log that tracks historical Zeus AI interactions across customer conversations. It provides a centralized view to evaluate Zeus AI responses, inspect execution duration, trace Zeus AI agent reasoning, and manage review workflows.

Related articles:
•  How to manage Zeus AI QA Test mode: Test changes before they reach customers.
•  Zeus AI Quality Assurance Overview: How Test mode and Run history work together.
•  How to manage Zeus AI Knowledge Snippets: Fix the knowledge behind a flagged answer.

Key features

  • Zeus AI Run Tracking: Logs every customer conversation with primary details, including customers, start times, run duration, CSAT scores, AI summaries, operational statuses (In Progress, Escalated), and review stages (Pending, Reviewed or Required).
  • Session Metadata & Visitor Insights: Run history information and visitor information is available
  • Qualitative Feedback: Dedicated input panel allowing reviewers to write, edit, and save internal evaluation notes.
  • Deep Diagnostic Tabs: Inspect execution details via dedicated tabs for Knowledge (retrieved help articles), Protocols (active compliance rules), Tools (triggered function calls with raw payloads), and Reasoning (AI decision logic).

How to audit a run

To enhance the quality of your Zeus AI answers, you can use this feature to audit responses and assign the corresponding review status, whether the answer is good, pending review, or should be flagged as inaccurate.

  1.  To audit the a Zeus AI response, go to " Zeus AI > QA > Run history " and click the row to open the detail pane for that conversation.
  2. Review the customer query against the AI response for accuracy and tone.
  3. Check the right-hand panel tabs (Knowledge, Protocols, Tools, Reasoning) to verify function calls and logic.
  4. Update the review status.
Review status options in a run

Review status options in a run. Click the image to enlarge.

Important:
Available review status are:
Pending: Default state indicating the interaction is awaiting audit or incomplete evaluation.
Reviewed: Confirms the interaction has been fully audited and meets standard quality criteria.
Flag (Required): Marks interactions that contain errors, compliance violations, inadequate responses, or technical issues requiring escalation. Once flagged, the conversation's status in the table updates to Required.
How to manage Zeus AI QA Run history

How to view session metadata, feedback & diagnostics

To inspect detailed information, session metrics, and decision logic for a Zeus AI conversation:

  1. Go to " Zeus AI > QA > Run history " and click a row to open the detail pane for that conversation. In the side pane, navigate through the displayed accordions and tabs:
MetadataSummaryFeedbackKnowledgeProtocolsToolsReasoningGuardrailsAutomations

Technical details (Run ID, channel, ticket number) and visitor statistics (session count, average duration, solve time).

The Metadata sectionThe Metadata section

Live, AI-generated updates on the current state of the conversation.

The Summary sectionThe Summary section

Enter and save notes or evaluation feedback for the run.

The Feedback sectionThe Feedback section

The documentation, help articles and sources used to answer the customer.

The Knowledge tabThe Knowledge tab

The compliance rules and operational guidelines followed in the response.

The Protocols tabThe Protocols tab

The function calls Zeus AI made, with expandable raw payloads.

The Tools tabThe Tools tab

The step-by-step logic Zeus AI used to build its response.

The Reasoning tabThe Reasoning tab

The safeguards and restrictions applied to the response. Only shown when guardrails were applied.

The Guardrails sectionThe Guardrails section

The automated actions and workflows triggered during the conversation. Only shown when automations were triggered.

The Automations sectionThe Automations section

Was this article helpful?