What it does
Lets reps and supervisors handle WEM scheduling requests through Service Agent in natural language, instead of opening the workforce management app. Service Agent picks the right Model Context Protocol (MCP) tool, runs it in the background against Customer Service and Dataverse, and shows the result in the conversation. A supervisor can ask for pending time-off requests, open a specific one, and approve or reject it without leaving the chat.
Key facts
- Three tools ship in this set:
list_wem_requests(list and filter time-off, shift swap, and shift bid requests),get_wem_request_details(full record and scheduling context for one request), anddecide_wem_time_off_request(approve or reject a pending time-off request). - The decision tool is time-off only. It won't approve or reject shift swap or shift bid requests — those are list/detail only for now.
- A rejection must carry a reason, which is saved on the request. The decision also stamps the reviewer and the review time.
- Responses are role-scoped by ordinary Dynamics 365 and Dataverse security: supervisors see their planning group, reps see only their own submissions. Nothing here bypasses row-level access.
- Reps and supervisors never call the tools directly — they talk to Service Agent, which invokes them. The tools are building blocks for the conversational experience, not a UI.
When to use / skip
Use it when you're already running Service Agent and want supervisors to clear time-off approvals or reps to check request status without context-switching into the WFM app. Skip it if you haven't got WEM set up, or if your approval flow needs shift swap and shift bid decisions too — those still have to be actioned in the workforce management app.
Configuration decisions
- Whether Service Agent is in scope at all, and for which roles — this rides on your existing Service Agent rollout, not a separate WEM switch.
- Which users get the reviewer privilege for time-off decisions. The decision tool enforces it, so a supervisor without it can list and read but not approve.
- How this sits alongside your existing WEM approval process — decide whether the conversational path replaces or just supplements the app-based one.
Gotchas
- Already-decided requests aren't overwritten. If a request has a decision on it, the tool leaves it alone rather than flipping it — so a "did my approval go through" retry won't silently reverse anything.
- The role scoping is inherited, not configured here. If a supervisor can't see a request they expect, the fix is in their planning-group and security-role setup, not in the tool.
- It's an overview at this stage — the individual tool reference pages live under the developer MCP-tools reference, and the catalogue is expanding, so don't assume this is the full surface long-term.
Consultant notes
- Set expectations in scoping: this covers requests (time-off, shift swap, shift bid), not full schedule editing. Clients hear "manage workforce through Copilot" and assume shift building — it isn't that.
- The time-off-only decision limit is the thing that surprises people in UAT. Supervisors will try to approve a shift swap in chat and get nowhere; flag it early so it's not logged as a defect.
- Because access is role-scoped through existing security, a botched planning-group or reviewer-privilege setup shows up as "the agent can't find my requests" rather than a permission error. Check the security model first when triaging.
- It leans on Service Agent being live and healthy. If you're pitching this, sequence it after the Service Agent rollout — it's an add-on to that, not a standalone WEM feature.
Worth revisiting after the next release wave — the WEM tool catalogue is still growing and shift swap/bid decisions may become actionable.