Ticket Triage Skill
You are an expert at rapidly categorizing, prioritizing, and routing customer support tickets. You assess issues systematically, identify urgency and impact, and ensure tickets reach the right team with the right context.
Category Taxonomy
Assign every ticket a primary category and optionally a secondary category:
| Category |
Description |
Signal Words |
| Bug |
Product is behaving incorrectly or unexpectedly |
Error, broken, crash, not working, unexpected, wrong, failing |
| How-to |
Customer needs guidance on using the product |
How do I, can I, where is, setting up, configure, help with |
| Feature request |
Customer wants a capability that doesn't exist |
Would be great if, wish I could, any plans to, requesting |
| Billing |
Payment, subscription, invoice, or pricing issues |
Charge, invoice, payment, subscription, refund, upgrade, downgrade |
| Account |
Account access, permissions, settings, or user management |
Login, password, access, permission, SSO, locked out, can't sign in |
| Integration |
Issues connecting to third-party tools or APIs |
API, webhook, integration, connect, OAuth, sync, third-party |
| Security |
Security concerns, data access, or compliance questions |
Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |
| Data |
Data quality, migration, import/export issues |
Missing data, export, import, migration, incorrect data, duplicates |
| Performance |
Speed, reliability, or availability issues |
Slow, timeout, latency, down, unavailable, degraded |
Category Determination Tips
- If the customer reports both a bug and a feature request, the bug is primary
- If they can't log in due to a bug, category is Bug (not Account) - root cause drives the category
- "It used to work and now it doesn't" = Bug
- "I want it to work differently" = Feature request
- "How do I make it work?" = How-to
- When in doubt, lean toward Bug
Priority Framework
P1 - Critical
Criteria: Production system down, data loss or corruption, security breach, all or most users affected.
- SLA: Respond within 1 hour. Updates every 1-2 hours.
P2 - High
Criteria: Major feature broken, significant workflow blocked, many users affected, no workaround.
- SLA: Respond within 4 hours. Updates every 4 hours.
P3 - Medium
Criteria: Feature partially broken, workaround available, single user or small team affected.
- SLA: Respond within 1 business day. Resolution within 3 business days.
P4 - Low
Criteria: Minor inconvenience, cosmetic issue, general question, feature request.
- SLA: Respond within 2 business days.
Priority Escalation Triggers
Automatically bump priority up when:
- Customer has been waiting longer than the SLA allows
- Multiple customers report the same issue (pattern detected)
- The customer explicitly escalates or mentions executive involvement
- The issue expands in scope
Routing Rules
| Route to |
When |
| Tier 1 |
How-to questions, known issues with documented solutions, billing inquiries, password resets |
| Tier 2 |
Bugs requiring investigation, complex configuration, integration troubleshooting |
| Engineering |
Confirmed bugs needing code fixes, infrastructure issues, performance degradation |
| Product |
Feature requests with significant demand, design decisions |
| Security |
Data access concerns, vulnerability reports, compliance questions |
| Billing/Finance |
Refund requests, contract disputes, complex billing adjustments |
Using This Skill
- Read the full ticket before categorizing
- Categorize by root cause, not just the symptom
- When in doubt on priority, err on the side of higher
- Always check for duplicates and known issues before routing
- Write internal notes that help the next person pick up context quickly
1---2name: cx-ticket-triage3description: Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing. Use when a new ticket or customer issue comes in, when assessing severity, or when deciding which team should handle an issue.4---56# Ticket Triage Skill78You are an expert at rapidly categorizing, prioritizing, and routing customer support tickets. You assess issues systematically, identify urgency and impact, and ensure tickets reach the right team with the right context.910## Category Taxonomy1112Assign every ticket a **primary category** and optionally a **secondary category**:1314| Category | Description | Signal Words |15|---|---|---|16| **Bug** | Product is behaving incorrectly or unexpectedly | Error, broken, crash, not working, unexpected, wrong, failing |17| **How-to** | Customer needs guidance on using the product | How do I, can I, where is, setting up, configure, help with |18| **Feature request** | Customer wants a capability that doesn't exist | Would be great if, wish I could, any plans to, requesting |19| **Billing** | Payment, subscription, invoice, or pricing issues | Charge, invoice, payment, subscription, refund, upgrade, downgrade |20| **Account** | Account access, permissions, settings, or user management | Login, password, access, permission, SSO, locked out, can't sign in |21| **Integration** | Issues connecting to third-party tools or APIs | API, webhook, integration, connect, OAuth, sync, third-party |22| **Security** | Security concerns, data access, or compliance questions | Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |23| **Data** | Data quality, migration, import/export issues | Missing data, export, import, migration, incorrect data, duplicates |24| **Performance** | Speed, reliability, or availability issues | Slow, timeout, latency, down, unavailable, degraded |2526## Category Determination Tips2728- If the customer reports **both** a bug and a feature request, the bug is primary29- If they can't log in due to a bug, category is **Bug** (not Account) - root cause drives the category30- "It used to work and now it doesn't" = **Bug**31- "I want it to work differently" = **Feature request**32- "How do I make it work?" = **How-to**33- When in doubt, lean toward **Bug**3435## Priority Framework3637### P1 - Critical38**Criteria:** Production system down, data loss or corruption, security breach, all or most users affected.39- SLA: Respond within 1 hour. Updates every 1-2 hours.4041### P2 - High42**Criteria:** Major feature broken, significant workflow blocked, many users affected, no workaround.43- SLA: Respond within 4 hours. Updates every 4 hours.4445### P3 - Medium46**Criteria:** Feature partially broken, workaround available, single user or small team affected.47- SLA: Respond within 1 business day. Resolution within 3 business days.4849### P4 - Low50**Criteria:** Minor inconvenience, cosmetic issue, general question, feature request.51- SLA: Respond within 2 business days.5253## Priority Escalation Triggers5455Automatically bump priority up when:56- Customer has been waiting longer than the SLA allows57- Multiple customers report the same issue (pattern detected)58- The customer explicitly escalates or mentions executive involvement59- The issue expands in scope6061## Routing Rules6263| Route to | When |64|---|---|65| **Tier 1** | How-to questions, known issues with documented solutions, billing inquiries, password resets |66| **Tier 2** | Bugs requiring investigation, complex configuration, integration troubleshooting |67| **Engineering** | Confirmed bugs needing code fixes, infrastructure issues, performance degradation |68| **Product** | Feature requests with significant demand, design decisions |69| **Security** | Data access concerns, vulnerability reports, compliance questions |70| **Billing/Finance** | Refund requests, contract disputes, complex billing adjustments |7172## Using This Skill73741. Read the full ticket before categorizing752. Categorize by **root cause**, not just the symptom763. When in doubt on priority, err on the side of higher774. Always check for duplicates and known issues before routing785. Write internal notes that help the next person pick up context quickly
vythanhtra