Purpose
Take a contact center's current operational metrics, benchmark each against industry-appropriate standards, rank the gaps by financial and experience impact, and prescribe concrete improvement levers for every lagging metric — so leaders know exactly which two or three moves will produce the most value before allocating budget or headcount.
When to Use
Invoke this skill when the user asks to:
- Benchmark contact center metrics against industry standards
- Diagnose why cost-per-contact, AHT, or CSAT is off target
- Identify the biggest performance gaps in customer operations
- Build an operational improvement plan or roadmap for the support org
- Prepare a QBR, board deck, or executive review of contact center performance
- Prioritize which KPI to fix first given limited resources
Inputs Required
Before starting, collect:
- Current metrics: As many as available — AHT, FCR, CSAT, cost-per-contact, deflection rate, agent utilization (plus optional: abandon rate, transfer rate, occupancy, adherence, NPS)
- Industry/vertical: The sector (e.g., SaaS, retail/e-commerce, telecom, financial services, healthcare) — benchmarks vary meaningfully by vertical
- Contact channels: Voice, chat, email, self-service — and rough volume mix
- Team size: Number of agents / FTEs and any BPO/outsourced mix
- Monthly contact volume: Total contacts handled per month
- Primary goal: The metric or outcome leadership most wants to move (cost, CSAT, efficiency, deflection)
- Any recent changes: Tooling, staffing, policy, or volume shifts in the last 90 days
If industry is not specified, default to a cross-industry blended benchmark and state the assumption. If cost-per-contact is missing but volume and headcount are known, estimate it and flag the estimate.
Instructions
Step 1: Normalize and Validate the Inputs
Before benchmarking, sanity-check the metrics.
- Confirm each metric is expressed in standard units: AHT in seconds or minutes, FCR/CSAT/deflection/utilization as percentages, cost-per-contact in currency per contact
- Flag any metric that is internally contradictory (e.g., high FCR paired with high transfer rate, or high utilization paired with low occupancy)
- Note which requested benchmarks cannot be computed due to missing inputs and proceed with what's available
Step 2: Benchmark Each Metric Against Industry Standards
Compare each provided metric to the appropriate range. Use these general benchmark bands, adjusted for the stated industry:
- AHT (Average Handle Time): Voice 4–6 min; Chat 8–12 min (concurrent); Email 8–24 hrs response. Lower is not always better — cutting AHT at the expense of FCR is a false economy.
- FCR (First Contact Resolution): 70–79% is solid; 80%+ is strong; below 65% signals process or knowledge gaps. FCR is the single highest-leverage metric — it drives cost, CSAT, and volume simultaneously.
- CSAT: 75–85% is typical; 85%+ is strong; below 70% is a warning. Interpret alongside response rate.
- Cost-per-contact: Voice $6–$12; Chat $3–$7; Email $2.50–$5; Self-service $0.10–$1. Vertical and geography shift these substantially.
- Deflection rate (self-service containment): 20–40% is common; 40–60% is strong for mature self-service; below 15% signals under-invested help content or bots.
- Agent utilization: 60–75% is the healthy zone. Above 85% causes burnout and attrition; below 55% signals overstaffing or forecasting problems.
For each metric, classify as: On/Above Benchmark, Slightly Below (within ~10% of the band), or Significant Gap (>10% off the band). State the benchmark band used and the industry adjustment applied.
Step 3: Quantify and Rank the Gaps
Translate each gap into impact, then rank.
- Financial impact: Estimate annualized cost of the gap where possible (e.g., a 5-point FCR shortfall across monthly volume → repeat contacts × cost-per-contact × 12; excess AHT → additional agent-minutes × loaded rate)
- Experience impact: Note effect on CSAT/NPS and churn risk for gaps that touch the customer directly
- Rank the gaps: Order from largest to smallest combined impact — not alphabetically, not in the order provided
- Identify the top 2–3 priority gaps that would produce the most value if closed
Step 4: Prescribe Improvement Levers for Each Lagging Metric
For every metric classified as Slightly Below or Significant Gap, provide specific levers. Draw from these lever sets:
- FCR levers: Knowledge base gap analysis on top repeat-contact reasons; agent authority/policy loosening to resolve without escalation; skills-based routing; post-contact "issue fully resolved?" survey to measure true FCR
- AHT levers: Guided workflows/decision trees for complex contacts; desktop consolidation to cut screen-switching; targeted coaching on the longest-handling reason codes; macro/canned response library for chat and email
- CSAT levers: Root-cause the lowest-scoring contact reasons and QA tags; sentiment-triggered escalation; agent coaching tied to verbatim comments; fix the top 3 process failures behind detractor comments
- Cost-per-contact levers: Shift volume to lower-cost channels; deflect top repeat reasons to self-service; right-size staffing against forecast; automate after-call work
- Deflection levers: Publish/optimize help content for the top 10 contact reasons; deploy or tune a bot on high-volume low-complexity intents; surface self-service at the point of need (in-product, IVR, pre-chat); measure containment vs. escalation-after-bot
- Utilization levers: Improve forecasting and scheduling accuracy; introduce flexible/part-time shifts for peak coverage; rebalance channel staffing; address shrinkage (adherence, breaks, off-phone time)
For each lever, note: expected magnitude (rough range of improvement), time-to-impact (Quick <30 days / Medium 1–3 mo / Long 3–6 mo), and effort/cost (Low/Medium/High).
Step 5: Build the Priority Action Plan
Turn the top gaps into a sequenced plan.
- List the top 5 actions in priority order, each tied to a target metric and the expected point-improvement
- Sequence quick wins first, then medium-horizon structural fixes
- State the one metric to fix first and why, with an explicit rationale
- Define the leading indicators to watch weekly so leadership knows early whether each action is working
Output Format
- Structure: Benchmark comparison table → ranked gap analysis → improvement levers per lagging metric → priority action plan
- Length: 900–1,300 words
- Format: Benchmark comparison as a table (Metric | Current | Benchmark Band | Status | Gap); levers and action plan as structured bullets
- Sections: Input validation notes → Benchmark comparison table → Ranked gap analysis with impact estimates → Improvement levers by metric → Top 5 priority action plan → Metric to fix first
- Tone: VP of Customer Operations — analytical, direct, financially literate, action-first. No filler.
Quality Checklist
Before delivering output, verify:
- [ ] Every provided metric appears in the benchmark table with a status classification and the benchmark band used
- [ ] The industry-specific benchmark adjustment is stated, not just applied silently
- [ ] Gaps are ranked by quantified impact (financial and/or experience) — not by input order
- [ ] Every lagging metric has at least 3 specific levers, each with magnitude, time-to-impact, and effort labels
- [ ] The action plan names one metric to fix first with an explicit rationale
- [ ] Any estimated or missing inputs are flagged, not presented as exact
Notes
- FCR is usually the highest-leverage metric in the entire scorecard — improving it reduces volume, cost, and dissatisfaction at once. When in doubt about where to start, start there.
- Beware AHT tunnel vision: a low AHT paired with a low FCR means agents are ending contacts fast without resolving them, which inflates repeat-contact volume and cost.
- Utilization above 85% predicts attrition; a "gap" here is a warning to reduce load, not a target to push higher.
- If self-service deflection is low, it is often the fastest cost lever available — help-content and bot fixes on the top 10 contact reasons typically pay back within a quarter.
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills