Utarbeidet med KI.
Skills-based routing requires that skills are registered and kept up to date. Here is the setup and the pitfall that causes inquiries to remain unassigned.
Languages and two or three areas of expertise are enough for most people. Twenty skills result in a model that no one maintains and that produces requests with no match.
Each agent is assigned the skills they actually have. Have the team leader confirm the list—self-reporting tends to be either too modest or too optimistic.
Specify which skills are required for each type of inquiry. Be careful when requiring multiple skills at the same time—each requirement reduces the number of available agents.
This is the most important setting. If no agent with the right skills is available, the requirement must either be relaxed automatically after a certain period of time, or the inquiry must be sent to a catch-all queue. Otherwise, it will remain there until someone notices it.
People change roles. A skills model that is not maintained routes tasks to the wrong people and makes the system seem unreliable.
Still et spørsmål eller del hva som hjalp deg.

Publisert 7.10.2024
En portalløsning er en smart investering for mange virksomheter. Den gir ikke bare bedre kundeopplevelser og økt brukervennlighet, men også muligheten til å kutte betydelige kostnader gjennom effektiv selvbetjening.
Les merPublisert 1.10.2025
Det siste året har det skjedd mye i Dynamics 365 Customer Service - først og fremst innenfor AI og automatisering: Smartere verktøy, oversettelse i sanntid og trygg håndtering av data. Det gir bedre kundeopplevelser og mer effektive serviceteam.
Les merHar du et spørsmål eller en erfaring å dele?
Bli den første som bidrar.