support-operations
Expert support operations guidance for customer service excellence. Use when designing ticket management systems, creating SLA policies, building support tier structures (L1/L2/L3), optimizing knowledge bases, defining severity levels and escalation procedures, implementing support metrics (CSAT, FRT, TTR, FCR), configuring support tool stacks, or building support-to-CS feedback loops. Covers Zendesk, Intercom, Freshdesk, and help desk best practices.
- Installs
- 159
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/ncklrs/startup-os-skills --skill support-operations- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads support-operations automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Support Operations
Strategic support operations expertise for customer-facing teams — from ticket management and SLA design to escalation workflows and self-service optimization.
Philosophy
Great support isn't about closing tickets fast. It's about solving customer problems permanently while building scalable systems.
The best support operations teams:
- Prevent before they support — Self-service and proactive help reduce ticket volume
- Measure what drives loyalty — Resolution quality beats response speed
- Escalate with context — Every handoff preserves customer history
- Feed insights upstream — Support data drives product and success improvements
How This Skill Works
When invoked, apply the guidelines in rules/ organized by:
ticket-*— Ticket management, prioritization, queue optimizationsla-*— SLA design, compliance monitoring, escalation triggerstier-*— Support tier structure, skill-based routing, specializationknowledge-*— Knowledge base strategy, self-service, deflectionmetrics-*— CSAT, FRT, TTR, FCR, quality scoringescalation-*— Severity definitions, escalation paths, incident managementtooling-*— Support stack optimization, integrations, automationfeedback-*— Support-to-CS handoffs, product feedback loops, voice of customer
Core Frameworks
The Support Operations Hierarchy
| Level | Focus | Metrics | Owner |
|---|---|---|---|
| Tickets | Individual resolution | Handle time, CSAT | Agents |
| Queue | Flow optimization | Wait time, backlog | Team leads |
| Channel | Channel effectiveness | Deflection, containment | Managers |
| Operations | System performance | Cost per ticket, NPS | Directors |
| Strategy | Business impact | Retention, expansion | VP/C-level |
The Support Tier Model
┌─────────────────────────────────────────────────────────────────┐
│ TIER 3 (L3) │
│ Engineering escalation, code-level issues, custom development │
│ Target: <5% of tickets | SLA: Best effort │
├─────────────────────────────────────────────────────────────────┤
│ TIER 2 (L2) │
│ Technical specialists, complex troubleshooting, integrations │
│ Target: 15-25% of tickets | SLA: 4-8 hours │
├─────────────────────────────────────────────────────────────────┤
│ TIER 1 (L1) │
│ First response, common issues, documentation guidance │
│ Target: 60-80% resolution | SLA: 15-60 minutes │
├─────────────────────────────────────────────────────────────────┤
│ SELF-SERVICE (L0) │
│ Knowledge base, chatbots, community forums, in-app help │
│ Target: 30-50% deflection | SLA: Instant │
└─────────────────────────────────────────────────────────────────┘
Ticket Priority Matrix
| Priority | Business Impact | Response SLA | Resolution SLA | Examples |
|---|---|---|---|---|
| P1 Critical | Complete outage, data loss | 15 min | 4 hours | System down, security breach |
| P2 High | Major feature broken | 1 hour | 8 hours | Key workflow blocked |
| P3 Medium | Feature impaired | 4 hours | 24 hours | Partial functionality |
| P4 Low | Minor issue, cosmetic | 8 hours | 72 hours | UI bug, minor inconvenience |
| P5 Request | Feature request, how-to | 24 hours | 5 days | Enhancement, training |
Support Metrics Framework
| Metric | Definition | Target | Warning |
|---|---|---|---|
| CSAT | Customer satisfaction score | 90%+ | <85% |
| FRT | First response time | <1 hour | >4 hours |
| TTR | Time to resolution | <24 hours | >72 hours |
| FCR | First contact resolution | 70%+ | <50% |
| NPS | Net promoter score | 30+ | <10 |
| Ticket Volume | Tickets per 100 customers | 5-15 | >25 |
| Deflection Rate | Self-service success | 30-50% | <20% |
| Escalation Rate | Tickets escalated | 10-20% | >30% |
| Reopen Rate | Tickets reopened | <5% | >10% |
| Agent Utilization | Productive time | 70-80% | <60% or >90% |
The Ticket Lifecycle
┌─────────────────────────────────────────────────────────────────┐
│ │
│ NEW → TRIAGED → ASSIGNED → IN PROGRESS → PENDING → RESOLVED │
│ │ │ │
│ ▼ ▼ │
│ ESCALATED WAITING │
│ │ (Customer) │
│ ▼ │
│ ENGINEERING │
│ │
└─────────────────────────────────────────────────────────────────┘
Channel Strategy Matrix
| Channel | Best For | Cost | Scalability | Personal |
|---|---|---|---|---|
| Self-service | Common issues | Lowest | Highest | Lowest |
| Chatbot | Quick questions | Low | High | Low |
| Live chat | Real-time help | Medium | Medium | Medium |
| Email/Ticket | Complex issues | Medium | Medium | Medium |
| Phone | Urgent/sensitive | High | Low | High |
| Video | Technical demos | High | Low | Highest |
Severity Levels
| Severity | Definition | Escalation Path | Communication |
|---|---|---|---|
| SEV1 | System-wide outage | Immediate to engineering + exec | Status page, proactive email |
| SEV2 | Major feature broken | 1 hour to L3 | Affected users notified |
| SEV3 | Feature degraded | 4 hours to L2 | Standard ticket updates |
| SEV4 | Minor impact | Normal queue | Standard ticket updates |
Key Formulas
Cost Per Ticket
Cost Per Ticket = (Total Support Cost) / (Total Tickets Handled)
Target: $5-25 depending on complexity
Support Capacity Planning
Required Agents = (Ticket Volume × Handle Time) / (Available Hours × Utilization Rate)
Example:
(500 tickets × 20 min) / (8 hours × 60 min × 0.75) = 28 agents
Self-Service ROI
Savings = (Deflected Tickets × Cost Per Ticket) - Self-Service Investment
Anti-Patterns
- Speed over quality — Fast wrong answers create repeat contacts
- Ticket tennis — Multiple handoffs without resolution
- Knowledge hoarding — Solutions in heads, not documentation
- Metric gaming — Closing tickets prematurely to hit targets
- Escalation avoidance — L1 struggling when L2 is needed
- Channel forcing — Making customers switch channels unnecessarily
- Copy-paste responses — Generic answers that don't address the issue
- Invisible backlog — Tickets aging without visibility
- No feedback loop — Support insights never reach product
- Over-automation — Bots handling issues that need humans
FAQ
What does the support-operations skill do?
Expert support operations guidance for customer service excellence. Use when designing ticket management systems, creating SLA policies, building support tier structures (L1/L2/L3), optimizing knowledge bases, defining severity levels and escalation procedures, implementing support metrics (CSAT, FRT, TTR, FCR), configuring support tool stacks, or building support-to-CS feedback loops. Covers Zendesk, Intercom, Freshdesk, and help desk best practices.
How do I install support-operations?
Run npx skills add https://github.com/ncklrs/startup-os-skills --skill support-operations in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/support-operations/ (personal) or .claude/skills/support-operations/ (project).
Which AI agents can use support-operations?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is support-operations safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains support-operations?
It is published by ncklrs in ncklrs/startup-os-skills. It has 159 recorded installs.
More from ncklrs/startup-os-skills
community-builder
ncklrs/startup-os-skills
Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.
proposal-writer
ncklrs/startup-os-skills
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
motion-designer
ncklrs/startup-os-skills
Advanced motion designer with decades of After Effects and motion graphics experience, specialized in creating engaging video specifications for Remotion. Use when creating video specs, planning motion graphics, designing animations, or when asked to "create a video", "design motion graphics", "plan video content", or "spec out a video". Produces detailed scene-by-scene specifications with timing, audio, sound effects, and animation descriptions.
website-copy-specialist
ncklrs/startup-os-skills
Expert website copywriting for SaaS and B2B companies. Use when writing homepage copy, feature pages, about pages, pricing pages, comparison pages, product tours, integration pages, use case pages, demo/contact pages, or navigation microcopy. Use for website messaging hierarchy, value proposition development, and page-level conversion optimization.
vsl-storyboard-writer
ncklrs/startup-os-skills
Open the skill to read its SKILL.md instructions.
remotion-animation
ncklrs/startup-os-skills
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.