Plan requirement
| Subscription | Suite Growth or higher, Support Professional or higher |
| Access | Admin |
Skills describe what an agent can handle, so work reaches somebody able to do it rather than whoever is next.
How they work
You define skill types and values. Agents are given the skills they have. Tickets are given the skills they need, by rule. Routing then only offers a ticket to agents with the matching skills.
Skills or groups
The distinction worth getting right before you build anything.
- Groups are organisational. Who someone works with, what queue they belong to.
- Skills cut across groups. A language, a product, a certification, held by people in several teams.
Modelling a team as a skill produces two systems doing one job. Modelling a language as a group produces people in five groups.
The three that are almost always worth it
- Language. The clearest case. Either someone can answer in Dutch or they cannot.
- A specialist product that only a few people know.
- A certification or authorisation that legally or contractually matters.
Where it goes wrong
Too many skills. Each one narrows who can take a ticket, and several combined can narrow it to nobody. A ticket needing three skills held by one person waits until that person is free, and if they are on holiday it waits all week.
The failure is silent: work sits in the queue and everyone looks available.
Start with one
Language, usually. Run it for a month, look at what waits and why, then decide whether a second is worth its cost.
Comments
0 comments
Article is closed for comments.