We are announcing the ability to use planning groups to treat multiple queues as a single unit to calculate the capacity that is needed for operations more efficiently within Dynamics 365 Customer Service and Dynamics 365 Contact Center. This feature reached general availability on August 31, 2026.
How does this affect me?
With this feature, instead of building capacity plans for each queue and manually calculating overall staffing needs across queues, planning groups can combine queues to more efficiently plan capacity by considering the entire pool of staff shared across queues as a single unit. When a plan is built from a forecast scenario, the planning group is derived automatically from that scenario, keeping the forecast and capacity plan aligned to the same group with no additional input from the planner.
To use Workforce Management capabilities, an administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.
What action do I need to take?
This message is for awareness, and no action is required.
If you would like more information on this feature, please visit Create capacity plans for planning groups.
Changes › MC1465492
Dynamics 365 Customer Service - Create capacity plans for planning groups
- Published
- 01 Sep 2026
- Last modified
- 01 Sep 2026 10:14 UTC
- Act by
- —
- Ends
- 01 Oct 2026
- First archived
- 01 Sep 2026
- Revisions
- 1
- Tags
- New feature
Full post
Related messages
- MC1485169 Dynamics 365 Contact Center - Use role-based enforcement for recording and transcription downloads
- MC1538980 Dynamics 365 Contact Center - Orchestrate conversation distribution with natural language playbooks
- MC1538962 Dynamics 365 Contact Center - Use bullseye routing with user groups to orchestrate conversations
- MC1536059 Microsoft 365 Copilot: Conversation orchestration expands routing and overflow capabilities
- MC1526697 Dynamics 365 apps and Dataverse – Information about the 2026 time zone changes in Canada
Discussion
No messages yet — start the thread.
© Microsoft — archived from the Microsoft 365 Message Center. Content notice