Created with AI.
Queues determine whether cases get seen. This guide shows you how to set them up without ending up with twenty queues that no one monitors.
The question is who can resolve the issue, not which department they belong to. A queue for billing questions and one for technical issues makes sense. A queue for each employee does not — then you have reinvented the inbox.
A queue without defined members is a queue no one feels responsible for. Also be clear about who is responsible when no one picks up an item — this is usually the team lead.
Queues are created in the Customer Service settings. You then define rules for where cases are routed—typically based on the recipient address, case type, or customer.
Let caseworkers pick cases themselves when the team is small and mature—it provides flexibility. Use automatic assignment when volumes are high or when some people systematically pick the easiest cases. Both approaches work; what does not work is leaving it unclear.
The biggest risk with queues is that a case gets left unattended because everyone assumes someone else will handle it. An alert when a case has remained unassigned for a set number of hours eliminates almost the entire problem.
Look at how long cases remain in the queue before someone picks them up. If that wait is long, it does not help that the actual resolution is quick—the customer will still experience poor service.
Ask a question or share what helped you.

Customer Service | Article
WEM MCP tools enabled time-off requests, shift swaps and shift bids in Service Agent. Administrators could enable each tool for a role, team or pilot group.

Project management | Event
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.

Automation | Article
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.

Customer Service | Article
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.

Customer Service | Article
Service Agent became generally available across Dynamics 365 and Microsoft 365. Workforce Engagement Management connected demand, staffing and quality work.

Sales | Article
Gartner found nearly five hours saved per seller each week, but many organisations did not reinvest the time. Dynamics wave 1 described connections across customer insight, sales, service and field work.
Do you have a question or experience to share?
Be the first to contribute.