Created with AI.
Routing rules determine who gets what. This guide presents a simple model that works, rather than a set of rules no one understands.
The first version should only send chat messages to the chat queue and emails to the email queue. Get it working, and build from there.
Route by topic or customer type when you have queues that are actually distinct. Routing to five queues with the same agents achieves nothing.
Rules are evaluated from top to bottom, and the first match wins. Put the most specific ones at the top; otherwise, a general rule will match everything.
Anything that doesn't match a rule has to go somewhere. Without a final rule, requests are left without a queue and are almost invisible.
Take ten inquiries from last week and check where they would have ended up. This reveals gaps faster than reading the rules.
See how many end up in the catch-all queue. If the proportion is high, you are missing a rule—or the rules are too narrow.
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.