Skills Compliance
Complaint root cause and remediation
Complaint root-cause analysis has a characteristic failure: the analysis is done, the themes are named, actions are assigned, the report is filed — and the complaints keep arriving at the same rate. A year later the same themes are rediscovered by a different analyst.
npx rulebase-skills install cx-complaint-root-causeWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “root cause analysis on our complaints”
- “why do we keep getting the same complaints”
- “complaint themes and remediation”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
Cause, not category
A complaint category is a reporting bucket. A cause is a mechanism you could remove.
Classify the cause by where it sits
The classification determines the owner and the remedy, and this is where the analysis earns its keep: Product or service defect, Process design, Communication, Handling, Expectation set at sale, Customer error, with a design contribution.
Complaints are the tip
Every complaint category has a much larger silent population who had the same experience and did not complain. Complaint propensity varies enormously by segment, channel, product and customer confidence — so complaint volume is a poor proxy for harm volume, and ranking causes by complaint count systematically under-weights issues affecting customers least likely to complain.
Track remediation to outcome, not to completion
This is the part that fixes the recurring-theme problem. For each cause: A named owner and a specific change, not "review the process", A measurable prediction, The verification result, recorded.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
