Created with AI.
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.
Ask a question or share what helped you.

Published 10/7/2024
A portal solution is a smart investment for many businesses. It not only improves the customer experience and usability, but also offers the opportunity to significantly reduce costs through efficient self-service.
Read morePublished 10/1/2025
A lot has happened in Dynamics 365 Customer Service over the past year—primarily in AI and automation: smarter tools, real-time translation, and secure data handling. This results in better customer experiences and more efficient service teams.
Read moreDo you have a question or experience to share?
Be the first to contribute.