Skills CX operations
WIP limits
Concurrency and WIP limits look like capacity levers. Used wrong, they are quality destroyers dressed up as free capacity.
npx rulebase-skills install cx-wip-limitsWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “how many chats per agent”
- “concurrency settings”
- “WIP limits”
- “agents juggling too many tickets”
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.
Chat concurrency: the false free lunch
Each concurrent chat adds: Context-switching cost between threads, Staggered response times as the agent finishes another reply first, Risk of wrong-thread replies (quality and compliance incident), Perceived ghosting when gaps exceed channel norms.
Personal WIP for async work
Email, messaging tickets, and back-office tasks accumulate as open work per agent. Without a WIP cap, the backlog is invisible until SLAs breach — and the breach looks like an individual failure when it was a system with no limit.
Team and queue WIP
Above personal limits, some operations cap queue WIP — total open not-yet-assigned work — to force staffing or overflow decisions instead of infinite backlog absorption.
Limits as policy, not secret shame
Publish limits where agents and planners see them: Personal async WIP by queue type, What happens at limit.
Relationship to occupancy and scheduling
High occupancy from concurrency is not the same as efficient staffing: Occupancy, Concurrency.
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
