Skills CX operations
Cost to serve
Cost per contact is the number that unlocks budget and justifies automation, which is exactly why it is usually built to reach a conclusion. The two failure modes are a denominator chosen to flatter and a savings claim that counts money nobody will stop spending.
npx rulebase-skills install cx-cost-to-serveWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “what does a ticket cost us”
- “cost per contact”
- “what would automating this save”
- “cost to serve by segment”
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.
Build the cost base explicitly
State what is in and what is out. The number varies by a factor of two or more depending on this, so a cost per contact quoted without its basis is not comparable to anything.
Allocate by time, not by count
Contacts are not interchangeable. A two-minute password reset and a ninety-minute dispute cost very different amounts, so allocating total cost evenly across contacts makes cheap contact types look expensive and expensive ones look cheap — which systematically points automation at the wrong work.
Automation savings: the part that is usually wrong
A deflection business case typically multiplies contacts avoided by fully-loaded cost per contact. That number is nearly always too high, for four reasons worth stating plainly.
Where the money actually is
Rank contact drivers by total cost — volume × allocated cost — not by unit cost. The expensive-per-contact drivers are usually rare, and the ranking by unit cost sends teams to fix work that barely registers in the budget.
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
