agentleFS
nisarthnisarth/claude-skills-store/skills/customer-support/ticket-triage/SKILL.md

ticket-triage

Skill1 starsChanged 7 months agoMITView on GitHub

Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it is a duplicate or known issue before routing. Trigger with "triage this ticket", "prioritize this", "where should this go", or "is this a duplicate".

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before routing, search for existing reports:

    line 41
  2. Distinctive:

    Open tickets: Search by error message, feature name, and symptom keywords.

    line 43
  3. Distinctive:

    Known issues: Check the bug tracker or incident dashboard for active problems.

    line 44
  4. Distinctive:

    Recent incidents: Look for ongoing incidents that match the reported behavior.

    line 45
  5. Distinctive:

    KB articles: Check if a self-service answer already exists.

    line 46
  6. Distinctive:

    If a duplicate or known issue is found, link to it rather than creating a separate investigation.

    line 48
  7. Distinctive:

    Document the triage decision for the ticket record.

    line 84
  8. Distinctive:

    Action: Search for open SSO tickets and known auth issues, determine if this matches an existing problem, link or create new based on …

    line 128
  9. Distinctive:

    Check for duplicates before assigning priority.

    line 133
  10. Distinctive:

    Do not over-prioritize. If everything is P1, nothing is.

    line 135
  11. Distinctive:

    When in doubt between two priority levels, consider the customer tier and whether a workaround exists.

    line 136

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ticket Triage

Categorize, prioritize, and route an incoming support ticket. Check for duplicates and known issues before assignment to avoid redundant work.

Workflow

Step 1: Read and Classify

Parse the ticket content to determine:

  • Category: Bug, feature request, how-to question, billing, account management, integration issue, security concern, data request.
  • Product area: Which feature or module is involved.
  • Severity signal: Error messages, "production down" language, data loss mentions, urgency cues.
  • Customer tier: Enterprise, pro, free -- derived from account data.
  • Channel: Email, chat, phone, social, in-app feedback.

Step 2: Check for Duplicates

Before routing, search for existing reports:

  • Open tickets: Search by error message, feature name, and symptom keywords.
  • Known issues: Check the bug tracker or incident dashboard for active problems.
  • Recent incidents: Look for ongoing incidents that match the reported behavior.
  • KB articles: Check if a self-service answer already exists.

If a duplicate or known issue is found, link to it rather than creating a separate investigation.

Step 3: Assign Priority

Apply the priority matrix based on impact and urgency:

PriorityImpactUrgencyExamples
P1 - CriticalProduction down, data loss, security breachImmediateCannot log in, data deleted, payment processing broken
P2 - HighMajor feature broken, significant workflow disruptionSame dayReports not generating, integration failing, bulk operations broken
P3 - MediumFeature degraded, workaround availableNext business daySlow performance, UI glitch with workaround, minor data display error
P4 - LowCosmetic, enhancement, minor inconvenienceWithin a weekTypo in UI, feature suggestion, documentation gap

Adjust priority upward for:

  • Enterprise or high-ARR accounts (one tier bump).
  • Issues affecting multiple customers (one tier bump).
  • Approaching or breached SLA (one tier bump).
  • Security-related concerns (minimum P2).

Step 4: Route to Team

Determine the right team based on category and required expertise:

CategoryPrimary TeamEscalation Path
Bug (reproducible)EngineeringEngineering Lead
Bug (intermittent)Support L2Engineering
Feature requestProductProduct Lead
How-to questionSupport L1Support L2
Billing/accountBillingFinance
Security concernSecurityCISO
Integration issueIntegrationsEngineering
Data requestSupport L2Data Engineering

Step 5: Produce Triage Summary

Document the triage decision for the ticket record.

Output Format

## Triage Summary

**Ticket**: <ID>
**Received**: <date/time>
**Customer**: <name> | <tier>

### Classification
- **Category**: <category>
- **Product Area**: <feature/module>
- **Priority**: P1 / P2 / P3 / P4
- **Priority Rationale**: <why this priority level>

### Duplicate Check
- **Duplicates found**: Yes / No
- **Related tickets**: <IDs or "none">
- **Known issue**: <bug ID or "none">
- **KB article**: <link or "none">

### Routing
- **Assigned to**: <team>
- **Reason**: <why this team>
- **SLA target**: <response time based on priority>

### Quick Summary
<1-2 sentence description for the receiving team>

### Recommended Action
<specific next step: respond with KB link, investigate, escalate, merge with existing>

Examples

User: "Triage this: customer says their dashboard shows wrong numbers since yesterday" Action: Classify as bug, check for known data issues, assign P2 for data accuracy, route to engineering, check for similar reports.

User: "New ticket from Acme Corp -- they want to export data in Parquet format" Action: Classify as feature request, assign P4, route to product, note the enterprise tier for prioritization context.

User: "Is this a dup? Customer can't log in with Google SSO" Action: Search for open SSO tickets and known auth issues, determine if this matches an existing problem, link or create new based on findings.

Best Practices

  • Triage quickly. The goal is fast, accurate routing -- not solving the problem at this stage.
  • Check for duplicates before assigning priority. If 10 customers reported the same issue, it may already be tracked as a P1.
  • Include the priority rationale so reviewers can adjust without re-investigating.
  • Do not over-prioritize. If everything is P1, nothing is. Reserve critical priority for genuine production-impacting issues.
  • When in doubt between two priority levels, consider the customer tier and whether a workaround exists.
  • Tag tickets consistently with category and product area to enable reporting and trend analysis.
  • For ambiguous tickets, ask one clarifying question rather than guessing incorrectly and misrouting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.