What is changing
After conversation work presence is a system-generated status. It is set when a customer service representative is finishing tasks after an interaction, such as writing notes, updating records, selecting dispositions, or completing follow-up actions. Instead of showing a generic Busy or Do Not Disturb, the representative appears as one of two states:
- Busy – After Conversation Work
- DND – After Conversation Work
Representatives can't change this status. The system applies it according to how an administrator configured the workstream in Copilot Service admin center. Once the feature is enabled, supervisors can view and filter representatives by these statuses.
Microsoft's Message Center post (MC1484604) says the feature removes ambiguity: supervisors can tell agents doing wrap-up work apart from representatives who are generally Busy or in DND. The presence status is set by the system and looks different from manually set or system-evaluated Busy/DND states.
Rollout status and scope
- The roadmap entry lists the status as Rolling out, with General Availability, Web, and Worldwide (Standard Multi-Tenant) scope.
- The estimated GA date is October 2026. The Message Center post says the feature will reach general availability on October 30, 2026.
- Roadmap dates are estimates. "Rolling out" means deployment has started but may not have reached every customer. Don't assume it's in your tenant yet.
- One third-party summary of the announcement describes it as mainly informational, with no required action and limited configuration impact. That means no enablement step was announced. It doesn't mean your configuration is automatically correct.
An earlier, related announcement
An earlier Message Center item, MC1429024, covered Dynamics 365 Customer Service and Contact Center. It described two new custom presences in Copilot Service admin center that let supervisors distinguish wrap-up work from other Busy or DND time. It placed them under Productivity > Custom presence > Manage > Active Presences. It also said "Wrap-up" must be configured to block capacity for the status to take effect. That item was dated July 2026. The roadmap item covered here is a separate Contact Center announcement. I couldn't confirm how the two relate, so don't treat them as one rollout.
How wrap-up and capacity settings fit in
Keep three things separate: presence, conversation state, and capacity. The new feature adds presence labels. It doesn't redefine how long a representative is blocked.
Microsoft Learn's conversation-state documentation defines Wrap-up as an intermediate state. It begins after the representative ends the conversation. The representative then does post-conversation work, such as taking notes and updating customer information, before the conversation moves to Closed. The workstream's Block capacity for wrap up setting controls what happens to capacity during that time.
| Setting | Documented behavior |
|---|---|
| Always block | The default. Capacity stays consumed until the representative or a supervisor closes the conversation, or the system closes it automatically based on the configured time. |
| Don't block | Capacity is released immediately when the conversation enters Wrap-up. |
| Custom time | Capacity is blocked for a duration of 30 seconds to 60 minutes. When it elapses, the system releases capacity and automatically resets presence. |
These settings live in the Work distribution area of a workstream in Copilot Service admin center. One documented exception applies: if the capacity profile uses End of Day mode, capacity isn't reset when the wrap-up duration ends.
The roadmap text labels its three options "Always block," "Custom time," and "Don't block." They match the Learn setting names, so the existing configuration is the likely driver. Learn doesn't describe the new statuses, so this link is my inference.
Details worth knowing
- End versus close: Learn says the End button moves a conversation to Wrap-up. Closing with the X button without ending first behaves differently. Voice and chat conversations return to Open for reassignment. Persistent chat and asynchronous conversations move to Waiting, and their capacity is released immediately. A representative who closes with X may therefore never show wrap-up status.
- Transfers: If Wrap up after transfer is enabled in Copilot Service admin center and wrap-up capacity blocking is configured, the first representative's session enters Wrap-up when the conversation is transferred. The second representative's session becomes active. In the always-block case, Learn says the system releases capacity after 15 minutes. That figure comes from the transfer-specific explanation, so don't apply it to all wrap-up.
- Live chat disconnects: Learn says active conversations move automatically to Wrap-up when a live chat disconnects.
What admins and supervisors should do
- Review the Block capacity for wrap up setting on each workstream. Don't-block workstreams may not hold capacity during wrap-up. The previous Message Center item says blocking is needed for the status to take effect.
- If you use Custom time, check that the duration fits how long your wrap-up work really takes. After it expires, the system releases capacity and resets presence.
- Check capacity profiles for End of Day mode, because of the documented exception above.
- Tell supervisors the new statuses are system-applied, so representatives can't select them manually.
- After rollout reaches your tenant, test with a pilot workstream. Confirm that the labels appear and that supervisor filtering works as expected.
Limits of the evidence
I found no Microsoft Learn procedure for enabling or filtering by the new statuses. I can't point to a specific dashboard, grid, or menu path for supervisor filtering. I also can't confirm per-tenant availability, licensing requirements, or behavior outside the listed Worldwide Standard Multi-Tenant and Web scope. Confirm those in your Microsoft 365 Message Center and in your own environment.
The takeaway
The new labels improve visibility without changing the underlying workstream rules. A supervisor looking at a wallboard can now tell whether a "Busy" agent is on a call, in a break, or finishing a disposition. Whether that is more useful depends on how well your wrap-up capacity settings match your real workflow.
References
- Dynamics 365 Contact Center: Use after conversation presence status for wrap-up activities Microsoft 365 Roadmap · 2026-11-17T22:45:29.907242Z
- Understand conversation states in Dynamics 365 Contact Center | Microsoft Learn learn.microsoft.com
- Microsoft Copilot Roadmap | Microsoft 365 microsoft.com