Classification, then assignment

Learn it in 5 minutes

The unified-routing overview applies to Dynamics 365 Contact Center embedded, Contact Center standalone, and Customer Service. It says unified routing has two stages. In classification, rules and machine-learning models can add information on the work item. In assignment, requests are prioritized and then assigned using the nature of the work, related entities, skills, and the current availability and workload.

The page says you configure unified routing in the Copilot Service admin center, and that representatives must use the Copilot Service workspace app to be assigned work. It says unified routing is not supported in Unified Service Desk. Intelligent skill finder depends on an AI Builder category classification model, so AI Builder has to be available in the region where you use it. The page says unified routing is supported in the same regions as Dynamics 365 Contact Center. This room does not copy that region list.

Unified routing classifies a work item, then assigns it. Representatives use Copilot Service workspace. Unified Service Desk is not supported.

Room HTML

Visual

SVGPNGHTML

Worked example

Classification adds information. Assignment uses it. They are not the same stage.

1. Classify Rules or ML models add information
2. Assign Priority, skills, availability, workload
3. App Copilot Service workspace
4. Limit Not Unified Service Desk

If it fails: A skill is missing and the assignment method is rebuilt before anyone checks classification.

Checklist HTML

Quiz

Flashcards

Ecosystem

Glossary

• Least active assignment The assignment-methods page says least active is available for voice and messaging only, and is the default selection when you create a voice or messaging queue. Config: The page says the last-capacity-release data is in msdyn_agentchannelstate. It also says not to use the feature for employment decisions. Fault: Least active is promised on a record queue.
• Quality evaluation plan The quality and coaching page, which applies to Dynamics 365 Contact Center only, says an evaluation plan sets the criteria, the conversations, the timing, and the actions. Config: The page names the Omnichannel Administrator role, plus consumption-based billing and capacity. It says not to use the feature for employment decisions. Fault: A plan is activated before any indicator exists in the quality library.
• Quality guardrail On the quality and coaching page, a guardrail defines a required or prohibited behavior. Guardrails are evaluated for violations rather than assigned numeric scores, and each has a priority. Config: Set priority and optional nudge text, then activate the guardrail before you add it to a plan. Fault: A prohibited behavior is given a numeric score because the indicator form was copied.
• Short-term forecast The forecasting overview says a short-term scenario predicts volume and average handle time in 15-minute intervals for a horizon of up to six weeks (42 days), using a linear trend on internal or external data. Config: The same page says a long-term scenario is daily, up to three years (1,096 days). Weighted average is marked preview. Fault: A six-week forecast is read as a daily three-year plan.

Sister technologies

Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.

Config and troubleshooting

A skill is missing and the assignment method is rebuilt before anyone checks classification.

Cross-platform bridges

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem