Routing rules in Dynamics 365 Customer Service

How a case or conversation gets to the right agent is the question every Customer Service implementation grapples with. Dynamics 365 ships two routing engines — a simple, legacy one and a modern, AI-aware one — and customers should adopt the modern one.

Basic routing rules. The legacy mechanism is a list of basic routing rule sets with conditional logic that assigns incoming cases to queues based on attributes (priority, channel, product line). Basic rules are easy to set up, run synchronously on case creation, and don't consider agent capacity or skills. They're still in use on simpler tenants but are increasingly being replaced.

Unified Routing. The modern engine. Unified Routing handles cases, conversations (chat, voice, SMS, social), records of any other entity, and emails through a single configuration. It runs in three phases:

1. Classification. Incoming work is enriched with derived attributes: priority based on customer tier, language detected by AI, sentiment from the email body, product category from the subject. Classification rules are configured per channel and can call AI models.
2. Routing rule sets. A set of rules evaluates the classified work and assigns a queue — typically a queue per skill area, region, or service tier.
3. Assignment. Within the queue, an assignment method picks an agent: longest-idle, round-robin, highest-priority-first, or percentage-based for blended skills. Assignment honours agent capacity (how many active items each agent can handle), operating hours, and presence status.

Skills. A skills hierarchy is configurable; agents are tagged with skills and proficiency levels. Routing rules can require a skill match — only Spanish-speaking agents handle Spanish chats; only senior agents handle escalations. Skills are also AI-recommended based on conversation analysis.

Capacity profiles. A capacity profile declares how much work an agent can hold simultaneously per channel — typically 1 voice call, 3 chats, 5 cases. Routing respects the profile and queues work that exceeds capacity.

Overflow and escalation. Time-based overflow re-routes work that's waited too long; manual reassignment by supervisors covers the edge cases.

Telemetry. Real-time supervisor dashboards show queue depths, longest waits, agent occupancy, and SLA risk, with the ability to intervene.

Migration. Microsoft is gradually deprecating basic routing in favour of Unified Routing. New implementations should configure Unified Routing from day one.

Configuration discipline. Routing complexity grows quickly — one rule turns into twenty. Start with a small skill taxonomy, a flat queue topology, and a handful of routing rules; add complexity only when measured queue wait times or quality metrics demand it.