Meet Service Agent: Everything you need to know
It’s time to introduce you to another AI agent in the Dynamics 365 Customer Service family! After being available in public preview since March of this year, the Service Agent officially reached General Availability on June 30, making it ready for organizations to begin using in production! If you had a chance to read my recent article about the Sales Agent, then you will find some of this is going to feel familiar, because to me the Service Agent feels like Sales Agent’s big brother or sister! Instead of helping sellers stay on top of opportunities and customer relationships, Service Agent is focused on helping customer service reps in their day to day customer service activities. Just like Sales Agent, Service Agent is designed to work alongside your users rather than replace them. It brings together customer information, recent interactions, knowledge, and AI-powered assistance into a single conversational experience that helps CSRs quickly get the context they need. The result is less time searching for information and more time delivering great customer service. In this article, I’ll walk you through what Service Agent is, where your customer service representatives can access it, and some of its key capabilities that help streamline the customer service experience. I also will give you my 2 cents on where I feel the agent is lacking after I spent several hours testing its capabilities!
What is the Service Agent?
In my opinion the Service Agent is the next evolution of the AI capabilities that are built for Dynamics 365 Customer Service. The difference is that Service Agent doesn’t just summarize data and answers questions, it can also reason across BOTH Dynamics 365 data and your Microsoft 365 data (SharePoint, Outlook and Teams) through Work IQ! What that means is that instead of your CSRs switching between D365 Customer Service, Outlook and Microsoft Teams to try to piece together the full picture, Service Agent can pull all of that context into one conversation, while still respecting whatever security roles and permissions are already in place.
What can Service Agent do?
I want to start with the most important thing. If you use Copilot in D365 Customer Service today, you already know it’s mostly about answering questions and summarizing information, and it does that by pulling data from D365 Customer Service. Service Agent can do all of that too, but here’s the part that makes it different: it uses Work IQ to pull information from Microsoft 365 as well (SharePoint, Teams, Outlook). Not just D365 Customer Service. Here’s why that matters. the context needed to solve a customer’s issue is usually scattered across different places, knowledge articles, an email thread, maybe a Teams conversation with another rep. Today, piecing that together means a CSR has to go dig through each app individually. Service Agent skips that step and just pulls it all into one place for you. Think about how often there’s a customer email sitting in your inbox that you haven’t gotten to yet, or worse, missed entirely. Ask Service Agent to summarize the case, and it can include that email too. During one of my tries it even provided clickable links which allowed me to open the email right from the chat! Does that mean you never have to keep an eye on your inbox again? I don’t think so. From what I understand, Work IQ only gives the agent access to what the signed-in user has access to in M365, so it’s not going to surface an email that’s sitting in a coworker’s inbox.
Service Agent can also complete tasks right from the chat. Think of things like updating fields, adding notes, creating child cases, drafting (and sending) customer emails, recommending next best actions, reassigning cases, and more. Microsoft announced Service Agent is powered by 90+ Dynamics 365 Customer Service MCP tools, which means it can do A LOT! On top of that organizations can extend the agent with custom MCP tools as well. You can view the full list of D365 Customer Service MCP tools that are available in the Service Agent here.
CSRs can also upload files and images for Service Agent to interpret, generate images, pull on-demand charts from service data, and even have it create Word, Excel, or PowerPoint files for them! There are also interactive ‘apps-in-chat’ experiences available, meaning that views, forms, and cards can show up inline instead of everything being plain text. So instead of Service Agent just telling a rep about a list of cases, it can actually show them an interactive grid of cases right there in the chat. CSRs can also ask the agent to open an existing case, which will load a form in the chat from which the CSR can make updates to the case directly without having to navigate away from the chat!
Why this matters
At the end of the day, this is about making CSRs more productive and giving your customers a better experience because of it. Every minute a CSR spends hunting through emails and Teams chats is a minute the customer is left waiting, and that adds up fast when you’re measuring things like average handling time and CSAT. Service Agent saves time by surfacing the full picture up front, so CSRs walk into a case already knowing the context instead of piecing it together on the fly. The ability to take action right from the chat (updating a case, drafting email responses, creating child cases) means fewer clicks and less switching between apps, which means less times spent and faster resolution rates. For organizations already investing in D365 Customer Service and Microsoft 365 Copilot, this is the kind of upgrade that pays for itself in reduced handle time alone, before you even factor in happier employees and happier customers.
Where to access Service Agent
Before your reps can start using Service Agent, an admin has to enable this for your organization (I’ll write a follow-up article on how to do this, as I was having some issues when I did this myself and I noticed there was not a lot of documentation out there if you get stuck.) There are also some licensing restrictions for CSR’s that need access to the agent. They will need a Dynamics 365 Customer Service license (Enterprise or Premium) and a Microsoft 365 Copilot license to get the fully connected experience across Teams, Outlook, and Microsoft 365 Copilot chat.
Since the Service Agent is accessed through M365 Copilot as a declarative agent, CSR’s can access the Service Agent anywhere M365 Copilot is available. This is in Outlook, Microsoft Teams, M365 Copilot Chat and inside of D365 Customer Service (as long as you enable M365 Copilot in the model driven app.)
When the agent is accessed through the Copilot (or Customer) Service Workspace app, there are a few minor differences vs when you access it through outlook or M365 Copilot. According to the documentation, when you access the agent through CSW the Service Agent is automatically selected so CSRs don’t have to open the agent manually. If a case is open while chatting with the agent, it will understand the context which means the Agent has access to the case record that is open.
When a CSR navigates back to a case for this a conversation with Service Agent already exists, the agent automatically restores the chat.
Is the Service Agent ready for prime time?
As mentioned in the intro of this article, I spent several hours testing the agents to see how far I could push it, and I wanted to share my observations. My biggest one: the response time could use some improvement. When I asked the agent to ‘Show all interaction history’ for a case, it took the agent about 13 seconds (on average) to respond. That’s not a dealbreaker for most scenarios, but if you’re on the phone with a customer trying to get up to speed on their case 13 seconds is a long time. I also noticed the first answer I got back wasn’t quite the full picture, it only showed activities from the case’s timeline, and missed an internal Teams chat and a customer email sitting in my Outlook inbox that were both related to the case. When I specifically asked the agent to include M365 activities like Outlook emails and Teams chats, it found the Teams chat every time, but only caught the Outlook email 3 out of 4 times. I also tried asking it to remember to always include M365 activity going forward, and it let me know it couldn’t guarantee that preference would carry across future sessions, which tells me memory capabilities (something a few of the other agents already have) aren’t quite there yet. I’m hopeful that’s on the roadmap.
Between this and a few other smaller things I ran into, my take is that Service Agent isn’t quite ready to be your CSRs’ only tool yet, but it’s a genuinely solid start. In the meantime, I’d recommend keeping the existing Copilot experience in D365 Customer Service running alongside Service Agent rather than replacing one with the other. Given how fast AI tools are moving these days, I have a feeling it won’t take long for Service Agent to catch up.
Take a look at the video below to see the agent in action. I hope you enjoyed this article! Be sure to check in again soon for a new one, or subscribe to never miss another post!
