agentsclimarketplace

Csat root cause

Skill SkillMedev/customer-support-copilot/skills/csat-root-cause

Six skills to resolve faster, escalate smarter, and turn tickets into self-service.

Install
npx -y skills add SkillMedev/customer-support-copilot --skill csat-root-cause

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyzes CSAT and NPS verbatims to surface root-cause themes and prioritize fixes by frequency and impact. Use when interpreting customer satisfaction data to inform product or process decisions.

SKILL.md

3.7 KB, as published. Nobody here has run it

CSAT Root Cause Analysis

Raw CSAT scores tell you that something is wrong. Verbatim comments tell you what and why. The goal of root-cause analysis is to turn hundreds of individual comments into a ranked list of fixable problems.

Data preparation

Before analyzing, filter the dataset: remove blank verbatims, remove comments that mention only a specific agent by name (these are agent-performance signals, not product/process signals), and separate detractor verbatims (score 0-6 on NPS, 1-3 on CSAT) from promoter verbatims. Analyze detractors first - they drive churn.

Coding scheme

Apply a two-level coding scheme. Level 1 is the broad category (product bug, slow response time, unclear communication, pricing confusion, onboarding friction, feature gap, policy frustration). Level 2 is the specific sub-theme within that category. Code each verbatim with exactly one Level 1 and one Level 2 code. If a verbatim contains multiple distinct complaints, split it into sub-comments before coding.

Prioritization matrix

After coding, calculate two numbers for each theme: frequency (what percentage of verbatims mention it) and impact (what is the average CSAT score for tickets that mention it versus those that do not). Plot themes on a 2x2 matrix: high frequency + high impact = fix immediately, high frequency + low impact = quick wins, low frequency + high impact = critical edge cases, low frequency + low impact = monitor.

Presenting findings

Report findings as: the top three to five themes by priority, with verbatim examples for each, a proposed fix or owner for each theme, and a success metric (what does a fixed version look like in the data). Avoid reporting a theme without a proposed action - analysis without a recommendation is noise.

Thresholds that signal urgency

Escalate immediately if any single theme appears in more than 15% of detractor verbatims within a 30-day window, or if average CSAT for a theme drops below 2.5/5. These thresholds indicate systemic failure, not statistical noise.

Deliverable

Produce a root-cause report containing: the coded verbatim dataset (every comment tagged with one Level 1 and one Level 2 code), the frequency-by-impact matrix, the top three to five prioritized themes each with two or three representative verbatims, a proposed fix and named owner per theme, and the success metric that will show in the data when each fix has worked.

What to avoid

  • Do not present word clouds - they conflate frequency with font size and obscure causality.
  • Do not conflate correlation with causation; a theme appearing alongside low scores does not prove it caused the low score without further validation.
  • Do not analyze fewer than 30 verbatims; sample size below that produces unreliable theme distributions.
  • Do not pool detractor and promoter comments into one analysis - the same theme (e.g. pricing) means different things in each population.
  • Do not report a theme supported by fewer than 5 verbatims as a trend; call it an edge case and monitor it.

Quality bar

  • Every theme is scored on both frequency and impact - never prioritized on mention count alone.
  • Each reported theme carries a proposed action, an owner, and a success metric, not just a description.
  • Detractors and promoters are analyzed separately, and the escalation thresholds (15% of detractors in 30 days, theme CSAT below 2.5/5) are checked explicitly.
  • Verbatim examples are quoted, not paraphrased, so the reader can audit the coding.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.