> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversation triage

> Create API-backed review tickets, attach transcript evidence, and assign a responsible workspace member.

Triage turns an observed problem into a trackable review item. Ticket creation, reads, assignments, comments, and status updates are implemented through the public API.

<Note>
  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.
</Note>

You need access to the agent and a permitted workspace credential. For a conversation ticket, inspect the saved transcript first.

<Frame caption="Recording pending: Review and assign a conversation ticket. Follow the written guide below.">
  <img src="https://mintcdn.com/threetonelabs-c2efc9c8/RV32i5440UZIaFHA/images/tutorials/recording-pending.webp?fit=max&auto=format&n=RV32i5440UZIaFHA&q=85&s=55f66d2eef49d8c92c9ac46f84bace35" alt="Recording pending for Review and assign a conversation ticket. No playable video is available yet." width="1600" height="900" className="w-full h-auto aspect-video" loading="lazy" noZoom data-path="images/tutorials/recording-pending.webp" />
</Frame>

<Steps>
  <Step title="Create a specific finding" id="triage-create-finding">
    [Create a conversation ticket](/api-reference/create-agent-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.
  </Step>

  <Step title="Assign an eligible reviewer" id="triage-assign-reviewer">
    [List assignable users](/api-reference/list-assignable-users), then check `has_access`. [Update the ticket](/api-reference/update-ticket) with `assignee_user_id`; the assignee must be a workspace member with agent access. Passing null unassigns it.
  </Step>

  <Step title="Track the resolution" id="triage-track-resolution">
    Use `open`, `in_progress`, or `resolved` to describe review progress. Add [comments](/api-reference/add-comment) with the proposed configuration change and verification evidence. Read the ticket back to confirm the saved state.
  </Step>
</Steps>

[Manual tickets](/api-reference/create-manual-ticket) support agent follow-up work without a conversation. The `merged` status and `needs_clustering` field do not establish an automatic ticket-merging workflow.

<AccordionGroup>
  <Accordion title="Should I copy the entire transcript into a comment?" id="triage-faq-transcript">Prefer the conversation ID and relevant turn indexes. Include only the private information needed to understand the finding.</Accordion>
  <Accordion title="Does resolved mean an automated test passed?" id="triage-faq-resolved">No. Record the actual review evidence and identify any verification still blocked by execution availability.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.