Skip to main content
Triage turns an observed problem into a trackable review item. Ticket creation, reads, assignments, comments, and status updates are implemented through the public API.
Use the API workflow below. There is no connected triage dashboard to follow, and automatic classification or clustering is not established by the response fields.
You need access to the agent and a permitted workspace credential. For a conversation ticket, inspect the saved transcript first.
Recording pending for Review and assign a conversation ticket. No playable video is available yet.

Recording pending: Review and assign a conversation ticket. Follow the written guide below.

1

Create a specific finding

Create a conversation ticket with conversation_id and a concise qa_comment. Optional turn_comments use a zero-based turn_index. Describe the observed action and expected behavior.
2

Assign an eligible reviewer

List assignable users, then check has_access. Update the ticket with assignee_user_id; the assignee must be a workspace member with agent access. Passing null unassigns it.
3

Track the resolution

Use open, in_progress, or resolved to describe review progress. Add comments with the proposed configuration change and verification evidence. Read the ticket back to confirm the saved state.
Manual tickets support agent follow-up work without a conversation. The merged status and needs_clustering field do not establish an automatic ticket-merging workflow.
Prefer the conversation ID and relevant turn indexes. Include only the private information needed to understand the finding.
No. Record the actual review evidence and identify any verification still blocked by execution availability.