Reports

Reports let you flag issues you discover in traces or conversations and track them through to resolution. They’re tied to specific trace executions and conversation messages, giving your team the context needed to understand and fix problems.

​

When to use reports

• An agent gave an incorrect answer.
• A tool call failed or returned unexpected results.
• A handoff went to the wrong agent.
• You want to track a pattern of issues across conversations.
• You need to document a bug for your team to investigate.

​

Creating a report

Reports are created from the context of a specific conversation and trace:

1. In the Inbox, find the conversation with the issue.
2. On the problematic message, click the Report action.
3. Fill in the report form:

The report is automatically linked to the trace and conversation, so anyone reviewing it can jump directly to the relevant execution and message.

​

Report lifecycle

​

Managing reports

​

List view

Go to Reports in the sidebar to see all reports. Filter by:

• Severity: Minor, Moderate, Critical
• Status: Open, In Progress, Resolved, Closed
• Priority: Low, Medium, High, Urgent
• Assigned to: Specific team member
• MAS type: Storefront, Email, Instagram, Facebook
• Trace ID or Group ID: Find reports for a specific execution or conversation

​

Detail view

Click a report to see:

• Report info: ID, status, severity, priority, reporter, assignee.
• Metadata: Links to the related conversation and trace (click to jump directly).
• Fields: Description, expected behavior, actual behavior.
• Comments: Discussion thread for your team. @mention team members to notify them.
• Timeline: Audit log of all changes (status updates, priority changes, assignments, comments).

​

Quick actions

• Resolve / Reopen: Toggle the report status.
• View trace: Jump to the linked trace to review the execution.
• View conversation: Jump to the linked conversation in the Inbox.

​

Notifications

Reports integrate with the notification system. Team members receive notifications when:

• A new report is created.
• A report is assigned to them.
• Someone @mentions them in a report comment.
• Someone comments on a report they created or commented on.

Configure notification preferences in Settings > Personal > Notifications.

​

Best practices

• Set severity accurately: Critical for customer-facing errors, Minor for cosmetic issues.
• Include specifics: “Agent said order was delivered but tracking shows in-transit” is better than “Wrong answer.”
• Link to the trace: The trace has everything needed to diagnose the issue.
• Use comments: Discuss findings with your team directly on the report instead of in Slack or email. The full context (trace, conversation, discussion) stays in one place.
• Close resolved reports: Keep your report list clean by closing reports once the fix is verified.