
support-ops
Three stdlib scripts that measure support SLA attainment, staffing gaps, and ticket deflection from helpdesk exports.
- version
- 2.14.14
- GitHub stars
- 30.3K
What it does
- Adds
/cs-support-sla,/cs-support-staffing, and/cs-support-deflectionplus thecs-support-ops-leadagent for queue operations questions - Measures first-response and resolution attainment on business or calendar hours with holidays, counting open breaches as misses and listing tickets due next
- Runs Erlang C for phone and chat (service level, ASA, occupancy cap, shrinkage) and backlog drain for email, showing the roster gap per interval
- Designed for support leads who want staffing and SLA numbers from a ticket export with no helpdesk API or credentials
Run a customer support queue on numbers from a helpdesk ticket export. Three deterministic stdlib scripts: an SLA check that measures first-response and resolution attainment on business or calendar hours with holidays, counts open breaches as misses and lists tickets due next; a staffing planner using Erlang C for phone and chat (service level, ASA, occupancy cap, shrinkage, chat concurrency) and workload with backlog drain for email, with the roster gap per interval; and a deflection finder that ranks contact reasons and routes each to a help-center article, a macro or a product fix. Ships cs-support-ops-lead agent, /cs-support-sla, /cs-support-staffing and /cs-support-deflection commands and 3 cited references.
Add marketplace
/plugin marketplace add alirezarezvani/claude-skillsRun it inside Claude Code once, then install the plugin below.
Install
/plugin install support-ops@claude-code-skillsRun it inside Claude Code after adding the marketplace.
Files
Discovered from sourceSupport Ops
Portability: 3 stdlib Python scripts over CSV/JSON you export from any helpdesk. No helpdesk API, no credentials.
Support teams usually argue from anecdotes: "we're swamped", "the SLA is fine", "we need an FAQ". The ticket export settles each one. This skill measures SLA attainment on the clock the contract actually uses, sizes the team with queueing math instead of tickets-per-agent rules of thumb, and separates topics an article can deflect from topics only a product fix will.
Workflow
# 1 - Are we keeping the promise? What breaches next?
python scripts/sla_check.py --tickets tickets.csv --policy sla_policy.json
# 2 - How many people, when?
python scripts/staffing_plan.py --mode live --intervals volumes.csv --aht 420 --concurrency 2
python scripts/staffing_plan.py --mode async --arrivals 30 --aht 600 --backlog 120
# 3 - Which contact reasons should stop reaching agents?
python scripts/deflection_finder.py --tickets tickets.csv
Step 1 computes first-response and resolution attainment per priority on
business or calendar hours (holidays included), p50/p90, open tickets already
breached or due within --risk-hours, backlog age and reopen rate. Open
tickets past target count as misses.
Step 2 uses Erlang C for phone and chat (service level, ASA, occupancy cap,
shrinkage, chat concurrency) and workload plus backlog drain for email. With a
staffed column it shows the gap per interval.
Step 3 ranks the Pareto head of contact reasons and routes each one: DEFLECT when one answer resolves most tickets and few reopen, AUTOMATE when agents adapt a common answer, FIX_ROOT_CAUSE when tickets reopen or describe a defect, REVIEW otherwise.
Hard rules
- Ask which clock the SLA runs on (business or calendar, timezone, holidays) before reporting attainment. Never assume.
- Open breaches count. Never report attainment on closed tickets only.
- Run
sla_check.py, don't count hours by hand. Business-hours arithmetic across evenings and weekends is where manual counts go wrong. Name each breached and at-risk ticket with the time left, and say when a clock started later than the ticket (after hours, weekend). - Staff to the interval, not the day. A daily average hides the 11:00 peak.
- Headcount and hiring order belong to capacity-planner (business-operations). This skill schedules the agents you have, interval by interval.
- Never write an article for a defect. FIX_ROOT_CAUSE goes to engineering with ticket count and hours.
- Deflection savings are an upper bound until contact rate for the topic is measured after launch.
- State every default (attainment target, service level, shrinkage, occupancy cap, concurrency, Pareto cut).
Report
Answer in the reply, not only in a file, and never edit the user's input files. Show the working a reviewer would check: the load in Erlangs (arrivals x AHT / 3600), the agent count one below the answer and the service level it misses with, scheduled = on line / (1 - shrinkage), and for each breached or at-risk ticket the time used, the time left and when its clock started (a ticket that arrives after hours or on a weekend starts at the next opening).
Scripts
| Script | Role | Exit codes |
|---|---|---|
scripts/sla_check.py | Attainment, p50/p90, breached and at-risk open tickets, backlog age, reopens | 0 ok · 2 at risk / below target · 3 bad input · 4 open breaches |
scripts/staffing_plan.py | Agents on line and scheduled per interval, roster gap | 0 ok · 2 roster short · 3 bad input |
scripts/deflection_finder.py | Pareto of contact reasons with DEFLECT / AUTOMATE / FIX_ROOT_CAUSE / REVIEW | 0 none · 2 candidates · 3 bad input |
All support --help, --sample and --output json (--format is an alias).
References and assets
references/sla_design_and_measurement.md: metrics, clocks, setting targets (5 sources)references/staffing_and_erlang_c.md: the model, its gaps, defaults (5 sources)references/deflection_and_kcs.md: deflect vs automate vs fix, KCS, honest savings claims (5 sources)assets/sla_policy.example.json,assets/tickets.example.csv,assets/intervals.example.csv
Readme
support-ops
Run a support queue on numbers from a ticket export: SLA attainment on the clock your contract uses, how many agents each hour needs, and which ticket topics belong in the help center, in a macro or in engineering's backlog. Three stdlib Python scripts; no helpdesk API, no credentials.
| Script | Answers |
|---|---|
sla_check.py | Are we meeting first-response and resolution targets in business hours? Which open tickets breach next? |
staffing_plan.py | How many agents per interval for phone and chat (Erlang C) or email (workload), and where is the roster short? |
deflection_finder.py | Which contact reasons to deflect, automate or fix at the source? |
/plugin install support-ops@claude-code-skills
/cs-support-sla tickets.csv sla_policy.json
/cs-support-staffing --intervals volumes.csv --aht 420 --concurrency 2
/cs-support-deflection tickets.csv
For headcount and hiring order from daily demand, use capacity-planner in
business-operations-skills; this plugin schedules the agents you have, hour by hour.
Agent: cs-support-ops-lead. References cite Erlang (1917), Gans, Koole and
Mandelbaum (2003), Little (1961), the KCS v6 Practices Guide and ITIL 4. License: MIT.
Details
- Marketplace
- alirezarezvani/claude-skills
- Source
- business-growth/support-ops
- Author
- Alireza Rezvani
- Category
- Business Growth
- Keywords
- customer-support, sla, helpdesk, erlang-c, staffing, workforce-management, deflection, kcs, support-operations
More from alirezarezvani/claude-skills
All 130- swedish-mentorv2.14.5
- syllabusv2.14.6
- terraform-patternsv2.14.6
- universal-scraping-architectv2.14.9
- video-content-strategistv2.14.5
- video-studiov2.14.14
- vpe-advisorv2.14.5
- weekly-reviewv2.14.5
- workflow-builderv2.14.5
- write-a-skillv2.14.9
- youtube-fullv2.14.5
- zero-hallucination-coderv2.14.5
- a11y-auditv2.14.5
- access-lifecyclev2.14.5
- aeov2.14.6
- agent-harnessv2.14.11
- agent-launcher-skillsv2.14.5
- agent-memoryv2.14.6
- agent-regression-evalsv2.14.5
- agent-run-forensicsv2.14.7
- agenthubv2.14.11
- agile-product-ownerv2.14.5
- andreessenv2.14.6
- apple-hig-expertv2.14.5
Similar to support-ops
More Business & Finance
ruflo-business-podsruvnet/ruflo82.2K starsBusiness-domain pod templates for the federated business autopilot (ADR-164 Phase 2) — pod templates plus a dry-run-by-default single-tick runner that validates
front-end-checklistthedaviddias/Front-End-Checklist74.8K starsReview frontend code and live pages against 386 quality-gated rules for accessibility, performance, SEO, security, and HTML/CSS/JS best practices.
marketing-skillscoreyhaines31/marketingskills61.1K stars53 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production,
Ahrefs AutomationComposioHQ/awesome-claude-skills51.5K starsAutomate SEO research with Ahrefs -- analyze backlink profiles, research keywords, track domain metrics history, audit organic rankings, and perform batch URL a
agentic-bundle-aas-data-analyticssickn33/agentic-awesome-skills50.1K starsInstall the "AAS Data Analytics & Business Intelligence" editorial skill bundle for Claude Code.
activecampaignanthropics/claude-plugins-official47.9K starsMarketing automation, CRM, and email marketing powered by ActiveCampaign. Manage contacts, campaigns, automations, deals, and get AI-powered marketing insights