Dynamics 365 Contact Center - Simply Explained
Key Takeaways
- Dynamics 365 Contact Center is Microsoft's cloud service designed to manage live customer conversations across voice and digital channels from a single unified workspace.
- A contact center focuses on managing real-time interactions, whereas a traditional CRM acts as the long-term customer filing cabinet storing historical data and customer records.
- Organizations do not need to replace their existing CRM to use Dynamics 365 Contact Center; they can connect legacy systems or third-party platforms like Salesforce via connectors and Power Automate.
- Unified routing functions like a digital reception desk, directing incoming customer queries from any channel to the most appropriate agent based on skills, availability, and workload.
- AI agents and conversational IVR systems can handle straightforward self-service requests like order tracking, but they must seamlessly transfer context to human agents when complex issues arise.
- Agent workspaces integrate live transcription, sentiment analysis, conversation summaries, and Microsoft Teams collaboration tools to reduce screen switching and resolve issues faster.
Imagine contacting a company about a missing order through web chat. The automated assistant cannot solve the problem, so you call instead. The phone agent asks for your order number, your address, and the entire story again. Then you are transferred and explain everything for a third time. That is not really a customer problem—it is a systems problem. In this episode of Microsoft Knowledge Nuggets on M365 FM, we explain Dynamics 365 Contact Center in plain English and look at how Microsoft brings voice, chat, messaging, routing, customer context, Copilot, AI agents, supervisors, and existing CRM systems together into one connected contact center experience.
WHAT DYNAMICS 365 CONTACT CENTER ACTUALLY IS
Dynamics 365 Contact Center is Microsoft's cloud service for managing live customer conversations across voice and digital channels from a connected workspace. A traditional contact center might immediately make you think about telephones, queues, and people wearing headsets. Modern customer service involves considerably more. Customers call, start web chats, send text messages, email companies, use mobile applications, and communicate through supported social messaging channels. Dynamics 365 Contact Center brings those different doors into a common service environment so requests can reach the appropriate people without every channel becoming its own disconnected island. ㅤ
A CONTACT CENTER IS MORE THAN A PHONE SYSTEM
A phone system primarily manages calls. A modern contact center needs to manage customer conversations. One customer may call about an invoice. Another starts a web chat because a delivery is late. Somebody else sends an email because they cannot access their account. The contact center receives those interactions, determines where they should go, and provides agents with the tools and information needed to respond. Dynamics 365 Contact Center moves this process into Microsoft's cloud environment instead of requiring every interaction to operate through separate systems.
CONTACT CENTER IS NOT THE SAME THING AS CRM
Dynamics 365 Contact Center should not be confused with a traditional Customer Relationship Management system. A CRM maintains the broader customer relationship: who the customer is, what they purchased, previous activities, opportunities, cases, service history, and other business information. The contact center focuses on the live interaction. Think of the CRM as the customer filing cabinet containing the long-term customer story. Dynamics 365 Contact Center is the service desk in front of that filing cabinet where calls and messages arrive and employees deal with customer requests as they happen.
YOU DO NOT NECESSARILY NEED TO REPLACE YOUR EXISTING CRM
One important point in the episode is that an organization does not necessarily have to replace its existing customer system to use Dynamics 365 Contact Center. Organizations already using Dynamics 365 Customer Service can connect contact center interactions with cases, customer records, and knowledge information. The transcript also discusses Microsoft's Salesforce connector and the possibility of connecting other systems using technologies such as Power Automate. The objective is to let organizations maintain relevant customer information in their existing business environment while providing agents with a connected Microsoft contact center experience.
THE PEOPLE INSIDE A CONTACT CENTER
Several roles participate in the contact center process. The customer wants an answer without repeatedly explaining the problem. The service agent handles calls, chats, emails, and messages. AI agents may handle straightforward questions or collect information before human involvement becomes necessary. Behind those interactions are supervisors responsible for monitoring queues, reviewing service activity, and helping teams improve performance. Dynamics 365 Contact Center connects these roles around the customer conversation.
THE PROBLEM WITH SEPARATE CHANNELS
The traditional approach often creates a different system for every communication channel. Phone agents work in one application. Chat agents use another. Email arrives in a shared mailbox. Each application provides a different view of the customer, and employees spend their day switching between systems. This fragmentation becomes visible to customers when they move between channels. Dynamics 365 Contact Center attempts to treat a phone call, web chat, or other interaction as part of a broader customer story rather than as unrelated events.
FOLLOWING ONE CUSTOMER FROM SELF-SERVICE TO HUMAN HELP
The episode follows a customer named Maya who ordered a coffee machine. The expected delivery date passes, but nothing arrives. Maya opens the company's website and asks through chat: Where is my order? Initially, this may not require a human employee. An AI agent can ask for the order number, check delivery information, and potentially answer straightforward questions. If the carrier simply reports a one-day delay, Maya can receive an immediate answer without waiting for an available service agent.
WHERE AI SELF-SERVICE WORKS
AI self-service can work particularly well when requests are common, clearly defined, and connected to information the system can reliably access. Checking order status, finding store hours, changing certain information, or explaining a standard return policy are examples discussed in the episode. The objective is not to prevent customers from reaching humans. It is to handle straightforward requests without forcing every customer to wait for an employee.
WHEN THE CUSTOMER NEEDS A HUMAN
Maya's situation becomes more complicated when the delivery system says the coffee machine was delivered even though it is not at her door. That requires investigation and judgment. Before handing the conversation to a person, however, the AI agent can already collect useful information: the order number, address, delivery record, and the fact that Maya is reporting a missing delivery. When Maya requests human assistance, that information can move with the conversation. She should not need to begin again with: “I already explained all of this.”
AI-ASSISTED VOICE AND IVR
The same principle can apply when Maya calls instead of using web chat. Traditional Interactive Voice Response systems—IVR—are often associated with menus telling callers to press one number for one department and another number for something else. The transcript describes a more conversational approach where the customer can explain what they need using normal language. Maya could say that her order is marked as delivered but has not arrived. The voice experience can gather information and determine the reason for the call before transferring her to the appropriate human employee.
SELF-SERVICE SHOULD NOT BECOME A WALL
An automated voice or chat experience should not become a barrier preventing customers from reaching a human. If the customer has a problem requiring judgment, authorization, empathy, or investigation, there needs to be a clear route to an appropriate employee. More importantly, the context already collected should survive that handoff. Good self-service removes simple repetitive work. It does not force customers into endless automation when the automation cannot solve their problem.
OMNICHANNEL CUSTOMER COMMUNICATION
Customers may contact an organization through email, web chat, SMS, mobile experiences, voice, or supported social messaging channels. From the customer's perspective, these are simply different doors into the same company. Someone might start through web chat during lunch and continue the conversation using another channel later. A connected contact center needs to preserve enough context for the organization to understand that those interactions may relate to the same underlying customer issue.
PROACTIVE CUSTOMER ENGAGEMENT
Sometimes the company can communicate before the customer needs to ask for help. If another business system identifies a delivery failure, the organization could proactively notify the customer, explain the situation, provide an updated delivery date, or offer another appropriate action. Done well, proactive engagement prevents customers from having to chase the company for information it already possesses. Done badly, it becomes another unwanted message. The process therefore depends on good customer information, appropriate communication rules, and a legitimate reason for contacting the customer.
UNIFIED ROUTING: THE DIGITAL RECEPTION DESK
Once a customer needs human assistance, the contact center needs to determine where that conversation should go. Think of unified routing as the reception desk inside a large building. A visitor explains why they are there. Reception determines which department is appropriate, checks where help is available, and directs the visitor accordingly. A contact center performs a similar function for customer interactions. A missing-delivery call should not automatically reach somebody who only handles billing, while a password-reset conversation should not unnecessarily sit behind unrelated product-return requests. ㅤ
WHAT IS A QUEUE?
A queue is essentially a waiting area for customer work. An organization might have queues for billing, technical support, returns, sales, deliveries, or other service functions. When an interaction arrives, Dynamics 365 Contact Center can place it into the appropriate queue and attempt to find an agent capable of handling that type of request. This applies across different communication channels rather than requiring completely independent routing systems for voice, chat, and messaging.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
🚀 Want to be part of m365.fm?
Then stop just listening… and start showing up.
👉 Connect with me on LinkedIn and let’s make something happen:
- 🎙️ Be a podcast guest and share your story
- 🎧 Host your own episode (yes, seriously)
- 💡 Pitch topics the community actually wants to hear
- 🌍 Build your personal brand in the Microsoft 365 space
This isn’t just a podcast — it’s a platform for people who take action.
🔥 Most people wait. The best ones don’t.
👉 Connect with me on LinkedIn and send me a message:
"I want in"
Let’s build something awesome 👊
Frequently Asked Questions
What is Dynamics 365 Contact Center?
Dynamics 365 Contact Center is Microsoft's cloud-based solution for managing live customer conversations across voice and digital channels—such as web chat, email, SMS, and social messaging—within a single connected workspace.
Do I need to replace my current CRM to use Dynamics 365 Contact Center?
No, organizations do not need to replace their existing CRM. You can connect Dynamics 365 Contact Center to other customer platforms using available integrations like the Salesforce connector or Power Automate.
How does unified routing work in Dynamics 365 Contact Center?
Unified routing acts like a digital reception desk, evaluating incoming customer requests from any communication channel and automatically placing them into the correct queue while matching them with the best available agent based on specific skills.
Can AI agents handle customer service requests before a human is involved?
Yes, AI agents can efficiently handle routine requests like checking order status or reading return policies, collecting necessary customer details, and handing over the conversation with full context if human intervention is required.
00:00:00,000 --> 00:00:02,120
Imagine you contact a company about a missing order
2
00:00:02,120 --> 00:00:03,120
through webchat.
3
00:00:03,120 --> 00:00:05,120
The chat agent can't fix it, so you call.
4
00:00:05,120 --> 00:00:07,240
The person on the phone asks for your order number,
5
00:00:07,240 --> 00:00:09,040
your address, and the whole story again.
6
00:00:09,040 --> 00:00:11,320
Then they transfer you, and you repeat everything
7
00:00:11,320 --> 00:00:12,240
a third time.
8
00:00:12,240 --> 00:00:13,520
That isn't a customer problem.
9
00:00:13,520 --> 00:00:14,640
It's a systems problem.
10
00:00:14,640 --> 00:00:16,800
Welcome to another Microsoft Knowledge Nuggets episode
11
00:00:16,800 --> 00:00:18,200
on M365.
12
00:00:18,200 --> 00:00:20,520
FM, I'm Mirko Peters, and we're looking
13
00:00:20,520 --> 00:00:23,480
at Dynamics 365 Contact Center in plain English.
14
00:00:23,480 --> 00:00:26,240
By the end, you'll understand how it pulls calls, messages,
15
00:00:26,240 --> 00:00:29,160
customer context, and agent help into one connected place.
16
00:00:29,160 --> 00:00:31,600
Think of a busy office building where customers arrive
17
00:00:31,600 --> 00:00:34,120
through the front desk, the phone room, and the message desk.
18
00:00:34,120 --> 00:00:36,000
Staff can still find the same customer file.
19
00:00:36,000 --> 00:00:37,560
That's the idea.
20
00:00:37,560 --> 00:00:40,520
What Dynamics 365 Contact Center actually is.
21
00:00:40,520 --> 00:00:43,560
So what exactly is Dynamics 365 Contact Center?
22
00:00:43,560 --> 00:00:45,800
It's Microsoft's cloud service for handling customer
23
00:00:45,800 --> 00:00:48,480
conversations across phone calls and digital channels
24
00:00:48,480 --> 00:00:49,480
from one workspace.
25
00:00:49,480 --> 00:00:51,360
That sounds like a lot of product language.
26
00:00:51,360 --> 00:00:52,280
Let's break it down.
27
00:00:52,280 --> 00:00:53,960
A Contact Center is the part of a business
28
00:00:53,960 --> 00:00:55,640
that deals with live customer contact.
29
00:00:55,640 --> 00:00:57,240
Imagine a customer calls about a bill.
30
00:00:57,240 --> 00:00:59,360
Another starts a web chat about a delivery.
31
00:00:59,360 --> 00:01:01,560
A third email is because they can't sign in.
32
00:01:01,560 --> 00:01:04,120
The Contact Center receives those requests, sends them
33
00:01:04,120 --> 00:01:06,560
to the right person, and helps that person respond.
34
00:01:06,560 --> 00:01:09,680
Dynamics 365 Contact Center puts that work in the cloud.
35
00:01:09,680 --> 00:01:11,840
The company doesn't need a separate old-style phone system
36
00:01:11,840 --> 00:01:13,760
in a backroom just to take customer calls,
37
00:01:13,760 --> 00:01:15,360
but it's much bigger than a phone system.
38
00:01:15,360 --> 00:01:16,720
A phone system handles calls.
39
00:01:16,720 --> 00:01:19,200
This one handles calls and also supports digital conversations
40
00:01:19,200 --> 00:01:21,800
like web chat, SMS, email, mobile experiences,
41
00:01:21,800 --> 00:01:23,040
and social messaging.
42
00:01:23,040 --> 00:01:26,160
The exact channels the company uses depend on its setup.
43
00:01:26,160 --> 00:01:27,160
The point stays the same.
44
00:01:27,160 --> 00:01:29,320
Customer requests arrive through different doors
45
00:01:29,320 --> 00:01:30,840
and reach the people who can help.
46
00:01:30,840 --> 00:01:32,880
Now most people hear Dynamics 365
47
00:01:32,880 --> 00:01:35,760
and assume this must be another customer relationship system.
48
00:01:35,760 --> 00:01:36,560
It isn't.
49
00:01:36,560 --> 00:01:38,960
A customer relationship system, often called a CRM,
50
00:01:38,960 --> 00:01:40,600
holds the wider customer record.
51
00:01:40,600 --> 00:01:42,800
That includes who the customer is, what they bought,
52
00:01:42,800 --> 00:01:44,760
open cases, past service requests,
53
00:01:44,760 --> 00:01:46,640
and notes from the business relationship.
54
00:01:46,640 --> 00:01:50,400
Dynamics 365 Contact Center focuses on the live conversation.
55
00:01:50,400 --> 00:01:52,920
Think of the CRM as the customer filing cabinet.
56
00:01:52,920 --> 00:01:55,000
It stores the customer story over time.
57
00:01:55,000 --> 00:01:56,400
The Contact Center is the service desk
58
00:01:56,400 --> 00:01:58,480
in front of that filing cabinet where calls and messages
59
00:01:58,480 --> 00:02:00,880
arrive and people work through issues as they happen.
60
00:02:00,880 --> 00:02:02,720
Those two things can work closely together.
61
00:02:02,720 --> 00:02:05,320
If a company uses Dynamics 365 Customer Service,
62
00:02:05,320 --> 00:02:07,400
the Contact Center can work alongside its cases,
63
00:02:07,400 --> 00:02:09,400
customer records, and knowledge articles.
64
00:02:09,400 --> 00:02:10,960
An agent can handle a conversation
65
00:02:10,960 --> 00:02:12,480
while looking at the customer information
66
00:02:12,480 --> 00:02:13,960
needed to solve the problem.
67
00:02:13,960 --> 00:02:16,400
But here's the thing, oh, a company doesn't need to replace.
68
00:02:16,400 --> 00:02:20,160
It's existing CRM just to use Dynamics 365 Contact Center.
69
00:02:20,160 --> 00:02:21,680
That's a big part of the product.
70
00:02:21,680 --> 00:02:23,680
A business might already use another customer system
71
00:02:23,680 --> 00:02:26,200
and still want Microsoft for its Contact Center tools.
72
00:02:26,200 --> 00:02:28,520
Microsoft provides a Salesforce connector.
73
00:02:28,520 --> 00:02:31,200
Other connections can use tools like Power Automate.
74
00:02:31,200 --> 00:02:32,240
The goal is simple.
75
00:02:32,240 --> 00:02:34,880
Keep the customer data where the business already keeps it
76
00:02:34,880 --> 00:02:36,160
while giving agents a better place
77
00:02:36,160 --> 00:02:37,520
to manage customer contact.
78
00:02:37,520 --> 00:02:39,360
Now, a Contact Center involves several people.
79
00:02:39,360 --> 00:02:40,720
First, you have the customer.
80
00:02:40,720 --> 00:02:43,040
They want an answer without being passed around.
81
00:02:43,040 --> 00:02:44,680
Then you have the service agent, oh,
82
00:02:44,680 --> 00:02:48,080
the person answering a call, chat, email, or message.
83
00:02:48,080 --> 00:02:50,800
You may also have an AI agent handling simple questions
84
00:02:50,800 --> 00:02:52,760
before a human joins the conversation.
85
00:02:52,760 --> 00:02:54,880
And behind the scenes, supervisors watch cues,
86
00:02:54,880 --> 00:02:56,600
review service activity, and help teams
87
00:02:56,600 --> 00:02:58,000
improve how they respond.
88
00:02:58,000 --> 00:03:01,520
All of those jobs connect inside Dynamics 365 Contact Center.
89
00:03:01,520 --> 00:03:03,320
The old approach often meant separate tools
90
00:03:03,320 --> 00:03:04,360
for separate channels.
91
00:03:04,360 --> 00:03:06,080
A phone agent lived in one system.
92
00:03:06,080 --> 00:03:09,440
A chat agent used another, email sat in an inbox somewhere else.
93
00:03:09,440 --> 00:03:11,640
Every tool carried its own view of the customer
94
00:03:11,640 --> 00:03:14,000
and staff switched screens all day.
95
00:03:14,000 --> 00:03:16,760
Dynamics 365 Contact Center brings those conversations
96
00:03:16,760 --> 00:03:18,880
into one workspace with shared context
97
00:03:18,880 --> 00:03:20,400
around the customer interaction.
98
00:03:20,400 --> 00:03:22,480
That doesn't magically fix a bad service process.
99
00:03:22,480 --> 00:03:24,640
A confused policy is still a confused policy.
100
00:03:24,640 --> 00:03:27,080
Poor customer information is still poor customer information.
101
00:03:27,080 --> 00:03:29,440
What it can do is remove the extra doors
102
00:03:29,440 --> 00:03:32,160
between a customer request and the person trying to solve it.
103
00:03:32,160 --> 00:03:34,240
So instead of treating a phone call and a web chat
104
00:03:34,240 --> 00:03:37,080
like unrelated events, the Contact Center can treat them
105
00:03:37,080 --> 00:03:39,000
as parts of the same customer story.
106
00:03:39,000 --> 00:03:40,800
Let's follow one of those customer requests
107
00:03:40,800 --> 00:03:43,320
from the first message through to human help.
108
00:03:43,320 --> 00:03:48,360
The customer journey from first question to human help.
109
00:03:48,360 --> 00:03:51,240
So imagine Maya just ordered a coffee machine online.
110
00:03:51,240 --> 00:03:54,280
And when the delivery date comes and goes with nothing showing up,
111
00:03:54,280 --> 00:03:57,760
she opens the company website and types into the chat box.
112
00:03:57,760 --> 00:04:00,280
Oh, where is my order?
113
00:04:00,280 --> 00:04:03,320
Oh, at first, Maya does not need a real personal.
114
00:04:03,320 --> 00:04:05,400
An AI agent can ask for her order number,
115
00:04:05,400 --> 00:04:08,120
check the delivery status and answer simple questions.
116
00:04:08,120 --> 00:04:10,320
If the carrier delayed the package by one day,
117
00:04:10,320 --> 00:04:12,920
she gets an instant answer without waiting in a queue.
118
00:04:12,920 --> 00:04:16,120
This kind of self-service works best for common clear requests
119
00:04:16,120 --> 00:04:18,880
like checking in order status, changing an address,
120
00:04:18,880 --> 00:04:22,200
finding store hours or reading a return policy.
121
00:04:22,200 --> 00:04:23,960
But Maya out-to-mar situation is different
122
00:04:23,960 --> 00:04:26,560
because the order page says the machine was delivered.
123
00:04:26,560 --> 00:04:28,840
Yet, it outens not at her door.
124
00:04:28,840 --> 00:04:31,080
That needs a human being who can look into the details,
125
00:04:31,080 --> 00:04:33,560
investigate the delivery and decide what happens next.
126
00:04:33,560 --> 00:04:35,200
Before Maya ever gets to a human,
127
00:04:35,200 --> 00:04:37,400
the AI agent can collect useful information
128
00:04:37,400 --> 00:04:39,240
like her order number, address,
129
00:04:39,240 --> 00:04:41,640
and the delivery record showing the package arrived.
130
00:04:41,640 --> 00:04:44,880
It also identifies the issue as a missing delivery.
131
00:04:44,880 --> 00:04:46,640
When Maya asks to speak with someone,
132
00:04:46,640 --> 00:04:49,000
the agent does notmit start over because the person
133
00:04:49,000 --> 00:04:51,200
who picks up can see everything.
134
00:04:51,200 --> 00:04:53,200
What Maya typed, what the AI agent found
135
00:04:53,200 --> 00:04:54,640
and why this got handed off.
136
00:04:54,640 --> 00:04:57,960
Maya never has to say, "How I already explained all of this."
137
00:04:57,960 --> 00:05:00,560
"Ail, that small detail makes the whole experience
138
00:05:00,560 --> 00:05:02,120
feel completely different."
139
00:05:02,120 --> 00:05:03,560
Voice calls work the same way.
140
00:05:03,560 --> 00:05:05,960
Picture Maya calling support instead of using chat.
141
00:05:05,960 --> 00:05:08,400
Rather than pressing one for this and two for that
142
00:05:08,400 --> 00:05:09,800
through a long recorded menu,
143
00:05:09,800 --> 00:05:12,880
a conversational voice agent can ask her what she needs
144
00:05:12,880 --> 00:05:13,920
in normal words.
145
00:05:13,920 --> 00:05:16,360
She might say, "Omi order says delivered,
146
00:05:16,360 --> 00:05:17,760
but I don't know what to have it."
147
00:05:17,760 --> 00:05:20,280
A.O, the voice agent can ask for the order number,
148
00:05:20,280 --> 00:05:21,600
confirm a few details,
149
00:05:21,600 --> 00:05:23,000
and gather the reason for the call
150
00:05:23,000 --> 00:05:24,840
before a human agent takes over.
151
00:05:24,840 --> 00:05:26,600
This type of phone-self service is called
152
00:05:26,600 --> 00:05:29,760
an interactive voice response system or IVR.
153
00:05:29,760 --> 00:05:31,000
That name sounds technical,
154
00:05:31,000 --> 00:05:33,680
but it simply means the system that talks to callers
155
00:05:33,680 --> 00:05:34,880
before they reach a person.
156
00:05:34,880 --> 00:05:36,840
In Dynamics 365 Contact Center,
157
00:05:36,840 --> 00:05:39,160
that first conversation can use AI to understand
158
00:05:39,160 --> 00:05:41,080
what the customer means rather than relying
159
00:05:41,080 --> 00:05:43,400
only on a rigid chain of button choices.
160
00:05:43,400 --> 00:05:46,320
Still, a voice agent should never become a wall
161
00:05:46,320 --> 00:05:48,960
between the customer and real help.
162
00:05:48,960 --> 00:05:50,440
If Maya needs a person,
163
00:05:50,440 --> 00:05:52,440
the handoff needs to happen cleanly.
164
00:05:52,440 --> 00:05:55,480
The human agent should receive the conversation details,
165
00:05:55,480 --> 00:05:57,240
not make Maya start again.
166
00:05:57,240 --> 00:06:00,080
A good Contact Center uses self-service to remove easy work
167
00:06:00,080 --> 00:06:01,800
while keeping a clear path to a person
168
00:06:01,800 --> 00:06:03,200
for problems that need judgment.
169
00:06:03,200 --> 00:06:05,080
Customers reach out through many channels,
170
00:06:05,080 --> 00:06:07,120
O, email, text, mobile app,
171
00:06:07,120 --> 00:06:08,640
or social messaging platforms,
172
00:06:08,640 --> 00:06:11,440
the business has connected to its Contact Center.
173
00:06:11,440 --> 00:06:13,400
From the customer, O, TMS view,
174
00:06:13,400 --> 00:06:15,600
the channel is just the door they chose that day.
175
00:06:15,600 --> 00:06:17,880
Maya might start with web chat during lunch,
176
00:06:17,880 --> 00:06:20,040
then send a message later because she outtams away
177
00:06:20,040 --> 00:06:21,000
from her laptop.
178
00:06:21,000 --> 00:06:22,440
The business needs to recognize
179
00:06:22,440 --> 00:06:25,080
that those contacts can relate to the same missing order
180
00:06:25,080 --> 00:06:27,480
and that history should travel with the request.
181
00:06:27,480 --> 00:06:29,520
When a conversation moves from an AI agent
182
00:06:29,520 --> 00:06:31,960
to a service agent or from one person to another,
183
00:06:31,960 --> 00:06:34,640
the previous messages and gathered details can come along.
184
00:06:34,640 --> 00:06:36,560
An agent can see the path that brought Maya there
185
00:06:36,560 --> 00:06:38,280
instead of guessing from a short note like,
186
00:06:38,280 --> 00:06:40,120
"O customer has delivery issue."
187
00:06:40,120 --> 00:06:41,640
A.O. sometimes the company does no terms
188
00:06:41,640 --> 00:06:43,480
wait for Maya to reach out.
189
00:06:43,480 --> 00:06:45,160
If its system spot a delivery failure,
190
00:06:45,160 --> 00:06:46,440
it can send a message first.
191
00:06:46,440 --> 00:06:48,120
That message might explain the problem,
192
00:06:48,120 --> 00:06:49,440
give a new delivery date,
193
00:06:49,440 --> 00:06:51,800
or provide a link for the customer to choose another option,
194
00:06:51,800 --> 00:06:53,280
that's proactive engagement.
195
00:06:53,280 --> 00:06:55,960
Dunwell, it saves customers from chasing an answer.
196
00:06:55,960 --> 00:06:58,120
Dun badly, it becomes another unwanted message
197
00:06:58,120 --> 00:06:59,520
so it needs good customer data
198
00:06:59,520 --> 00:07:01,200
and a clear reason for reaching out.
199
00:07:01,200 --> 00:07:04,440
Either way, every customer request needs a destination
200
00:07:04,440 --> 00:07:06,880
and the system needs to decide who should receive it
201
00:07:06,880 --> 00:07:10,040
when they can take it and what information should go with it.
202
00:07:10,040 --> 00:07:12,000
Routing.
203
00:07:12,000 --> 00:07:13,680
The digital reception desk.
204
00:07:13,680 --> 00:07:15,120
Once Maya asks for a person,
205
00:07:15,120 --> 00:07:17,960
the system needs to decide where her request should go.
206
00:07:17,960 --> 00:07:20,680
Picture routing like the reception desk in a large company.
207
00:07:20,680 --> 00:07:22,160
Every visitor arrives with a reason
208
00:07:22,160 --> 00:07:23,760
and reception checks what they need,
209
00:07:23,760 --> 00:07:26,520
sees who is available and points them to the right department.
210
00:07:26,520 --> 00:07:29,240
A contact center does the same thing with customer requests.
211
00:07:29,240 --> 00:07:31,320
A phone call about a missing delivery should no-tempt
212
00:07:31,320 --> 00:07:33,320
land with someone who only handles billing
213
00:07:33,320 --> 00:07:35,320
and a chat about a password reset should now come
214
00:07:35,320 --> 00:07:38,040
at wait behind a queue of product return questions.
215
00:07:38,040 --> 00:07:40,120
The goal is to put each conversation in front of someone
216
00:07:40,120 --> 00:07:42,440
who has the right skills and enough room to take it on.
217
00:07:42,440 --> 00:07:44,760
Microsoft calls this unified routing,
218
00:07:44,760 --> 00:07:46,480
which just means the same routing idea works
219
00:07:46,480 --> 00:07:49,120
across different channels or whether it's a voice call,
220
00:07:49,120 --> 00:07:51,720
web chat, SMS, email or social message,
221
00:07:51,720 --> 00:07:55,120
they all follow rules that direct work to the right team.
222
00:07:55,120 --> 00:07:56,600
Without that shared approach,
223
00:07:56,600 --> 00:07:59,760
each channel can turn into its own little island.
224
00:07:59,760 --> 00:08:02,480
Phone calls follow one set of rules, chat follows another,
225
00:08:02,480 --> 00:08:04,640
and email lands in a shared mailbox,
226
00:08:04,640 --> 00:08:06,120
waiting for someone to notice it.
227
00:08:06,120 --> 00:08:08,360
Customers feel the result when they land in the wrong place
228
00:08:08,360 --> 00:08:10,040
or wait far longer than they should.
229
00:08:11,040 --> 00:08:13,320
With Dynamics 365 contact center,
230
00:08:13,320 --> 00:08:15,200
a company can create queueso, a queue,
231
00:08:15,200 --> 00:08:17,040
is simply a waiting area for work,
232
00:08:17,040 --> 00:08:19,360
like a billing queue, technical support queue,
233
00:08:19,360 --> 00:08:21,280
returns queue or sales queue.
234
00:08:21,280 --> 00:08:24,400
When my out-tems request comes in,
235
00:08:24,400 --> 00:08:26,920
the system places it in the queue that fits her issue
236
00:08:26,920 --> 00:08:29,880
and routing looks for an agent who can handle that type of work.
237
00:08:29,880 --> 00:08:33,440
But it does know to just pick the next name on a list,
238
00:08:33,440 --> 00:08:35,600
the system looks at whether an agent is available,
239
00:08:35,600 --> 00:08:38,040
what skills they have, how much work they already have,
240
00:08:38,040 --> 00:08:40,240
and what channel they're set up to handle.
241
00:08:40,240 --> 00:08:42,320
An agent already managing several chats
242
00:08:42,320 --> 00:08:43,640
might not have room for another one
243
00:08:43,640 --> 00:08:45,320
and someone trained on delivery problems
244
00:08:45,320 --> 00:08:46,960
might be a better fit than someone
245
00:08:46,960 --> 00:08:49,040
who mainly handles account changes.
246
00:08:49,040 --> 00:08:52,720
So routing is more than sending a message from point A to point B.
247
00:08:52,720 --> 00:08:54,720
Ito-Tumors deciding who can give the customer
248
00:08:54,720 --> 00:08:56,880
a useful answer with the least delay.
249
00:08:56,880 --> 00:08:59,360
Imagine two agents, one knows the delivery system very well,
250
00:08:59,360 --> 00:09:00,560
but is already on a call,
251
00:09:00,560 --> 00:09:02,440
and another is free, but only handles billing.
252
00:09:02,440 --> 00:09:04,680
The contact center can wait for the right skilled agent
253
00:09:04,680 --> 00:09:06,480
based on the rules the business has set
254
00:09:06,480 --> 00:09:08,880
instead of sending Maya to the first free person.
255
00:09:08,880 --> 00:09:10,080
Those rules matter.
256
00:09:10,080 --> 00:09:11,720
If a company sets them badly,
257
00:09:11,720 --> 00:09:13,920
customers can still end up waiting too long
258
00:09:13,920 --> 00:09:15,240
or reaching the wrong team.
259
00:09:15,240 --> 00:09:17,040
The software can follow the rules quickly,
260
00:09:17,040 --> 00:09:18,360
but people still need to decide
261
00:09:18,360 --> 00:09:20,360
what a sensible service process looks like.
262
00:09:20,360 --> 00:09:21,720
Sometimes the first agent learns
263
00:09:21,720 --> 00:09:23,680
that a conversation belongs elsewhere.
264
00:09:23,680 --> 00:09:26,200
Maybe Maya out may as, "smisting package"
265
00:09:26,200 --> 00:09:28,320
becomes a question about a payment reversal.
266
00:09:28,320 --> 00:09:30,760
The agent can transfer the conversation to another queue
267
00:09:30,760 --> 00:09:33,440
and the next person should receive the context already collected
268
00:09:33,440 --> 00:09:35,480
rather than treating it like a brand new request.
269
00:09:35,480 --> 00:09:37,120
There is also a consultation option
270
00:09:37,120 --> 00:09:38,840
where the agent can ask an expert for help
271
00:09:38,840 --> 00:09:41,640
while staying responsible for the customer conversation.
272
00:09:41,640 --> 00:09:43,560
Picture a support agent who needs a quick answer
273
00:09:43,560 --> 00:09:45,320
from someone in the delivery team.
274
00:09:45,320 --> 00:09:46,640
They can bring that person into the work
275
00:09:46,640 --> 00:09:48,840
without telling Maya to call back later and start over.
276
00:09:48,840 --> 00:09:51,360
The customer gets help from the person who knows the answer
277
00:09:51,360 --> 00:09:53,320
and the first agent stays present.
278
00:09:53,320 --> 00:09:55,520
That is often better than a call transfer
279
00:09:55,520 --> 00:09:57,760
where a customer suddenly hears a new voice
280
00:09:57,760 --> 00:10:00,400
and has no idea whether anyone understood the problem.
281
00:10:00,400 --> 00:10:03,440
Supervisors can also watch the queues as work arrives.
282
00:10:03,440 --> 00:10:05,000
If a particular queue fills up,
283
00:10:05,000 --> 00:10:06,880
they can see demand building and respond
284
00:10:06,880 --> 00:10:08,640
before customers wait too long.
285
00:10:08,640 --> 00:10:11,200
Good routing does now attempt guarantee a good answer
286
00:10:11,200 --> 00:10:13,400
but it removes a common source of frustration
287
00:10:13,400 --> 00:10:15,040
being moved from department to department
288
00:10:15,040 --> 00:10:17,640
because nobody can see where the request belongs.
289
00:10:17,640 --> 00:10:20,480
Getting Maya to the right person is only half the job though
290
00:10:20,480 --> 00:10:22,360
because that person still needs enough context
291
00:10:22,360 --> 00:10:25,000
to solve the problem without digging through separate tools.
292
00:10:25,000 --> 00:10:29,720
The agent workspace, one screen for the full conversation,
293
00:10:29,720 --> 00:10:33,320
Maya out TMS, request reaches you as an agent
294
00:10:33,320 --> 00:10:35,840
but you don't know, Tim, I just get a notification saying,
295
00:10:35,840 --> 00:10:37,240
"Oh, customer needs help.
296
00:10:37,240 --> 00:10:38,520
Oh, you get the full picture."
297
00:10:38,520 --> 00:10:40,320
With Dynamics 365 Contact Center,
298
00:10:40,320 --> 00:10:43,520
you have one workspace for both voice and digital conversations.
299
00:10:43,520 --> 00:10:46,760
Whether Maya calls or uses chat, the screen looks the same.
300
00:10:46,760 --> 00:10:48,840
That saves time and cuts down on things getting lost.
301
00:10:48,840 --> 00:10:51,280
You can see who the customer is, which channel they used
302
00:10:51,280 --> 00:10:53,960
and all the details linked to the current conversation.
303
00:10:53,960 --> 00:10:56,320
Depending on how the company connects its customer system,
304
00:10:56,320 --> 00:10:59,040
that same view can pull up past contacts, open cases,
305
00:10:59,040 --> 00:11:01,400
notes, account details and related service work.
306
00:11:01,400 --> 00:11:03,600
For Maya, that might show her order number,
307
00:11:03,600 --> 00:11:06,000
the earlier chat, delivery status
308
00:11:06,000 --> 00:11:07,480
and notes from her last contact.
309
00:11:07,480 --> 00:11:09,560
Instead of jumping between five different tabs,
310
00:11:09,560 --> 00:11:11,800
you focus on finding her missing machine.
311
00:11:11,800 --> 00:11:14,280
This shared view also matters when Maya calls back tomorrow
312
00:11:14,280 --> 00:11:17,520
because the replacement order still has no to Matt arrived.
313
00:11:17,520 --> 00:11:19,520
A new agent can see the previous conversation
314
00:11:19,520 --> 00:11:20,960
and what was already done.
315
00:11:20,960 --> 00:11:22,640
When she always Tim's already frustrated,
316
00:11:22,640 --> 00:11:25,160
nobody has to rely on Maya remembering every detail.
317
00:11:25,160 --> 00:11:26,880
Now, calls bring a different problem.
318
00:11:26,880 --> 00:11:28,600
People talk faster than they type,
319
00:11:28,600 --> 00:11:31,720
with live transcription, the spoken conversation turns into text.
320
00:11:31,720 --> 00:11:34,040
You can follow along, catch anything you missed
321
00:11:34,040 --> 00:11:35,200
and review it later.
322
00:11:35,200 --> 00:11:37,320
Translation also helps team support customers
323
00:11:37,320 --> 00:11:39,000
who speak different languages.
324
00:11:39,000 --> 00:11:42,360
If you don't, Tim, that speak Maya out,
325
00:11:42,360 --> 00:11:45,480
as language, the contact center can translate
326
00:11:45,480 --> 00:11:47,080
the conversation in real time.
327
00:11:47,080 --> 00:11:48,760
That does not admit replace good service
328
00:11:48,760 --> 00:11:51,360
or careful wording, especially with sensitive topics,
329
00:11:51,360 --> 00:11:53,000
but it gives you a way to help when language
330
00:11:53,000 --> 00:11:55,000
would block the conversation entirely.
331
00:11:55,000 --> 00:11:57,000
Long customer interactions get messy fast.
332
00:11:57,000 --> 00:11:58,560
A chat might have 20 messages.
333
00:11:58,560 --> 00:12:01,440
A call could involve a bot, one agent, a transfer
334
00:12:01,440 --> 00:12:02,400
and a specialist.
335
00:12:02,400 --> 00:12:04,000
By the time the next person joins,
336
00:12:04,000 --> 00:12:06,480
reading everything takes longer than solving the problem.
337
00:12:06,480 --> 00:12:09,320
That utems when conversation summaries come into play.
338
00:12:09,320 --> 00:12:10,760
Instead of reading the full transcript,
339
00:12:10,760 --> 00:12:12,280
the next person gets a short summary
340
00:12:12,280 --> 00:12:15,320
of what the customer needs, what utemails already happened
341
00:12:15,320 --> 00:12:16,800
and what still needs action.
342
00:12:16,800 --> 00:12:19,280
That helps during handoffs, when a supervisor joins
343
00:12:19,280 --> 00:12:21,760
or when the next shift takes over an open case,
344
00:12:21,760 --> 00:12:23,440
but you still need to verify the details.
345
00:12:23,440 --> 00:12:24,840
A summary is a starting point,
346
00:12:24,840 --> 00:12:26,960
not proof that every word is correct.
347
00:12:26,960 --> 00:12:28,920
The workspace can also show sentiment signals
348
00:12:28,920 --> 00:12:30,280
during the conversation.
349
00:12:30,280 --> 00:12:32,240
In plain English, the system flags language
350
00:12:32,240 --> 00:12:35,560
that suggests a customer is calm, unhappy or getting more upset.
351
00:12:35,560 --> 00:12:37,280
Suppose Maya starts polite, then types,
352
00:12:37,280 --> 00:12:39,440
"How, yautom, contacted you three times
353
00:12:39,440 --> 00:12:41,240
and nobody will help."
354
00:12:41,240 --> 00:12:44,520
Oh, that shift in tone shows up as a signal for you.
355
00:12:44,520 --> 00:12:46,760
Etautm is not a score to judge customers.
356
00:12:46,760 --> 00:12:48,040
Etautm is not mind-reading.
357
00:12:48,040 --> 00:12:49,360
People use words differently.
358
00:12:49,360 --> 00:12:51,320
A system can misunderstand tone,
359
00:12:51,320 --> 00:12:54,040
treat sentiment as a reminder to pay closer attention,
360
00:12:54,040 --> 00:12:55,880
not as a reason to assume anything.
361
00:12:55,880 --> 00:12:58,440
During the call with Maya, you might need an answer fast,
362
00:12:58,440 --> 00:13:02,040
I.U., the delivery policy, a script for confirming an address
363
00:13:02,040 --> 00:13:04,680
or a way to link the conversation to an existing case,
364
00:13:04,680 --> 00:13:08,200
add notes, or find a canned response.
365
00:13:08,200 --> 00:13:10,720
All those tools live inside the same work area.
366
00:13:10,720 --> 00:13:12,120
Knowledge search lets you browse
367
00:13:12,120 --> 00:13:14,520
approved help content while the customer waits.
368
00:13:14,520 --> 00:13:17,240
Scripts walk you through company defined steps
369
00:13:17,240 --> 00:13:20,080
and suggested replies can save typing for routine messages,
370
00:13:20,080 --> 00:13:22,280
but you should always read them before sending.
371
00:13:22,280 --> 00:13:24,800
A pre-written message that does now at MAT fit
372
00:13:24,800 --> 00:13:27,000
can sound worse than no message at all.
373
00:13:27,000 --> 00:13:28,800
Sometimes you need backup from a coworker
374
00:13:28,800 --> 00:13:32,040
who knows the product, process, or customer better.
375
00:13:32,040 --> 00:13:35,640
That U.T.M.A.S. when Microsoft Teams enters the picture.
376
00:13:35,640 --> 00:13:37,280
You can pull in an expert through Teams
377
00:13:37,280 --> 00:13:39,360
while keeping the customer engagement open.
378
00:13:39,360 --> 00:13:40,960
The expert helps answer the question
379
00:13:40,960 --> 00:13:43,160
without forcing Maya through another transfer.
380
00:13:43,160 --> 00:13:45,240
She gets a better answer and you stay in control
381
00:13:45,240 --> 00:13:47,320
of the conversation, so the workspace gives you
382
00:13:47,320 --> 00:13:49,200
the customer story, the live conversation,
383
00:13:49,200 --> 00:13:50,520
and all the help you need around it.
384
00:13:50,520 --> 00:13:52,120
You still make the service decisions,
385
00:13:52,120 --> 00:13:54,680
but Copilot can handle some of that repetitive admin work,
386
00:13:54,680 --> 00:13:55,760
Sterezone.
387
00:13:55,760 --> 00:13:58,120
Copilot and AI agents help before,
388
00:13:58,120 --> 00:14:00,040
during and after the conversation.
389
00:14:00,040 --> 00:14:02,280
Copilot and AI agents sound similar,
390
00:14:02,280 --> 00:14:03,760
people mix them up all the time,
391
00:14:03,760 --> 00:14:05,360
but they actually do different jobs.
392
00:14:05,360 --> 00:14:07,280
Copilot helps you while you're out working
393
00:14:07,280 --> 00:14:10,320
or finding information, suggesting replies,
394
00:14:10,320 --> 00:14:12,520
creating summaries and helping with notes.
395
00:14:12,520 --> 00:14:15,120
An AI agent on the other hand can handle a defined task
396
00:14:15,120 --> 00:14:16,240
on its own.
397
00:14:16,240 --> 00:14:17,960
That could be answering a routine question,
398
00:14:17,960 --> 00:14:19,800
collecting details, or creating a case
399
00:14:19,800 --> 00:14:21,200
after you confirm the action.
400
00:14:21,200 --> 00:14:23,880
Think of Copilot as help sitting right beside you.
401
00:14:23,880 --> 00:14:26,040
An AI agent takes care of a specific task
402
00:14:26,040 --> 00:14:28,200
before, during or after the conversation.
403
00:14:28,200 --> 00:14:31,080
Before you even join in, an AI agent can ask questions
404
00:14:31,080 --> 00:14:32,920
and narrow down what the customer needs.
405
00:14:32,920 --> 00:14:34,600
Microsoft has names for these old,
406
00:14:34,600 --> 00:14:37,160
the customer assist agent and the customer intent agent.
407
00:14:37,160 --> 00:14:39,240
The names are fancier than the actual job.
408
00:14:39,240 --> 00:14:42,640
The customer assist agent handles simple self-service requests
409
00:14:42,640 --> 00:14:44,360
and passes harder problems to you.
410
00:14:44,360 --> 00:14:46,560
The customer intent agent looks at customer conversations
411
00:14:46,560 --> 00:14:48,360
and figures out why people are reaching out.
412
00:14:48,360 --> 00:14:51,680
Imagine Maya writes, "I only coffee machine never arrived,
413
00:14:51,680 --> 00:14:53,560
but the tracking page says it did."
414
00:14:53,560 --> 00:14:56,480
Oh, the system recognizes this looks like a delivery problem.
415
00:14:56,480 --> 00:14:58,960
So it can ask clarifying questions about the order number
416
00:14:58,960 --> 00:15:00,920
or delivery address before you jump in.
417
00:15:00,920 --> 00:15:02,840
That gives you a much better starting point.
418
00:15:02,840 --> 00:15:04,840
During the conversation, Copilot helps you find
419
00:15:04,840 --> 00:15:06,600
approved knowledge, draft responses,
420
00:15:06,600 --> 00:15:08,960
and suggest questions to move the case forward.
421
00:15:08,960 --> 00:15:10,600
If you need to explain a return rule
422
00:15:10,600 --> 00:15:12,880
or figure out the next step for a missing delivery,
423
00:15:12,880 --> 00:15:15,000
you don't know what to have to remember everything.
424
00:15:15,000 --> 00:15:16,640
You can search the company knowledge base
425
00:15:16,640 --> 00:15:18,200
right there with the customer,
426
00:15:18,200 --> 00:15:20,320
but that does not mean Copilot should speak for you
427
00:15:20,320 --> 00:15:21,320
without review.
428
00:15:21,320 --> 00:15:23,000
A suggested reply is just a suggestion.
429
00:15:23,000 --> 00:15:25,040
You read it, you check if it fits the situation,
430
00:15:25,040 --> 00:15:27,760
you tweak it if needed, then you decide whether to send it.
431
00:15:27,760 --> 00:15:29,240
That human check really matters.
432
00:15:29,240 --> 00:15:30,760
A customer with a missing parcel does
433
00:15:30,760 --> 00:15:32,560
oh, and met to just need a polite, oh,
434
00:15:32,560 --> 00:15:33,960
who understand your concern.
435
00:15:33,960 --> 00:15:36,360
AO, they need someone to check the delivery record,
436
00:15:36,360 --> 00:15:38,880
decide on the next action and explain it clearly.
437
00:15:38,880 --> 00:15:40,800
Copilot can cut down the typing involved,
438
00:15:40,800 --> 00:15:43,480
but it can open to take responsibility for the decision.
439
00:15:43,480 --> 00:15:46,200
Once the conversation ends, the admin work kicks in.
440
00:15:46,200 --> 00:15:48,480
You have to write notes, record what happened,
441
00:15:48,480 --> 00:15:50,880
update the case, and make sure the next person
442
00:15:50,880 --> 00:15:51,800
can pick it up.
443
00:15:51,800 --> 00:15:54,160
Thato terms where Summary's save time.
444
00:15:54,160 --> 00:15:56,080
Copilot can draft a summary with the issue,
445
00:15:56,080 --> 00:15:58,000
actions discussed, and next steps.
446
00:15:58,000 --> 00:16:01,120
In some setups, AI agents can also prep case details
447
00:16:01,120 --> 00:16:02,360
from the conversation.
448
00:16:02,360 --> 00:16:04,600
That way you spend less time copying info from a chat
449
00:16:04,600 --> 00:16:07,160
or call into fields, but you always check the result
450
00:16:07,160 --> 00:16:09,240
before it becomes part of the customer record.
451
00:16:09,240 --> 00:16:11,280
The same pattern applies to knowledge articles.
452
00:16:11,280 --> 00:16:13,200
If my out-hymn is issue reveals a common problem
453
00:16:13,200 --> 00:16:16,040
with the delivery partner, an AI agent can suggest
454
00:16:16,040 --> 00:16:17,840
creating a help article and even draft one
455
00:16:17,840 --> 00:16:19,840
from the case notes, but you need to review it,
456
00:16:19,840 --> 00:16:22,000
a bad article spreads bad advice fast.
457
00:16:22,000 --> 00:16:24,520
Someone has to check the wording, confirm the steps,
458
00:16:24,520 --> 00:16:26,520
remove customer details, and approve it
459
00:16:26,520 --> 00:16:28,160
before other agents use it.
460
00:16:28,160 --> 00:16:30,920
AI also supports the people running the contact center.
461
00:16:30,920 --> 00:16:33,040
The quality assurance agent helps supervisors
462
00:16:33,040 --> 00:16:35,080
review conversations for service quality,
463
00:16:35,080 --> 00:16:37,040
policy checks, and coaching needs.
464
00:16:37,040 --> 00:16:39,440
Instead of manually going through every call,
465
00:16:39,440 --> 00:16:41,920
supervisors use AI to find the interactions
466
00:16:41,920 --> 00:16:43,000
that need attention.
467
00:16:43,000 --> 00:16:45,800
The service operations agent focuses on the back-end work
468
00:16:45,800 --> 00:16:49,080
AU the day-to-day tasks of keeping the contact center running.
469
00:16:49,080 --> 00:16:52,080
But neither tool replaces the supervisor AU,
470
00:16:52,080 --> 00:16:53,880
Tom posts as judgment.
471
00:16:53,880 --> 00:16:55,440
A metric can flag a problem, but it
472
00:16:55,440 --> 00:16:57,280
can't explain every situation.
473
00:16:57,280 --> 00:16:59,360
A short call might mean you solved something fast,
474
00:16:59,360 --> 00:17:01,280
or it might mean the customer gave up.
475
00:17:01,280 --> 00:17:02,520
People have to look at the context.
476
00:17:02,520 --> 00:17:04,760
So he outams the sensible way to look at AI
477
00:17:04,760 --> 00:17:06,840
in Dynamics 365 contact center.
478
00:17:06,840 --> 00:17:09,480
It can handle routine work, pull together information,
479
00:17:09,480 --> 00:17:10,920
and help you move faster.
480
00:17:10,920 --> 00:17:14,280
It can't outend fix unclear policies, missing customer data,
481
00:17:14,280 --> 00:17:16,040
or a service team that does not outempty
482
00:17:16,040 --> 00:17:18,120
have the authority to solve problems.
483
00:17:18,120 --> 00:17:20,320
And for any of this to work, the contact center
484
00:17:20,320 --> 00:17:22,200
needs to connect with the customer systems
485
00:17:22,200 --> 00:17:24,600
and communication tools the company already uses,
486
00:17:24,600 --> 00:17:28,520
or how it fits into Microsoft and existing customer systems.
487
00:17:28,520 --> 00:17:29,320
Here's the thing.
488
00:17:29,320 --> 00:17:32,480
Dynamics 365 contact center handles the conversation,
489
00:17:32,480 --> 00:17:35,480
but your customer record stays exactly where it already lives.
490
00:17:35,480 --> 00:17:38,560
If you're already on Dynamics 365 customer service,
491
00:17:38,560 --> 00:17:42,080
agents can pull up cases, customer details, and service history
492
00:17:42,080 --> 00:17:44,120
right beside the live conversation.
493
00:17:44,120 --> 00:17:45,840
Now, if your company runs Salesforce,
494
00:17:45,840 --> 00:17:48,880
Microsoft offers a connector to link those systems together.
495
00:17:48,880 --> 00:17:51,400
For other customer platforms, you can use Power Automate,
496
00:17:51,400 --> 00:17:53,560
but that means careful setup and testing.
497
00:17:53,560 --> 00:17:55,360
Think of Dataverse as the central filing cabinet
498
00:17:55,360 --> 00:17:56,880
where all the connected data lives.
499
00:17:56,880 --> 00:17:58,960
Behind the scenes, Dynamics-based setups
500
00:17:58,960 --> 00:18:00,320
use it to store everything.
501
00:18:00,320 --> 00:18:03,080
As an agent, you don't need to worry about the technical details.
502
00:18:03,080 --> 00:18:05,480
What matters is that the right customer information shows up
503
00:18:05,480 --> 00:18:06,920
when the conversation arrives.
504
00:18:06,920 --> 00:18:09,560
For voice calls, the platform taps into Teams phone
505
00:18:09,560 --> 00:18:11,440
or Azure communication services,
506
00:18:11,440 --> 00:18:13,080
because Teams is already there,
507
00:18:13,080 --> 00:18:15,560
an agent can instantly message an internal expert
508
00:18:15,560 --> 00:18:17,040
for help during a live contact.
509
00:18:17,040 --> 00:18:18,360
Access needs control too.
510
00:18:18,360 --> 00:18:20,160
That's where Entra ID steps in.
511
00:18:20,160 --> 00:18:22,120
It decides who can sign in and what they can open,
512
00:18:22,120 --> 00:18:24,160
so customer conversations and records
513
00:18:24,160 --> 00:18:27,040
aren't visible to everyone in the company, the lot.
514
00:18:27,040 --> 00:18:29,880
Who it fits and the first question to ask.
515
00:18:29,880 --> 00:18:31,080
So who is this for?
516
00:18:31,080 --> 00:18:33,960
It works for organizations that manage a steady flow of calls
517
00:18:33,960 --> 00:18:36,480
and digital messages, especially when agents need
518
00:18:36,480 --> 00:18:38,280
one place to manage it all.
519
00:18:38,280 --> 00:18:40,920
This also fits a company that already uses another CRM,
520
00:18:40,920 --> 00:18:43,200
but once Microsoft's contact center tools,
521
00:18:43,200 --> 00:18:46,080
if you already use Dynamics 365 customer service,
522
00:18:46,080 --> 00:18:48,600
compare this product with Dynamics 365 customer service
523
00:18:48,600 --> 00:18:50,120
premium before picking licenses,
524
00:18:50,120 --> 00:18:52,000
because premium bundles customer service work
525
00:18:52,000 --> 00:18:54,560
and contact center capabilities into one package.
526
00:18:54,560 --> 00:18:56,200
But let me ask you one question first.
527
00:18:56,200 --> 00:18:58,120
Where does your customer information live
528
00:18:58,120 --> 00:19:00,160
and can every agent see the right parts of it
529
00:19:00,160 --> 00:19:01,600
during a conversation?
530
00:19:01,600 --> 00:19:04,280
Because AI alone won't fix a disconnected setup.
531
00:19:04,280 --> 00:19:08,760
Conclusion, one connected front desk Dynamics 365,
532
00:19:08,760 --> 00:19:10,600
contact center brings customer messages,
533
00:19:10,600 --> 00:19:13,920
routing, agent context, and AI help all to one front desk.
534
00:19:13,920 --> 00:19:15,640
Your team stops hunting for information
535
00:19:15,640 --> 00:19:16,960
and just solves problems.
536
00:19:16,960 --> 00:19:18,960
The real power is everything working together
537
00:19:18,960 --> 00:19:20,480
without switching screens.
538
00:19:20,480 --> 00:19:23,360
Subscribe to Microsoft Knowledge Nuggets on M365,
539
00:19:23,360 --> 00:19:24,720
FM and share this with anyone
540
00:19:24,720 --> 00:19:27,320
starting their customer service journey.
