Menu
Support ticket lifecycle management. Use when triaging, assigning, tracking, or resolving customer support tickets.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Schedule reminders and recurring tasks.
Two-layer memory system with grep-based recall.
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Business process analysis and improvement. Use when mapping, analyzing, or optimizing processes.
Requirements gathering and documentation. Use when eliciting, documenting, or validating requirements.
| name | ticket-management |
| description | Support ticket lifecycle management. Use when triaging, assigning, tracking, or resolving customer support tickets. |
| metadata | {"clawbot":{"emoji":"🎫"}} |
New → Triaged → Assigned → In Progress → Resolved → Closed
↓
Escalated → [Engineering/Product/Other]
| Priority | Criteria | Response SLA | Resolution SLA |
|---|---|---|---|
| P0 - Critical | Service down, data loss, security breach | 15 minutes | 4 hours |
| P1 - High | Major feature broken, many users affected | 1 hour | 24 hours |
| P2 - Medium | Feature degraded, workaround available | 4 hours | 3 days |
| P3 - Low | Minor issue, cosmetic, feature request | 24 hours | 1 week |
## Summary
[One-line description]
## Customer
- Account: [customer name/ID]
- Contact: [email/channel]
- Segment: [enterprise/SMB/self-serve]
## Issue Details
- **Reported**: [timestamp]
- **Priority**: [P0/P1/P2/P3]
- **Category**: [bug/question/feature-request/account]
## Description
[Detailed description from customer]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Expected vs actual result]
## Investigation Notes
[Your findings]
## Resolution
[How it was resolved]
Escalate when: