customer support triage
- Repo stars 1
- Author repo claude-skills
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Customer Support Triage
## Overview
Move quickly from raw ticket to the next best customer and internal action.
## Core Workflow
1. Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related.
2. Extract the facts already present and identify the minimum follow-up questions needed to unblock triage.
3. Choose the troubleshooting or escalation path based on risk, customer impact, and ownership.
4. Draft the customer reply in the correct tone with clear next steps and realistic expectations.
5. Capture internal notes, escalation reasons, and any evidence that the next team will need.
## Deliver
- Provide a triage decision, the next action, and a ready-to-send response draft.
- Keep customer-facing language calm, direct, and empathetic.
- Make internal handoff notes concise but complete.
## Guardrails
- Do not promise refunds, fixes, or timelines that are not authorized.
- Escalate security, safety, and account-compromise signals immediately.
- Ask only the follow-up questions that materially change the path forward.
Sections and files
Listed in source order.
sections -> Overview → Core Workflow → Deliver → Guardrails
terms -> Move quickly from raw ticket to the next best customer and internal action. · 1. Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related. · - Provide a triage decision, the next action, and a ready-to-send response draft. · - Do not promise refunds, fixes, or timelines that are not authorized.
files/cmd -> no explicit files or commands
body sha256 -> 8f0de39c1302
Overview
Move quickly from raw ticket to the next best customer and internal action.
Core Workflow
Classify the issue type, urgency, severity, and whether the request is support, bug, billing, abuse, or access related. Extract the facts already present and identify the minimum follow-up questions needed to unblock triage. Choose the troubleshooting or escalation path based on risk, customer impact, and ownership. Draft the customer reply in the correct tone with clear next steps and realistic expectations.
Deliver
Provide a triage decision, the next action, and a ready-to-send response draft. Keep customer-facing language calm, direct, and empathetic. Make internal handoff notes concise but complete.
Guardrails
Do not promise refunds, fixes, or timelines that are not authorized. Escalate security, safety, and account-compromise signals immediately. Ask only the follow-up questions that materially change the path forward.