Skills CX operations
Skills matrix and multi-skilling
The usual skills matrix is a spreadsheet of checkboxes: who has been trained on what. That tells you almost nothing about who can handle what at the level your customers and SLAs require. Worse, it is read as free capacity — "we have 40 people and 60 skills, so we have coverage" — and routing is built on that fiction until quality and handle time move in the wrong direction.
npx rulebase-skills install cx-skills-matrixWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “skills matrix”
- “who can handle what”
- “cross-training plan”
- “multi-skill our team”
- “build a capability map”
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.
Step 1: define the capability units
List capabilities at the granularity routing actually uses — not org-chart labels.
Step 2: build the matrix from work, not from people
Start from contact drivers and channels (or whatever your routing strata are). For each stratum, record: Volume share and seasonality, Current primary owners (team, site, or queue), Minimum Independent headcount needed for coverage (see below), Gap.
Step 3: size coverage honestly
Coverage math most teams get wrong.
Step 4: cross-training ROI
Before approving a cross-training wave, compare.
Step 5: routing implications
The matrix is not complete until ops agrees what changes: Primary vs overflow routing, Proficiency gates, Decay rules, New-work policy.
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
