Skills CX operations
Sampling conversations
Every manual review of support conversations is a sample, including the ones nobody calls a sample. The question is only whether it was drawn deliberately.
npx rulebase-skills install cx-conversation-samplingWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “which tickets should we review”
- “how do we pick a sample”
- “is our QA sampling representative”
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.
The frame comes first
The sampling frame is the list of conversations you could have drawn from. Almost every generalisation failure is a frame problem, not a size problem.
Choose the design to match the question
Simple random. The default, and correct when you want one overall estimate. Boring and defensible. Use it unless you have a specific reason not to.
Sampling for QA coverage
Ongoing QA sampling is the same problem with an extra constraint: it must also be fair to the people being measured.
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
