본문으로 건너뛰기
cccskills
무료GitHub에 공개

"cs-analytics"

"Measure and optimize customer service performance using CSAT, NPS, CES, First Contact Resolution, and text mining on support tickets. Use this skill when the user needs to evaluate CS team performance, identify top complaint drivers, optimize staffing, or build CS dashboards — even if they say 'is our CS team doing well', 'what are customers complaining about', 'how many agents do we need', or 'build a CS dashboard'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

  • SKILL.md5.3 KB
  • examples/sample_scenario.md5.9 KB
  • references/nps-methodology.md9.2 KB
  • references/ticket-text-mining.md12.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Customer Service Analytics

Framework

IRON LAW: Measure Satisfaction AND Efficiency — Never Just One

High CSAT with terrible resolution time = unsustainable (agents spend
too long per ticket). Fast resolution with low CSAT = cutting corners.
Both dimensions must be tracked and balanced.

Key Metrics

Satisfaction Metrics

MetricWhat It MeasuresHow to CollectBenchmark
CSATSatisfaction with specific interactionPost-interaction survey (1-5 scale)> 4.0/5
NPSLikelihood to recommend"How likely to recommend?" (0-10)> 30
CESEffort required to resolve"How easy was it to resolve?" (1-7)> 5.0/7

Efficiency Metrics

MetricFormulaBenchmark
First Contact Resolution (FCR)Resolved on first contact / Total contacts> 70%
Average Handle Time (AHT)Total handle time / Total contacts5-8 min (varies by industry)
Average Response TimeTime from ticket creation to first response< SLA target
BacklogOpen tickets / Daily throughput< 1 day
Escalation RateEscalated tickets / Total tickets< 20%
Reopen RateReopened tickets / Resolved tickets< 5%

Operational Metrics

MetricFormulaUse
Ticket VolumeTickets per day/week/monthStaffing planning
Channel Mix% by channel (email, chat, phone, LINE)Resource allocation
Peak HoursVolume by hour-of-dayShift scheduling
Category Distribution% by issue typeProcess improvement priority

Analysis Workflows

1. Top Contact Reason Analysis

  • Categorize all tickets by reason (auto-tag or manual)
  • Pareto chart: top 5 reasons usually account for 60-80% of volume
  • For each top reason: can it be self-served? Automated? Eliminated at source?

2. Text Mining on Tickets

  • Extract frequent keywords/phrases from ticket descriptions
  • Cluster into topics (LDA, BERTopic, or simple TF-IDF)
  • Identify emerging issues (new topics appearing in recent weeks)
  • Sentiment analysis on customer messages

3. Staffing Optimization

Required Agents = Peak Hour Volume × AHT / (60 × Utilization Target)

Example: 50 tickets/hour × 8 min AHT / (60 × 0.75 utilization) = 8.9 → 9 agents

Add buffer for breaks, meetings, and training (~15-20%).

4. Agent Performance

MetricCompareAction
Individual CSAT vs team avgIdentify coaching needsTraining for below-average
Individual AHT vs team avgIdentify efficiency gapsShadow high-performers
FCR by agentIdentify knowledge gapsKnowledge base improvements

VOC (Voice of Customer) Tracking

SignalSourceFrequency
Emerging complaintsTicket text miningWeekly
Feature requestsTagged tickets + surveysMonthly
Churn signals"Cancel" intent tickets, low CSAT patternsWeekly
Praise patternsHigh CSAT + positive commentsMonthly (share with team)

Output Format

# CS Analytics Report: {Period}

## Summary Dashboard
| Metric | Current | Prior | Target | Status |
|--------|---------|-------|--------|--------|
| CSAT | {X}/5 | {X}/5 | >4.0 | 🟢/🟡/🔴 |
| FCR | {%} | {%} | >70% | 🟢/🟡/🔴 |
| Avg Response Time | {hrs} | {hrs} | <{X}hrs | 🟢/🟡/🔴 |
| Ticket Volume | {N} | {N} | — | ↑/↓ |

## Top Contact Reasons (Pareto)
| # | Reason | Volume | % | Self-Servable? |
|---|--------|--------|---|---------------|
| 1 | {reason} | {N} | {%} | Y/N |

## Emerging Issues
{New topics detected in text mining this period}

## Staffing
- Current agents: {N}
- Required (based on volume): {N}
- Gap: {over/under-staffed by N}

## Recommendations
1. {highest-impact improvement}

Gotchas

  • CSAT response bias: Only 10-20% of customers respond to surveys, usually the very happy and very unhappy. The silent majority's experience is unknown. Supplement with behavioral data (repeat contact, churn).
  • NPS is strategic, CSAT is tactical: NPS measures overall brand loyalty (long-term). CSAT measures specific interaction quality (short-term). Don't use NPS to evaluate individual agents.
  • AHT optimization can hurt quality: Pressure to reduce AHT may cause agents to rush, reducing FCR and CSAT. Optimize FCR first, then look at AHT.
  • Ticket categorization drift: Categories become outdated as products evolve. Review and update the category taxonomy quarterly.
  • Correlation ≠ causation in CS data: "Agents who use more templates have higher CSAT" might mean templates help, OR that experienced agents (who happen to use templates) are just better.

References

  • For NPS survey design, see references/nps-methodology.md
  • For text mining on support tickets, see references/ticket-text-mining.md

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

"Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

charlieviettq의 스킬 모두 보기

이 스킬의 문제 신고