A customer sends an email, starts a chat, calls support, or contacts a company through another service channel. When an agent picks up that request, they need the complete customer story quickly. What did the customer already tell us? Which product do they own? Has somebody else worked on this problem? Is there an existing case? What was promised previously? Is there a service deadline approaching? Without a unified workspace, answering those questions can mean jumping between browser tabs, inboxes, CRM records, notes, knowledge bases, and communication applications. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Dynamics 365 Customer Service Workspace, now known as Copilot Service Workspace, in plain English. We explore sessions and tabs, cases and timelines, omnichannel customer service, the agent inbox, Smart Assist, knowledge management, agent scripts, macros, quick replies, Copilot, Microsoft Teams collaboration, Unified Routing, queues, presence, capacity, SLA management, escalation, self-service, dashboards, and customer service analytics. The central idea is straightforward: give customer service agents one organized workspace where the customer, the problem, the history, the knowledge, and the tools required to solve it remain connected.
WHAT IS DYNAMICS 365 CUSTOMER SERVICE WORKSPACE?
Dynamics 365 Customer Service Workspace was designed as a focused working environment for customer service agents. Microsoft now refers to this newer agent experience as Copilot Service Workspace, so organizations may encounter both names in documentation, videos, training materials, or existing environments. Think of it as a browser designed specifically around customer service. Instead of opening a completely separate browser window for every customer, case, knowledge article, product record, and conversation, the workspace organizes related information around the piece of customer work currently being handled. The objective is not simply to display CRM records. It is to help agents move between multiple customer issues without repeatedly losing and rebuilding context.
WHY CUSTOMER SERVICE AGENTS NEED A DIFFERENT WORKSPACE
Imagine an agent halfway through a customer call. A high-priority email arrives. Another customer replies to yesterday's chat. A different case is approaching its promised response deadline. This is normal customer service work. Agents frequently manage several customers, several communication channels, and substantial histories for each customer simultaneously. They need to understand what the customer purchased, what already happened, who previously worked on the issue, and whether somebody promised a response. When that information lives across multiple systems, the agent becomes an information detective. Customer Service Workspace attempts to remove some of that detective work.
THE PROBLEM WITH CONSTANT CONTEXT SWITCHING
Consider the traditional workflow. An agent searches an email inbox for an old customer message. They open the customer record in another browser tab. They find a case. Another application contains internal notes. A knowledge base contains troubleshooting instructions. Then another customer contacts them. The agent changes context. Ten minutes later, they return to the first customer and need to remember why several browser tabs are open. The applications may all work correctly individually. The problem is that the customer story is fragmented across them. That fragmentation becomes visible to customers when they hear: "Can you tell me that again?" or: "Let me find the previous update." Customer Service Workspace attempts to keep more of that story together.
FROM CUSTOMER SERVICE HUB TO COPILOT SERVICE WORKSPACE
Many Dynamics 365 users will be familiar with the older Customer Service Hub experience. Customer Service Hub supported core service activities such as working with cases, customer records, activities, knowledge articles, and dashboards. Customer Service Workspace introduced a different style of agent experience focused more heavily on handling several active pieces of work while preserving the context associated with each one. The supplied episode describes Microsoft subsequently naming this experience Copilot Service Workspace. The underlying concept remains an agent-focused workspace where customer service information and tools are organized around active work.
THE AGENT DESK, NOT THE ADMINISTRATION CONTROL ROOM
Copilot Service Workspace is primarily where agents perform their daily customer service work. It is not where every customer service rule is designed. Administrators configure areas such as channels, queues, routing rules, permissions, skills, capacity, and other service settings through the relevant administration experiences. The agent experiences the result of that configuration inside the workspace. Think of the distinction like this: The administration environment is the control room. Copilot Service Workspace is the service desk. Agents should be able to focus primarily on customers rather than the technical configuration behind how customer work reached them.
SESSIONS: ONE CUSTOMER ISSUE, ONE WORKING CONTEXT
One of the most important concepts inside the workspace is the session. Think of a session as a labeled desk drawer. One drawer contains everything associated with one customer's active issue. Another drawer contains another customer's conversation. Opening one drawer should not mix its contents with another. Inside Copilot Service Workspace, a session provides a boundary around a particular piece of customer work. That makes it easier for agents to manage several active issues without mixing their records, notes, and supporting information.
TABS: EVERYTHING RELATED TO THE CUSTOMER ISSUE
Inside each session are tabs. The first tab might contain the case. The agent clicks the customer and opens the customer record as another tab. They might then open the associated account. Another tab could contain the product. Another could contain a knowledge article. Another might contain an email. These are separate records, but they belong to the same customer story. Instead of scattering those records across unrelated browser windows, the workspace keeps them grouped inside the session. This gives agents the freedom to explore connected information without losing the original customer issue. ㅤ
A SIMPLE SESSION EXAMPLE
Imagine a customer contacts support because their coffee machine stopped working. The agent opens the case. That becomes the working session. The case contains the reported problem and current status. The agent clicks the customer's name. The customer record opens as another tab inside the same session. The agent reviews previous support interactions. Next, they open the product record to determine which coffee machine model the customer owns. Then they find an approved troubleshooting article. That article opens in another tab. The agent can move between the case, customer, product, and knowledge article while everything remains associated with the same customer issue.
MULTIPLE CUSTOMERS WITHOUT MIXING THEIR INFORMATION
Now imagine another customer contacts support. Their problem has nothing to do with the coffee machine case. Instead of adding more unrelated tabs to the existing workspace, the second customer receives a separate session. That session has its own tabs, records, and context. The first customer remains in one drawer. The second remains in another. This separation can reduce simple but potentially serious mistakes. When agents handle several cases simultaneously, it can be easy to type a note on the wrong record, lose track of which customer owns which information, or accidentally continue working from the wrong context. Sessions provide clearer boundaries between those customer stories.
SESSION AND TAB LIMITS
The supplied episode states that Copilot Service Workspace supports up to nine sessions at one time, with up to ten tabs within each session. The important point is not that agents should spend their day counting tabs. It is that a customer case rarely exists alone. A service issue can connect to contacts, accounts, products, activities, emails, knowledge articles, notes, and other business information. The workspace gives those connected records somewhere to remain together while the agent works.
SESSION RESTORE
A browser refresh during a complicated customer case can be disruptive. The supplied material describes a session restore feature in preview that administrators can enable. With session restore enabled, supported records and tabs can be restored following a browser refresh rather than forcing the agent to begin again from an empty home page. The episode notes that supported cases, accounts, related tabs, and the agent's previous focus can return after presence loads, while active conversations such as chats and calls can also return. This can help preserve context when a refresh occurs at exactly the wrong moment. Agents still need to save their work appropriately. A workspace can restore supported context, but it cannot protect information that was never saved.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
