ticket-triagelisted

# /ticket-triage > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Categorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response. ## Usage ``` /ticket-triage <ticket text, customer message, or issue description> ``` Examples: - `/ticket-triage Customer says their dashboard has been showing a blank page since this morning` - `/ticket-triage "I was charged twice for my subscription this month"` - `/ticket-triage User can't connect their SSO — getting a 403 error on the callback URL` - `/ticket-triage Feature request: they want to export reports as PDF` ## Workflow ### 1. Parse the Issue Read the input and extract: - **Core problem**: What is the customer actually experiencing? - **Symptoms**: What specific behavior or error are they seeing? - **Customer context**: Who is this? Any account details, plan level, or history available? - **Urgency signals**: Are they blocked? Is this production? How many users affected? - **Emotional state**: Frustrated, confused, matter-of-fact, escalating? ### 2. Categorize and Prioritize Using the category taxonomy and priority framework below: - Assign a **primary category** (bug, how-to, feature request, billing, account, integration, security, data, performance) and an optional secondary category - Assign a **priority** (P1–P4) based on impact and urgency - Identify the