Skills CX operations
Resolving customer identity across channels
This links people, not tickets. Deduplicating conversations that are the same request is a different job; this one asks whether the person who called on Tuesday is the person who emailed on Thursday, so that per-customer measures mean anything.
npx rulebase-skills install cx-customer-identity-resolutionWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “which customers contacted us on multiple channels”
- “how many separate tickets are actually the same person”
- “true contact rate per customer”
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 asymmetry that sets every threshold
Merging two different customers is far worse than failing to merge one.
Signals, ranked by reliability
Use them in this order, and stop as soon as a deterministic signal settles it.
The traps
Each of these produces confident false merges, and every one of them is common.
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
