← Files Quickchat AIARCHIVED FILE

skills/conversation-triage/SKILL.md

2.73 KB · Oct 4, 2026 · 12:06 UTC

↓ Download file

---
name: conversation-triage
description: >-
  Find and prioritize the customer conversations a teammate should follow up on:
  ones that are still unresolved and ones the AI escalated for the team to
  review. Read a sample, summarize what happened, note any that got a negative
  rating, and suggest a next step for each. Use when the user asks what
  needs a reply, which chats to review, what to follow up on, or to sort the
  support inbox. Do NOT use for aggregate stats (use performance-review) or to
  change the Agent (use improve-agent).
metadata:
  author: quickchat-ai
  version: "1.0"
---

# Conversation triage

Surface the customer conversations a teammate should follow up on, and make each
one actionable.

## Before you start
- Call `list_scenarios` to resolve the Agent. One Agent -> use it; else ask.
- Default window: the last 7 days.

## Steps
1. Use `get_insights` with insight_type="flagged" for the conversations the AI
   escalated for the team to review. It defaults to the most recent matches
   across ALL time, so pass `start_date`/`end_date` to constrain it to the
   window rather than filtering all-time results yourself, and page with
   `next_cursor` if needed.
2. Use `list_conversations` with `resolution_status="open"` plus
   `start_date`/`end_date` for the window to find open conversations.
3. Open `get_conversation_detail` on the most important few to read the
   transcript, see what happened, and note any negative rating the customer left.
4. Where a reply looks wrong or an action seems to have failed, call
   `get_message_diagnostics` on that conversation: it shows the tools the AI
   actually executed (with errors) and the Why AI Said That analysis when one
   exists (`analysis_status=not_generated` means it has not run yet).
5. Cross-reference: a conversation that is both escalated and unresolved is the
   top priority.
6. For each item the user approves, act on it with `update_conversation`:
   `assign_to` to route it to a teammate (or to 'me'), or `status='resolved'` to
   close it out (add `assign_to='me'` if it is not yours, `confirm=true` to resolve).

## Guardrails
- Assigning and resolving are real writes on the customer's Inbox, and resolving
  ends the conversation and can ask the visitor for a final rating. Ask before
  each one and never batch them without approval. Both need SUPPORT access or
  above; if you do not have `update_conversation` on this connection, recommend
  the next step and tell the user to take it in the Quickchat Inbox instead.

## Output
A prioritized list, most important first. For each: the customer's request in one
line, why it is on the list (unresolved or escalated for review), any negative
rating it received, and a suggested next step. End with the single top item to
handle first.

SHA-256: 1e262252845a6d8c9e91d3c1e4dcaf046103bb0e48f1e27bf592aa8c994e49dc