Aug. 18, 2026
Dynamics 365 Knowledge Management - Simply Explained
Key Takeaways
- Dynamics 365 Knowledge Management transforms scattered support notes, emails, and spreadsheets into a single, trusted source of guidance for customer service teams.
- Mirko Peters explains how embedding knowledge directly within Dynamics 365 Customer Service allows agents to search for approved answers without leaving their active case workflow.
- A successful knowledge article should begin with a short, direct answer followed by clear, step-by-step instructions that reflect the exact terminology customers use.
- Establishing clear article ownership, review dates, and approval workflows prevents outdated information from misguiding support agents or customers.
- Dividing knowledge into internal-only procedures and customer-facing self-service articles ensures safe access control while maintaining consistent service across all channels.
Dynamics 365 Knowledge Management helps customer service teams create a single, trusted source of knowledge that agents can use while supporting customers. Instead of searching through old emails, shared folders, spreadsheets, or relying on individual experience, teams can create approved knowledge articles that provide consistent answers across customer service channels. In this episode of M365 FM, Mirko Peters explains how Dynamics 365 Knowledge Management works and why a structured knowledge base can improve both agent productivity and the customer experience.
ㅤ
WHY CUSTOMER SERVICE TEAMS NEED KNOWLEDGE MANAGEMENT
ㅤ
Customer service teams accumulate knowledge quickly, but that knowledge is often scattered across documents, inboxes, shared folders, and individual employees. This makes it difficult for agents to find reliable information when customers need an immediate answer. Dynamics 365 Knowledge Management creates a shared knowledge base where approved information can be stored, maintained, and accessed by the entire support organization.
A centralized knowledge base also helps organizations provide more consistent customer service. Whether customers contact a company through phone, email, chat, or self-service, agents can work from the same approved information instead of creating their own answers.
ㅤ
WHAT IS DYNAMICS 365 KNOWLEDGE MANAGEMENT?
ㅤ
Dynamics 365 Knowledge Management provides teams with a central place to create, organize, review, search, publish, and improve knowledge articles. These articles can contain answers to common customer questions, troubleshooting instructions, internal procedures, policies, links, screenshots, and step-by-step guidance.
Knowledge is integrated into the Dynamics 365 Customer Service environment, allowing agents to search for relevant information while working on customer cases. Instead of switching between multiple applications and repositories, agents can access approved guidance directly within their customer service workflow.
ㅤ
CREATING EFFECTIVE KNOWLEDGE ARTICLES
ㅤ
A useful knowledge article starts with a real customer or agent problem. Clear titles, relevant keywords, categories, and straightforward language make articles easier to discover. Articles should provide the main answer quickly and then explain the necessary steps in the order agents or customers need to follow them.
Organizations can also connect related articles and organize knowledge around subjects such as billing, account access, delivery, returns, or product support. Using terminology that customers actually use can significantly improve knowledge search and discovery.
ㅤ
KNOWLEDGE ARTICLE REVIEW AND APPROVAL
ㅤ
Creating an article is only the beginning. Knowledge should be reviewed by appropriate subject matter experts before it becomes trusted guidance. Approval processes help ensure that instructions follow company policies, security requirements, and operational procedures.
After approval, articles can be published for the appropriate audience. Some knowledge should remain available only to employees, while other articles can be made available through customer self-service experiences.
ㅤ
SEARCHING KNOWLEDGE INSIDE DYNAMICS 365
ㅤ
Agents can search the knowledge base while working with customer cases in Dynamics 365 Customer Service. Search can use article titles, content, categories, labels, and other information to identify relevant guidance.
Dynamics 365 can also suggest articles based on information contained within a case. These suggestions help narrow the search, while the agent still determines whether the article actually applies to the customer's situation.
ㅤ
INTERNAL KNOWLEDGE AND CUSTOMER SELF-SERVICE
ㅤ
Not every knowledge article should be public. Internal articles can contain procedures, escalation instructions, account checks, and information intended specifically for employees. Customer-facing articles can provide safe, simplified instructions that customers can follow themselves.
This allows organizations to use the same overall knowledge management approach for both assisted customer service and self-service while maintaining appropriate access to internal information.
ㅤ
KEEPING KNOWLEDGE ACCURATE AND CURRENT
ㅤ
Knowledge management requires continuous maintenance. Products change, policies are updated, processes evolve, and application interfaces can change. Without regular reviews, previously correct knowledge can eventually become outdated.
Assigning article ownership, defining review processes, managing permissions, and collecting feedback help keep the knowledge base reliable. Search misses and repeated support cases can also reveal where articles are missing, difficult to find, or need improvement.
ㅤ
HOW KNOWLEDGE MANAGEMENT IMPROVES CUSTOMER SERVICE
ㅤ
A well-managed Dynamics 365 knowledge base can reduce the time agents spend searching for information and decrease their dependence on experienced colleagues. New employees gain access to established organizational knowledge, while experienced agents spend less time repeatedly answering the same questions.
Customers benefit from faster and more consistent answers. Self-service knowledge can also help customers solve common problems before they need to contact the service team.
ㅤ
A PRACTICAL DYNAMICS 365 KNOWLEDGE MANAGEMENT EXAMPLE
ㅤ
The episode follows practical customer service scenarios including billing questions and password-reset problems. An agent can search for an approved article, follow a structured checklist, explain the correct next steps to the customer, and escalate the case when necessary.
Agent feedback can then improve the article for future cases. In this way, every support interaction can potentially identify missing information and contribute to a stronger organizational knowledge base.
ㅤ
THE KEY TAKEAWAY
ㅤ
Dynamics 365 Knowledge Management turns scattered support information into a structured and reusable source of trusted guidance. By combining knowledge articles, search, approval workflows, permissions, self-service, feedback, and ongoing review, organizations can make useful knowledge available exactly where customer service teams need it.
The goal isn't simply to create more documentation. It's to make accurate, current, and easy-to-find answers available to agents and customers when they need them.
Subscribe to M365 FM for more Microsoft Knowledge Nuggets and Simply Explained episodes covering Dynamics 365, Microsoft 365, Power Platform, Azure, Copilot, AI, security, governance, and the Microsoft ecosystem.
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 Knowledge Management?
It is a centralized feature within Dynamics 365 Customer Service that allows organizations to create, organize, review, and search approved help articles so support teams can deliver consistent answers.
How does Dynamics 365 Knowledge Management improve agent productivity?
It eliminates the need for agents to search through old emails, shared folders, or interrupt colleagues, giving them direct access to trusted answers right inside their active case workspace.
Why are article reviews and approvals important in Dynamics 365?
Reviews by subject matter experts ensure that instructions comply with company policies, security requirements, and operational procedures before they are published to agents or customers.
Can customers access the same knowledge base as support agents?
Yes, organizations can publish customer-facing articles for self-service portals while restricting internal procedures, account checks, and escalation steps to employees only.
1
00:00:00,000 --> 00:00:03,800
A customer asks a simple question, but the agent has to hunt through old emails, shared
2
00:00:03,800 --> 00:00:07,440
folders, and somebody's spreadsheet while the customer waits on the line.
3
00:00:07,440 --> 00:00:10,320
That's where Dynamics 365 Knowledge Management comes in.
4
00:00:10,320 --> 00:00:13,520
Think of it as the shared filing cabinet for your support team.
5
00:00:13,520 --> 00:00:16,880
Approved answers live in one place instead of inside people's heads.
6
00:00:16,880 --> 00:00:20,120
It's a central library where every article is reviewed and approved before it reaches the
7
00:00:20,120 --> 00:00:21,120
team.
8
00:00:21,120 --> 00:00:25,320
I'm Mirko Peters from M365FM, and this is a Microsoft Knowledge Nugget.
9
00:00:25,320 --> 00:00:30,280
You'll see how articles search, access, feedback, and daily support work fit together.
10
00:00:30,280 --> 00:00:33,000
First though, let me show you the raw problem this solves.
11
00:00:33,000 --> 00:00:35,480
It's bigger than you might think.
12
00:00:35,480 --> 00:00:38,520
Why teams need a shared knowledge base?
13
00:00:38,520 --> 00:00:40,920
Imagine a new support agent starts on Monday.
14
00:00:40,920 --> 00:00:44,760
By Tuesday, I'll just two days and how they're answering questions about returns, billing,
15
00:00:44,760 --> 00:00:48,920
account access, and product rules that took your experience team years to learn.
16
00:00:48,920 --> 00:00:51,800
They might ask a colleague for help, but that colleague could be busy.
17
00:00:51,800 --> 00:00:54,560
And if they do interrupt, the colleague loses focus on their own work.
18
00:00:54,560 --> 00:00:58,240
So they search old emails, but an email from two years ago might have an answer that's
19
00:00:58,240 --> 00:01:00,200
now wrong because of policy change.
20
00:01:00,200 --> 00:01:03,520
This is how support knowledge grows without anyone planning it.
21
00:01:03,520 --> 00:01:05,120
It's messy and unreliable.
22
00:01:05,120 --> 00:01:06,880
One person keeps notes in a document.
23
00:01:06,880 --> 00:01:09,520
Another saves useful messages in a mailbox folder.
24
00:01:09,520 --> 00:01:13,360
Someone else just knows because they've handled the same customer problem 50 times before.
25
00:01:13,360 --> 00:01:16,680
The answer exists, but finding it eats up valuable time.
26
00:01:16,680 --> 00:01:18,640
And that time adds up across the whole team.
27
00:01:18,640 --> 00:01:22,320
While the agent searches the customer's frustration builds, customers notice that delay
28
00:01:22,320 --> 00:01:23,320
immediately.
29
00:01:23,320 --> 00:01:25,600
Every second of silence feels like an eternity.
30
00:01:25,600 --> 00:01:28,440
They hear typing, then, can I place you on hold for a moment?
31
00:01:28,440 --> 00:01:32,440
Or worse, they receive a guess because the agent wants to be helpful, but doesn't have
32
00:01:32,440 --> 00:01:34,240
a trusted answer in front of them.
33
00:01:34,240 --> 00:01:35,240
Nobody wants that.
34
00:01:35,240 --> 00:01:36,240
Here's the thing.
35
00:01:36,240 --> 00:01:38,520
The modern customer doesn't care how your team is organized inside.
36
00:01:38,520 --> 00:01:40,920
They just want to consistent answer every time.
37
00:01:40,920 --> 00:01:44,560
Customer service moves quickly, and people expect the same answer, whether they call, email,
38
00:01:44,560 --> 00:01:46,160
chat, or visit your website.
39
00:01:46,160 --> 00:01:50,360
If one agent explains a return policy one way, and another gives a different version,
40
00:01:50,360 --> 00:01:54,320
the customer doesn't see an internal knowledge problem.
41
00:01:54,320 --> 00:01:56,880
They see a company that can't agree with itself.
42
00:01:56,880 --> 00:02:00,360
A shared knowledge base gives the team one approved place to look.
43
00:02:00,360 --> 00:02:04,560
So instead of relying on memory agents, find guidance, the business has checked and agreed
44
00:02:04,560 --> 00:02:05,560
on.
45
00:02:05,560 --> 00:02:08,720
That means the answer stays consistent, even when different people handle the customer.
46
00:02:08,720 --> 00:02:10,360
That helps experienced agents too.
47
00:02:10,360 --> 00:02:11,360
Think about it.
48
00:02:11,360 --> 00:02:15,160
If you're the expert on returns, you answer the same question three times a day.
49
00:02:15,160 --> 00:02:16,640
That's a waste of your expertise.
50
00:02:16,640 --> 00:02:20,720
And the same question appears every day, an expert can spend hours repeating the same answer.
51
00:02:20,720 --> 00:02:24,080
With a good article, they write the guidance once, review it when things change, and let
52
00:02:24,080 --> 00:02:25,400
the whole team use it.
53
00:02:25,400 --> 00:02:28,120
The focus moves from repeating answers to improving them.
54
00:02:28,120 --> 00:02:29,840
You'll also notice patterns more clearly.
55
00:02:29,840 --> 00:02:33,960
If 10 customers ask how to change a delivery address, that might mean the website instructions
56
00:02:33,960 --> 00:02:34,960
are unclear.
57
00:02:34,960 --> 00:02:38,680
If agents keep searching for a billing rule and can't find it, the team knows an article
58
00:02:38,680 --> 00:02:39,680
is missing.
59
00:02:39,680 --> 00:02:42,120
Repeated questions aren't just noise, oh.
60
00:02:42,120 --> 00:02:45,360
They tell you where customers and agents get stuck and give you a practical list of
61
00:02:45,360 --> 00:02:47,360
topics that need clear guidance.
62
00:02:47,360 --> 00:02:51,280
A knowledge base becomes the company's working memory, keeping useful know how available
63
00:02:51,280 --> 00:02:55,720
when someone takes leave, changes jobs, joins the team, or simply forgets a detail during
64
00:02:55,720 --> 00:02:56,720
a busy afternoon.
65
00:02:56,720 --> 00:02:59,440
That doesn't mean every answer should become a long document.
66
00:02:59,440 --> 00:03:03,360
In fact, long documents often create the same problem all over again, because people still
67
00:03:03,360 --> 00:03:05,920
can't spot the one sentence or step they need.
68
00:03:05,920 --> 00:03:10,200
Good knowledge gives people a direct answer, clear steps, and enough context to handle the
69
00:03:10,200 --> 00:03:11,560
situation safely.
70
00:03:11,560 --> 00:03:16,080
So Dynamics 365 Knowledge Management brings this shared memory into the same customer service
71
00:03:16,080 --> 00:03:19,560
world where your support team handles daily work.
72
00:03:19,560 --> 00:03:21,520
It's not a separate tool to learn how.
73
00:03:21,520 --> 00:03:24,680
It's embedded into the tools agents already use every day.
74
00:03:24,680 --> 00:03:28,080
What Dynamics 365 Knowledge Management actually is?
75
00:03:28,080 --> 00:03:31,280
So what does Dynamics 365 Knowledge Management actually give you?
76
00:03:31,280 --> 00:03:32,680
Here's the simplest definition.
77
00:03:32,680 --> 00:03:36,600
It gives your team a single place to create, organize, review, find, and improve help articles
78
00:03:36,600 --> 00:03:39,200
out, all while they're working with customers.
79
00:03:39,200 --> 00:03:41,320
An article is a focused piece of guidance.
80
00:03:41,320 --> 00:03:44,960
It might answer something like, "How do I change my billing address?" or explain what an
81
00:03:44,960 --> 00:03:49,280
agent should check before approving a refund, including the policy link and steps for a special
82
00:03:49,280 --> 00:03:50,280
case.
83
00:03:50,280 --> 00:03:52,840
Now this isn't just a shared folder full of word files and PDFs.
84
00:03:52,840 --> 00:03:57,120
A folder can store information, but you often need to know the file name before you can
85
00:03:57,120 --> 00:03:58,640
find the answer.
86
00:03:58,640 --> 00:04:02,720
Dynamics 365 Knowledge Management works more like a reference
87
00:04:02,720 --> 00:04:05,040
desk inside your customer service department.
88
00:04:05,040 --> 00:04:08,760
Each answer has a title, a subject, and labels that help the right person find it when
89
00:04:08,760 --> 00:04:09,760
they need it.
90
00:04:09,760 --> 00:04:10,760
Think of a large office building.
91
00:04:10,760 --> 00:04:15,240
Your support team works at the customer service desks, dealing with calls, emails, and
92
00:04:15,240 --> 00:04:16,240
cases.
93
00:04:16,240 --> 00:04:18,720
Somewhere nearby sits a staffed reference desk.
94
00:04:18,720 --> 00:04:22,840
Behind that desk, there are clearly labeled folders with answers for billing, delivery, account
95
00:04:22,840 --> 00:04:25,400
access, product setup, and company rules.
96
00:04:25,400 --> 00:04:27,520
That reference desk is your knowledge base.
97
00:04:27,520 --> 00:04:31,720
The articles inside are like those folders, but they aren't all written the same way.
98
00:04:31,720 --> 00:04:36,440
A simple article might start with a short answer for the agent, then list the exact steps.
99
00:04:36,440 --> 00:04:41,160
Some might include links to a policy, a screenshot of what the customer sees, or a related article
100
00:04:41,160 --> 00:04:42,960
for the next likely question.
101
00:04:42,960 --> 00:04:44,480
And the goal isn't to write a textbook.
102
00:04:44,480 --> 00:04:48,520
It's to help someone handle one customer problem correctly without making them read five
103
00:04:48,520 --> 00:04:51,640
pages that only partly relate to the case in front of them.
104
00:04:51,640 --> 00:04:56,200
This ties directly into the work agents already do in Dynamics 365 customer service.
105
00:04:56,200 --> 00:05:00,160
When an agent opens a customer case, they don't have to leave that work area, open another
106
00:05:00,160 --> 00:05:03,400
site, and start a separate search through all documents.
107
00:05:03,400 --> 00:05:07,020
They can look for knowledge while they read the customer's issue, then open guidance that
108
00:05:07,020 --> 00:05:08,360
fits the question.
109
00:05:08,360 --> 00:05:09,880
That keeps the conversation moving.
110
00:05:09,880 --> 00:05:13,540
A case tells the agent what happened, and a knowledge article helps them decide what
111
00:05:13,540 --> 00:05:14,540
to do next.
112
00:05:14,540 --> 00:05:18,340
Put those two pieces together, and the person helping the customer has context and approved
113
00:05:18,340 --> 00:05:19,680
guidance in the same place.
114
00:05:19,680 --> 00:05:22,080
Now, some knowledge belongs only inside the company.
115
00:05:22,080 --> 00:05:26,720
For example, an article might explain internal checks before an agent changes account details,
116
00:05:26,720 --> 00:05:29,560
or list steps for passing a difficult case to another team.
117
00:05:29,560 --> 00:05:31,440
Customers should never see that kind of guidance.
118
00:05:31,440 --> 00:05:35,240
Other articles can answer customer questions directly through a self-service site.
119
00:05:35,240 --> 00:05:38,480
A customer might search for instructions on updating contact details, understanding an
120
00:05:38,480 --> 00:05:41,440
invoice, or resetting a password before they contact support.
121
00:05:41,440 --> 00:05:43,320
Same knowledge system, different audiences.
122
00:05:43,320 --> 00:05:46,920
That means your team can control which articles agents can read, and which articles customers
123
00:05:46,920 --> 00:05:47,920
can read.
124
00:05:47,920 --> 00:05:51,680
The public version should use customer-friendly words and safe instructions, while the internal
125
00:05:51,680 --> 00:05:54,480
version can include the work steps that only staff need.
126
00:05:54,480 --> 00:05:58,000
A lot of people think knowledge management is only for huge call centers with hundreds
127
00:05:58,000 --> 00:06:01,320
of agents, but a small support team can benefit just as much.
128
00:06:01,320 --> 00:06:04,160
If four people answer the same questions, they still need clear answers.
129
00:06:04,160 --> 00:06:08,040
In fact, a smaller team often feels the pain sooner because one person leaving for a
130
00:06:08,040 --> 00:06:11,720
week can take a lot of practical know-how with them.
131
00:06:11,720 --> 00:06:13,120
Dynamics 365.
132
00:06:13,120 --> 00:06:17,200
Knowledge management gives that know-how, a home, a structure, and a way for people to use
133
00:06:17,200 --> 00:06:19,000
it during real customer work.
134
00:06:19,000 --> 00:06:22,640
Next, let's follow a single question from the moment someone spots a missing answer to
135
00:06:22,640 --> 00:06:24,600
the point where the team can rely on it.
136
00:06:24,600 --> 00:06:25,600
Pass.
137
00:06:25,600 --> 00:06:27,040
The life of a knowledge article.
138
00:06:27,040 --> 00:06:29,160
So a knowledge article usually starts with a gap.
139
00:06:29,160 --> 00:06:33,760
Every agent receives a question about a product return, searches the knowledge base, and finds
140
00:06:33,760 --> 00:06:35,080
nothing they trust.
141
00:06:35,080 --> 00:06:39,120
Or perhaps the same question keeps appearing in cases, but every agent handles it a little differently.
142
00:06:39,120 --> 00:06:40,440
That's the moment to create an article.
143
00:06:40,440 --> 00:06:43,960
You want to start with the words customers actually use because those words will often become
144
00:06:43,960 --> 00:06:45,920
the words agents type into search.
145
00:06:45,920 --> 00:06:48,400
If customers ask, "Why can't I see my refund?"
146
00:06:48,400 --> 00:06:52,440
A title like "Check the status of a customer refund" gives the team a much better starting
147
00:06:52,440 --> 00:06:55,080
point than something vague like finance process.
148
00:06:55,080 --> 00:06:56,320
And keep the first answer short.
149
00:06:56,320 --> 00:07:00,280
An agent under pressure needs to see the main point quickly, then follow the detail only
150
00:07:00,280 --> 00:07:01,280
when they need it.
151
00:07:01,280 --> 00:07:04,920
So an article might begin with one sentence that explains when a refund should appear,
152
00:07:04,920 --> 00:07:08,480
followed by "Check the agent needs to complete before giving the customer an answer."
153
00:07:08,480 --> 00:07:10,680
Then write the steps in the order people need them.
154
00:07:10,680 --> 00:07:12,360
What should the agent check first?
155
00:07:12,360 --> 00:07:13,920
Which screen should they open?
156
00:07:13,920 --> 00:07:16,120
What information must they confirm with the customer?
157
00:07:16,120 --> 00:07:19,280
When should they stop and send the case to another team?
158
00:07:19,280 --> 00:07:20,280
Clear steps remove guesswork.
159
00:07:20,280 --> 00:07:25,040
A good article also separates what the customer can do from what only an employee can do.
160
00:07:25,040 --> 00:07:28,680
You might include a link to a public help page for the customer, while the internal version
161
00:07:28,680 --> 00:07:32,600
explains what the agent should check behind the scenes before they close the case.
162
00:07:32,600 --> 00:07:36,120
Pictures can help too, especially when someone needs to find a button or recognize a message
163
00:07:36,120 --> 00:07:37,120
on a screen.
164
00:07:37,120 --> 00:07:38,600
But don't add pictures just to fill space.
165
00:07:38,600 --> 00:07:41,640
If a picture doesn't help someone complete a step, leave it out.
166
00:07:41,640 --> 00:07:45,720
Screen's change, and every image creates another thing the article owner needs to keep
167
00:07:45,720 --> 00:07:46,720
current.
168
00:07:46,720 --> 00:07:50,120
Once the draft has the right answer, it needs labels.
169
00:07:50,120 --> 00:07:53,680
Categories tell people the general subject such as billing, delivery, accounts, or product
170
00:07:53,680 --> 00:07:54,680
setup.
171
00:07:54,680 --> 00:07:57,760
Keywords catch the different words people use for the same problem.
172
00:07:57,760 --> 00:08:01,280
A customer may say money back while an employee searches for refund.
173
00:08:01,280 --> 00:08:04,200
Both should lead to the same article, Language Matters 2.
174
00:08:04,200 --> 00:08:08,240
If your team supports customers in more than one language, each audience needs instructions
175
00:08:08,240 --> 00:08:10,600
they can read and use with confidence.
176
00:08:10,600 --> 00:08:14,560
You can also connect related products and related articles, so a person who solves one
177
00:08:14,560 --> 00:08:18,440
problem can quickly find the next piece of guidance without starting from scratch.
178
00:08:18,440 --> 00:08:19,440
Then comes the review.
179
00:08:19,440 --> 00:08:23,080
The person writing an article may understand the customer problem very well, but they might
180
00:08:23,080 --> 00:08:24,760
not own the policy behind it.
181
00:08:24,760 --> 00:08:27,760
A subject expert checks that the advice is correct.
182
00:08:27,760 --> 00:08:31,600
An article owner decides whether the content is ready for use and who should be able to read
183
00:08:31,600 --> 00:08:32,600
it.
184
00:08:32,600 --> 00:08:34,280
This step protects both the team and the customer.
185
00:08:34,280 --> 00:08:38,400
Imagine an agent writes helpful steps for changing an address, but those steps skip an identity
186
00:08:38,400 --> 00:08:40,440
check required by company policy.
187
00:08:40,440 --> 00:08:44,400
The article may sound clear and friendly, yet it could create a security problem if people
188
00:08:44,400 --> 00:08:46,160
follow it exactly as written.
189
00:08:46,160 --> 00:08:49,240
Approval catches that before the article reaches the service desk.
190
00:08:49,240 --> 00:08:52,440
After approval, you publish the article to the right audience.
191
00:08:52,440 --> 00:08:54,480
Some articles go to employees only.
192
00:08:54,480 --> 00:08:57,040
Others can appear on a customer's self-service site.
193
00:08:57,040 --> 00:09:01,240
The same customer question may need two versions, because staff need internal instructions
194
00:09:01,240 --> 00:09:05,040
while customers need simple, safe actions they can take themselves.
195
00:09:05,040 --> 00:09:06,880
But publishing isn't the finish line.
196
00:09:06,880 --> 00:09:10,680
Products change, company rules change, a button moves, a payment process changes.
197
00:09:10,680 --> 00:09:14,600
If nobody checks the article, yesterday's correct answer can send someone down the wrong
198
00:09:14,600 --> 00:09:15,600
path next month.
199
00:09:15,600 --> 00:09:18,240
That's why articles need an owner and a review date.
200
00:09:18,240 --> 00:09:21,560
Think of each article like a paper file moving across a service desk.
201
00:09:21,560 --> 00:09:24,720
First, it receives a clear label so people can find it.
202
00:09:24,720 --> 00:09:26,560
Then an expert stamps it as checked.
203
00:09:26,560 --> 00:09:29,560
It goes into the current file drawer where staff can rely on it.
204
00:09:29,560 --> 00:09:33,360
When the process changes, you don't leave the old file on the desk beside the new one.
205
00:09:33,360 --> 00:09:37,360
You update the article, keep track of the previous version, and retire content that no
206
00:09:37,360 --> 00:09:38,840
longer belongs in daily work.
207
00:09:38,840 --> 00:09:42,240
That way, people don't pick an old answer just because it happened to appear first.
208
00:09:42,240 --> 00:09:47,240
A knowledge base gets better through this cycle, spot the missing answer, write clear guidance,
209
00:09:47,240 --> 00:09:50,960
check it, publish it, then revisit it when the work changes.
210
00:09:50,960 --> 00:09:54,920
It even a well-written article can't help anyone if it stays hidden when a customer needs an
211
00:09:54,920 --> 00:09:57,080
answer.
212
00:09:57,080 --> 00:09:59,680
Finding knowledge while helping a customer.
213
00:09:59,680 --> 00:10:01,600
So what does this look like in practice?
214
00:10:01,600 --> 00:10:04,960
Here's the moment this system really proves its value.
215
00:10:04,960 --> 00:10:09,840
A customer contacts support because they don't understand a charge on their latest bill.
216
00:10:09,840 --> 00:10:13,720
They are frustrated and want an answer now, and the agent has the case open in Dynamics
217
00:10:13,720 --> 00:10:14,720
365.
218
00:10:14,720 --> 00:10:19,000
The case gives the agent useful context, "oo, the customers account, the type of charge,
219
00:10:19,000 --> 00:10:21,560
and the words the customer used to describe the problem."
220
00:10:21,560 --> 00:10:24,120
From that same work screen, the agent can search the knowledge base.
221
00:10:24,120 --> 00:10:28,000
They might search for duplicate charge or invoice question, and the search engine looks
222
00:10:28,000 --> 00:10:31,640
through article titles, content, categories, and labels to bring back guidance that fits
223
00:10:31,640 --> 00:10:33,680
the case, and that saves a lot of switching around.
224
00:10:33,680 --> 00:10:37,760
Without this integration, an agent would copy a phrase from the case, open a separate
225
00:10:37,760 --> 00:10:42,120
site, search a shared drive, and hope the answer still applies.
226
00:10:42,120 --> 00:10:45,760
But with knowledge connected directly to customer service, the search starts right where
227
00:10:45,760 --> 00:10:46,760
the work happens.
228
00:10:46,760 --> 00:10:51,480
A long list of results doesn't solve the problem, an agent doesn't need 10 articles that vaguely
229
00:10:51,480 --> 00:10:52,480
mention billing.
230
00:10:52,480 --> 00:10:56,120
They need one current article that explains the exact charge the checks to perform the
231
00:10:56,120 --> 00:11:00,080
words to use with the customer, and when to pass the case to someone else.
232
00:11:00,080 --> 00:11:02,440
One good result beats a pile of almost right results.
233
00:11:02,440 --> 00:11:05,960
That's why clear article titles and useful search words matter so much.
234
00:11:05,960 --> 00:11:10,200
An article called "billing information" gives people very little to work with.
235
00:11:10,200 --> 00:11:16,120
While a title like "explain a duplicate monthly subscription charge" tells the agent immediately,
236
00:11:16,120 --> 00:11:18,560
whether they found the right guidance.
237
00:11:18,560 --> 00:11:20,120
Categories narrow the search too.
238
00:11:20,120 --> 00:11:25,120
Categories like "billing, account access, delivery, returns, and product setup" act as broad
239
00:11:25,120 --> 00:11:27,120
signposts.
240
00:11:27,120 --> 00:11:30,600
Once the agent enters the right area, the article title and opening lines help them decide
241
00:11:30,600 --> 00:11:32,800
if it fits this customer situation.
242
00:11:32,800 --> 00:11:36,480
Dynamics 365 can also suggest articles based on what appears in a case.
243
00:11:36,480 --> 00:11:40,280
That sounds helpful and it can be, but the system doesn't replace the person reading the
244
00:11:40,280 --> 00:11:41,280
case.
245
00:11:41,280 --> 00:11:44,880
A suggested article may match a word in the customer's message while missing the actual
246
00:11:44,880 --> 00:11:45,880
problem.
247
00:11:45,880 --> 00:11:49,120
The agent still needs to read the guidance, check the account details, and decide whether
248
00:11:49,120 --> 00:11:50,120
it applies.
249
00:11:50,120 --> 00:11:52,800
Think of it like getting a few possible answers during a quiz.
250
00:11:52,800 --> 00:11:57,040
The answers narrow the work, but you still need to choose the one that fits the question.
251
00:11:57,040 --> 00:12:00,480
Customer service works the same way, especially when billing rules account history or special
252
00:12:00,480 --> 00:12:02,160
customer needs change the next step.
253
00:12:02,160 --> 00:12:03,600
Let's stick with that billing example.
254
00:12:03,600 --> 00:12:07,480
The agent searches for the charge type and opens an approved article about duplicate subscription
255
00:12:07,480 --> 00:12:08,480
payments.
256
00:12:08,480 --> 00:12:12,440
The first part tells them to check whether the customer has more than one active subscription.
257
00:12:12,440 --> 00:12:16,400
Next, it explains how to confirm the payment dates and what to tell the customer if the
258
00:12:16,400 --> 00:12:18,640
second charge came from a separate account.
259
00:12:18,640 --> 00:12:21,880
Then the article gives a clear next step if the charge is truly matched.
260
00:12:21,880 --> 00:12:25,520
Maybe the agent can begin a refund process or maybe another team needs to check the payment
261
00:12:25,520 --> 00:12:26,520
record first.
262
00:12:26,520 --> 00:12:29,560
Either way, the agent doesn't invent a response while the customer waits.
263
00:12:29,560 --> 00:12:33,600
They follow the company's approved process, explain what will happen next, and record
264
00:12:33,600 --> 00:12:34,600
the outcome in the case.
265
00:12:34,600 --> 00:12:38,560
The customer gets a clearer answer, the agent gets less pressure, and the team can see
266
00:12:38,560 --> 00:12:40,760
which guidance helped solve the case.
267
00:12:40,760 --> 00:12:43,920
Storage also helps before a customer reaches an agent.
268
00:12:43,920 --> 00:12:48,480
A self-service site gives customers a place to search for simple answers like how to update
269
00:12:48,480 --> 00:12:52,000
contact details, find an invoice, or reset account access.
270
00:12:52,000 --> 00:12:55,760
When the instructions solve the problem, the customer can carry on without opening a support
271
00:12:55,760 --> 00:12:56,760
request.
272
00:12:56,760 --> 00:12:59,400
That doesn't mean every issue belongs in self-service.
273
00:12:59,400 --> 00:13:03,760
A locked account with unusual activity, a disputed payment, or a customer who needs personal
274
00:13:03,760 --> 00:13:05,920
help still needs a real person.
275
00:13:05,920 --> 00:13:09,800
Knowledge management supports good service, but it doesn't turn customer care into a list
276
00:13:09,800 --> 00:13:10,800
of canned replies.
277
00:13:10,800 --> 00:13:12,360
People still listen and use judgment.
278
00:13:12,360 --> 00:13:15,960
The knowledge base gives them a trusted starting point right when the customer needs one,
279
00:13:15,960 --> 00:13:21,280
but that library only stays useful when someone keeps the content clear, safe, and current.
280
00:13:21,280 --> 00:13:24,480
Keeping knowledge accurate, safe, and useful.
281
00:13:24,480 --> 00:13:27,640
A knowledge base can become unreliable, surprisingly fast.
282
00:13:27,640 --> 00:13:31,960
Someone publishes a helpful answer, a process changes six months later, and nobody returns
283
00:13:31,960 --> 00:13:32,960
to the article.
284
00:13:32,960 --> 00:13:36,600
The old steps remain easy to find, so agents keep following them because they assume published
285
00:13:36,600 --> 00:13:38,080
guidance is still correct.
286
00:13:38,080 --> 00:13:42,040
That's why every article needs a clear owner out, someone who knows who can check the facts,
287
00:13:42,040 --> 00:13:45,560
update the content, and decide when it no longer belongs in use.
288
00:13:45,560 --> 00:13:48,160
The article owner doesn't need to write every word alone.
289
00:13:48,160 --> 00:13:52,360
A support agent may spot the problem, a product team member may know the product rule, and
290
00:13:52,360 --> 00:13:54,800
a finance expert may confirm a billing step.
291
00:13:54,800 --> 00:13:58,760
Still, one person needs to own the final article and keep it on a review schedule.
292
00:13:58,760 --> 00:14:01,960
Without an owner, everybody assumes somebody else will fix it.
293
00:14:01,960 --> 00:14:05,720
Approval gives you a safety check before guidance reaches agents or customers.
294
00:14:05,720 --> 00:14:10,520
A draft may contain the right general idea, but miss a step that protects an account, follows
295
00:14:10,520 --> 00:14:13,160
a company policy or handles an exception properly.
296
00:14:13,160 --> 00:14:16,760
That's especially important when an article tells someone how to change personal details,
297
00:14:16,760 --> 00:14:18,800
discuss payments, or access an account.
298
00:14:18,800 --> 00:14:22,400
A reviewer checks the wording, confirms the process, and decides whether the article is
299
00:14:22,400 --> 00:14:23,400
ready.
300
00:14:23,400 --> 00:14:26,240
The team can then trust that an approved article has gone through more than one person's
301
00:14:26,240 --> 00:14:27,240
memory.
302
00:14:27,240 --> 00:14:28,400
Permissions matter too.
303
00:14:28,400 --> 00:14:32,040
Not everybody should edit every article, and not every article should appear in front
304
00:14:32,040 --> 00:14:33,320
of every reader.
305
00:14:33,320 --> 00:14:37,040
An agent may need internal instructions for checking a customer account, while the customer
306
00:14:37,040 --> 00:14:40,400
only needs safe steps they can take on their own.
307
00:14:40,400 --> 00:14:42,680
Dynamics 365 lets you control that access.
308
00:14:42,680 --> 00:14:47,280
You can decide who writes drafts, who approves them, who publishes them, and who can see internal
309
00:14:47,280 --> 00:14:48,280
only content.
310
00:14:48,280 --> 00:14:51,680
That keeps private work steps away from public pages, while still giving agents what they
311
00:14:51,680 --> 00:14:53,160
need during a case.
312
00:14:53,160 --> 00:14:55,320
Then you need to listen to the people using the articles.
313
00:14:55,320 --> 00:14:59,160
An agent might find an article, but notice that step 4 no longer matches the screen.
314
00:14:59,160 --> 00:15:02,880
A customer may read a self-service article and still contact support because the instructions
315
00:15:02,880 --> 00:15:03,880
feel unclear.
316
00:15:03,880 --> 00:15:07,320
Someone may search three times and find nothing that answers the question.
317
00:15:07,320 --> 00:15:08,920
Those moments are useful signals.
318
00:15:08,920 --> 00:15:12,840
Feedback tells the content owner where guidance works, where it confuses people, and where a
319
00:15:12,840 --> 00:15:14,640
new article may be needed.
320
00:15:14,640 --> 00:15:16,200
Search misses matter as well.
321
00:15:16,200 --> 00:15:19,960
If people keep looking for change delivery address, but no article appears, the knowledge
322
00:15:19,960 --> 00:15:22,360
base has shown you a gap in plain sight.
323
00:15:22,360 --> 00:15:24,440
Repeat cases can point to the same gap.
324
00:15:24,440 --> 00:15:28,120
When the same issue keeps reaching the service team, check whether an article exists, whether
325
00:15:28,120 --> 00:15:31,960
people can find it, and whether the steps actually solve the problem.
326
00:15:31,960 --> 00:15:36,080
The answer may need better wording, a clearer title or a new process behind the scenes.
327
00:15:36,080 --> 00:15:37,520
Keep the writing simple.
328
00:15:37,520 --> 00:15:41,520
Use titles that describe the customer's problem, put one topic in each article, write short
329
00:15:41,520 --> 00:15:45,280
steps in the order people follow them, and use plain words instead of internal terms
330
00:15:45,280 --> 00:15:47,800
that only long time employees understand.
331
00:15:47,800 --> 00:15:51,200
A team can publish hundreds of articles and still leave agents searching.
332
00:15:51,200 --> 00:15:52,200
Volume isn't the goal.
333
00:15:52,200 --> 00:15:56,520
Useful current answers are the goal, and that takes regular review, clear ownership, and
334
00:15:56,520 --> 00:15:58,440
feedback from people doing the work.
335
00:15:58,440 --> 00:16:01,400
Let's put all of that into one customer situation.
336
00:16:01,400 --> 00:16:03,800
A simple end-to-end example.
337
00:16:03,800 --> 00:16:05,560
Let me walk you through a real scenario.
338
00:16:05,560 --> 00:16:09,160
A customer calls in because they can automate access to their online account.
339
00:16:09,160 --> 00:16:12,040
They click the password reset link but no email arrives.
340
00:16:12,040 --> 00:16:13,720
They try again, still nothing.
341
00:16:13,720 --> 00:16:17,560
Now the item re-frustrated out, they need to place an order and connect them at sign-in.
342
00:16:17,560 --> 00:16:22,000
The agent opens the case in Dynamics 365 and searches for our password reset email, not
343
00:16:22,000 --> 00:16:24,000
received.
344
00:16:24,000 --> 00:16:28,440
I/O an approved article appears right away, and the title clearly covers what will
345
00:16:28,440 --> 00:16:32,360
the account's going on.
346
00:16:32,360 --> 00:16:34,360
The agent knows this is the right answer.
347
00:16:34,360 --> 00:16:36,160
The article starts with a checklist.
348
00:16:36,160 --> 00:16:37,640
Confirm the email address on the account.
349
00:16:37,640 --> 00:16:39,880
Check whether the account is temporarily locked.
350
00:16:39,880 --> 00:16:41,800
Ask the customer to look in their junk mail folder.
351
00:16:41,800 --> 00:16:46,360
It even gives the agent safe wording for each step, so they can explain everything without
352
00:16:46,360 --> 00:16:47,960
sharing private account details.
353
00:16:47,960 --> 00:16:51,240
Say the reset email still does no, term t show up.
354
00:16:51,240 --> 00:16:54,360
The article spells out exactly what to do next, including when to send the case to the
355
00:16:54,360 --> 00:16:55,360
account support team.
356
00:16:55,360 --> 00:16:57,360
No vague advice like "Otry again later."
357
00:16:57,360 --> 00:17:01,920
The agent follows the approved steps, records what they checked and links the article to the
358
00:17:01,920 --> 00:17:02,920
case.
359
00:17:02,920 --> 00:17:05,240
But during the call, they notice something missing.
360
00:17:05,240 --> 00:17:09,120
The article tells customers to check junk mail, but it does no tempt mention that some
361
00:17:09,120 --> 00:17:13,440
work email systems block the reset message before it even reaches that folder.
362
00:17:13,440 --> 00:17:14,880
That note goes back to the article owner.
363
00:17:14,880 --> 00:17:18,120
After checking with the right team, the owner updates the article with a short extra step
364
00:17:18,120 --> 00:17:19,840
about work email filtering.
365
00:17:19,840 --> 00:17:23,120
Future agents see the clearer guidance, and the public customer version can include a
366
00:17:23,120 --> 00:17:25,000
safe version of the same advice.
367
00:17:25,000 --> 00:17:27,680
Think of the service desk as one connected workspace.
368
00:17:27,680 --> 00:17:30,440
The case holds the customer out, TMPS issue.
369
00:17:30,440 --> 00:17:32,960
The knowledge base holds the approved guidance.
370
00:17:32,960 --> 00:17:36,760
Internal instructions stay with staff, while a controlled public area gives customers answers
371
00:17:36,760 --> 00:17:38,440
they can safely use themselves.
372
00:17:38,440 --> 00:17:44,080
One customer question exposed to missing detail, and the next customer gets a better answer.
373
00:17:44,080 --> 00:17:45,080
Conclusion
374
00:17:45,080 --> 00:17:47,080
One shared answer
375
00:17:47,080 --> 00:17:51,960
Dynamics 365 knowledge management gives your support team a single place for answers everyone
376
00:17:51,960 --> 00:17:54,120
can trust while they help customers.
377
00:17:54,120 --> 00:17:58,520
Subscribe on your favorite podcast platform for more Microsoft knowledge nuggets with me,
378
00:17:58,520 --> 00:18:00,440
Merco Peters from M365.
379
00:18:00,440 --> 00:18:05,800
FM share this episode with someone building a Dynamics 365 support team, then watch the next
380
00:18:05,800 --> 00:18:08,400
guide to see how the connected platform fits together.
00:00:00,000 --> 00:00:03,800
A customer asks a simple question, but the agent has to hunt through old emails, shared
2
00:00:03,800 --> 00:00:07,440
folders, and somebody's spreadsheet while the customer waits on the line.
3
00:00:07,440 --> 00:00:10,320
That's where Dynamics 365 Knowledge Management comes in.
4
00:00:10,320 --> 00:00:13,520
Think of it as the shared filing cabinet for your support team.
5
00:00:13,520 --> 00:00:16,880
Approved answers live in one place instead of inside people's heads.
6
00:00:16,880 --> 00:00:20,120
It's a central library where every article is reviewed and approved before it reaches the
7
00:00:20,120 --> 00:00:21,120
team.
8
00:00:21,120 --> 00:00:25,320
I'm Mirko Peters from M365FM, and this is a Microsoft Knowledge Nugget.
9
00:00:25,320 --> 00:00:30,280
You'll see how articles search, access, feedback, and daily support work fit together.
10
00:00:30,280 --> 00:00:33,000
First though, let me show you the raw problem this solves.
11
00:00:33,000 --> 00:00:35,480
It's bigger than you might think.
12
00:00:35,480 --> 00:00:38,520
Why teams need a shared knowledge base?
13
00:00:38,520 --> 00:00:40,920
Imagine a new support agent starts on Monday.
14
00:00:40,920 --> 00:00:44,760
By Tuesday, I'll just two days and how they're answering questions about returns, billing,
15
00:00:44,760 --> 00:00:48,920
account access, and product rules that took your experience team years to learn.
16
00:00:48,920 --> 00:00:51,800
They might ask a colleague for help, but that colleague could be busy.
17
00:00:51,800 --> 00:00:54,560
And if they do interrupt, the colleague loses focus on their own work.
18
00:00:54,560 --> 00:00:58,240
So they search old emails, but an email from two years ago might have an answer that's
19
00:00:58,240 --> 00:01:00,200
now wrong because of policy change.
20
00:01:00,200 --> 00:01:03,520
This is how support knowledge grows without anyone planning it.
21
00:01:03,520 --> 00:01:05,120
It's messy and unreliable.
22
00:01:05,120 --> 00:01:06,880
One person keeps notes in a document.
23
00:01:06,880 --> 00:01:09,520
Another saves useful messages in a mailbox folder.
24
00:01:09,520 --> 00:01:13,360
Someone else just knows because they've handled the same customer problem 50 times before.
25
00:01:13,360 --> 00:01:16,680
The answer exists, but finding it eats up valuable time.
26
00:01:16,680 --> 00:01:18,640
And that time adds up across the whole team.
27
00:01:18,640 --> 00:01:22,320
While the agent searches the customer's frustration builds, customers notice that delay
28
00:01:22,320 --> 00:01:23,320
immediately.
29
00:01:23,320 --> 00:01:25,600
Every second of silence feels like an eternity.
30
00:01:25,600 --> 00:01:28,440
They hear typing, then, can I place you on hold for a moment?
31
00:01:28,440 --> 00:01:32,440
Or worse, they receive a guess because the agent wants to be helpful, but doesn't have
32
00:01:32,440 --> 00:01:34,240
a trusted answer in front of them.
33
00:01:34,240 --> 00:01:35,240
Nobody wants that.
34
00:01:35,240 --> 00:01:36,240
Here's the thing.
35
00:01:36,240 --> 00:01:38,520
The modern customer doesn't care how your team is organized inside.
36
00:01:38,520 --> 00:01:40,920
They just want to consistent answer every time.
37
00:01:40,920 --> 00:01:44,560
Customer service moves quickly, and people expect the same answer, whether they call, email,
38
00:01:44,560 --> 00:01:46,160
chat, or visit your website.
39
00:01:46,160 --> 00:01:50,360
If one agent explains a return policy one way, and another gives a different version,
40
00:01:50,360 --> 00:01:54,320
the customer doesn't see an internal knowledge problem.
41
00:01:54,320 --> 00:01:56,880
They see a company that can't agree with itself.
42
00:01:56,880 --> 00:02:00,360
A shared knowledge base gives the team one approved place to look.
43
00:02:00,360 --> 00:02:04,560
So instead of relying on memory agents, find guidance, the business has checked and agreed
44
00:02:04,560 --> 00:02:05,560
on.
45
00:02:05,560 --> 00:02:08,720
That means the answer stays consistent, even when different people handle the customer.
46
00:02:08,720 --> 00:02:10,360
That helps experienced agents too.
47
00:02:10,360 --> 00:02:11,360
Think about it.
48
00:02:11,360 --> 00:02:15,160
If you're the expert on returns, you answer the same question three times a day.
49
00:02:15,160 --> 00:02:16,640
That's a waste of your expertise.
50
00:02:16,640 --> 00:02:20,720
And the same question appears every day, an expert can spend hours repeating the same answer.
51
00:02:20,720 --> 00:02:24,080
With a good article, they write the guidance once, review it when things change, and let
52
00:02:24,080 --> 00:02:25,400
the whole team use it.
53
00:02:25,400 --> 00:02:28,120
The focus moves from repeating answers to improving them.
54
00:02:28,120 --> 00:02:29,840
You'll also notice patterns more clearly.
55
00:02:29,840 --> 00:02:33,960
If 10 customers ask how to change a delivery address, that might mean the website instructions
56
00:02:33,960 --> 00:02:34,960
are unclear.
57
00:02:34,960 --> 00:02:38,680
If agents keep searching for a billing rule and can't find it, the team knows an article
58
00:02:38,680 --> 00:02:39,680
is missing.
59
00:02:39,680 --> 00:02:42,120
Repeated questions aren't just noise, oh.
60
00:02:42,120 --> 00:02:45,360
They tell you where customers and agents get stuck and give you a practical list of
61
00:02:45,360 --> 00:02:47,360
topics that need clear guidance.
62
00:02:47,360 --> 00:02:51,280
A knowledge base becomes the company's working memory, keeping useful know how available
63
00:02:51,280 --> 00:02:55,720
when someone takes leave, changes jobs, joins the team, or simply forgets a detail during
64
00:02:55,720 --> 00:02:56,720
a busy afternoon.
65
00:02:56,720 --> 00:02:59,440
That doesn't mean every answer should become a long document.
66
00:02:59,440 --> 00:03:03,360
In fact, long documents often create the same problem all over again, because people still
67
00:03:03,360 --> 00:03:05,920
can't spot the one sentence or step they need.
68
00:03:05,920 --> 00:03:10,200
Good knowledge gives people a direct answer, clear steps, and enough context to handle the
69
00:03:10,200 --> 00:03:11,560
situation safely.
70
00:03:11,560 --> 00:03:16,080
So Dynamics 365 Knowledge Management brings this shared memory into the same customer service
71
00:03:16,080 --> 00:03:19,560
world where your support team handles daily work.
72
00:03:19,560 --> 00:03:21,520
It's not a separate tool to learn how.
73
00:03:21,520 --> 00:03:24,680
It's embedded into the tools agents already use every day.
74
00:03:24,680 --> 00:03:28,080
What Dynamics 365 Knowledge Management actually is?
75
00:03:28,080 --> 00:03:31,280
So what does Dynamics 365 Knowledge Management actually give you?
76
00:03:31,280 --> 00:03:32,680
Here's the simplest definition.
77
00:03:32,680 --> 00:03:36,600
It gives your team a single place to create, organize, review, find, and improve help articles
78
00:03:36,600 --> 00:03:39,200
out, all while they're working with customers.
79
00:03:39,200 --> 00:03:41,320
An article is a focused piece of guidance.
80
00:03:41,320 --> 00:03:44,960
It might answer something like, "How do I change my billing address?" or explain what an
81
00:03:44,960 --> 00:03:49,280
agent should check before approving a refund, including the policy link and steps for a special
82
00:03:49,280 --> 00:03:50,280
case.
83
00:03:50,280 --> 00:03:52,840
Now this isn't just a shared folder full of word files and PDFs.
84
00:03:52,840 --> 00:03:57,120
A folder can store information, but you often need to know the file name before you can
85
00:03:57,120 --> 00:03:58,640
find the answer.
86
00:03:58,640 --> 00:04:02,720
Dynamics 365 Knowledge Management works more like a reference
87
00:04:02,720 --> 00:04:05,040
desk inside your customer service department.
88
00:04:05,040 --> 00:04:08,760
Each answer has a title, a subject, and labels that help the right person find it when
89
00:04:08,760 --> 00:04:09,760
they need it.
90
00:04:09,760 --> 00:04:10,760
Think of a large office building.
91
00:04:10,760 --> 00:04:15,240
Your support team works at the customer service desks, dealing with calls, emails, and
92
00:04:15,240 --> 00:04:16,240
cases.
93
00:04:16,240 --> 00:04:18,720
Somewhere nearby sits a staffed reference desk.
94
00:04:18,720 --> 00:04:22,840
Behind that desk, there are clearly labeled folders with answers for billing, delivery, account
95
00:04:22,840 --> 00:04:25,400
access, product setup, and company rules.
96
00:04:25,400 --> 00:04:27,520
That reference desk is your knowledge base.
97
00:04:27,520 --> 00:04:31,720
The articles inside are like those folders, but they aren't all written the same way.
98
00:04:31,720 --> 00:04:36,440
A simple article might start with a short answer for the agent, then list the exact steps.
99
00:04:36,440 --> 00:04:41,160
Some might include links to a policy, a screenshot of what the customer sees, or a related article
100
00:04:41,160 --> 00:04:42,960
for the next likely question.
101
00:04:42,960 --> 00:04:44,480
And the goal isn't to write a textbook.
102
00:04:44,480 --> 00:04:48,520
It's to help someone handle one customer problem correctly without making them read five
103
00:04:48,520 --> 00:04:51,640
pages that only partly relate to the case in front of them.
104
00:04:51,640 --> 00:04:56,200
This ties directly into the work agents already do in Dynamics 365 customer service.
105
00:04:56,200 --> 00:05:00,160
When an agent opens a customer case, they don't have to leave that work area, open another
106
00:05:00,160 --> 00:05:03,400
site, and start a separate search through all documents.
107
00:05:03,400 --> 00:05:07,020
They can look for knowledge while they read the customer's issue, then open guidance that
108
00:05:07,020 --> 00:05:08,360
fits the question.
109
00:05:08,360 --> 00:05:09,880
That keeps the conversation moving.
110
00:05:09,880 --> 00:05:13,540
A case tells the agent what happened, and a knowledge article helps them decide what
111
00:05:13,540 --> 00:05:14,540
to do next.
112
00:05:14,540 --> 00:05:18,340
Put those two pieces together, and the person helping the customer has context and approved
113
00:05:18,340 --> 00:05:19,680
guidance in the same place.
114
00:05:19,680 --> 00:05:22,080
Now, some knowledge belongs only inside the company.
115
00:05:22,080 --> 00:05:26,720
For example, an article might explain internal checks before an agent changes account details,
116
00:05:26,720 --> 00:05:29,560
or list steps for passing a difficult case to another team.
117
00:05:29,560 --> 00:05:31,440
Customers should never see that kind of guidance.
118
00:05:31,440 --> 00:05:35,240
Other articles can answer customer questions directly through a self-service site.
119
00:05:35,240 --> 00:05:38,480
A customer might search for instructions on updating contact details, understanding an
120
00:05:38,480 --> 00:05:41,440
invoice, or resetting a password before they contact support.
121
00:05:41,440 --> 00:05:43,320
Same knowledge system, different audiences.
122
00:05:43,320 --> 00:05:46,920
That means your team can control which articles agents can read, and which articles customers
123
00:05:46,920 --> 00:05:47,920
can read.
124
00:05:47,920 --> 00:05:51,680
The public version should use customer-friendly words and safe instructions, while the internal
125
00:05:51,680 --> 00:05:54,480
version can include the work steps that only staff need.
126
00:05:54,480 --> 00:05:58,000
A lot of people think knowledge management is only for huge call centers with hundreds
127
00:05:58,000 --> 00:06:01,320
of agents, but a small support team can benefit just as much.
128
00:06:01,320 --> 00:06:04,160
If four people answer the same questions, they still need clear answers.
129
00:06:04,160 --> 00:06:08,040
In fact, a smaller team often feels the pain sooner because one person leaving for a
130
00:06:08,040 --> 00:06:11,720
week can take a lot of practical know-how with them.
131
00:06:11,720 --> 00:06:13,120
Dynamics 365.
132
00:06:13,120 --> 00:06:17,200
Knowledge management gives that know-how, a home, a structure, and a way for people to use
133
00:06:17,200 --> 00:06:19,000
it during real customer work.
134
00:06:19,000 --> 00:06:22,640
Next, let's follow a single question from the moment someone spots a missing answer to
135
00:06:22,640 --> 00:06:24,600
the point where the team can rely on it.
136
00:06:24,600 --> 00:06:25,600
Pass.
137
00:06:25,600 --> 00:06:27,040
The life of a knowledge article.
138
00:06:27,040 --> 00:06:29,160
So a knowledge article usually starts with a gap.
139
00:06:29,160 --> 00:06:33,760
Every agent receives a question about a product return, searches the knowledge base, and finds
140
00:06:33,760 --> 00:06:35,080
nothing they trust.
141
00:06:35,080 --> 00:06:39,120
Or perhaps the same question keeps appearing in cases, but every agent handles it a little differently.
142
00:06:39,120 --> 00:06:40,440
That's the moment to create an article.
143
00:06:40,440 --> 00:06:43,960
You want to start with the words customers actually use because those words will often become
144
00:06:43,960 --> 00:06:45,920
the words agents type into search.
145
00:06:45,920 --> 00:06:48,400
If customers ask, "Why can't I see my refund?"
146
00:06:48,400 --> 00:06:52,440
A title like "Check the status of a customer refund" gives the team a much better starting
147
00:06:52,440 --> 00:06:55,080
point than something vague like finance process.
148
00:06:55,080 --> 00:06:56,320
And keep the first answer short.
149
00:06:56,320 --> 00:07:00,280
An agent under pressure needs to see the main point quickly, then follow the detail only
150
00:07:00,280 --> 00:07:01,280
when they need it.
151
00:07:01,280 --> 00:07:04,920
So an article might begin with one sentence that explains when a refund should appear,
152
00:07:04,920 --> 00:07:08,480
followed by "Check the agent needs to complete before giving the customer an answer."
153
00:07:08,480 --> 00:07:10,680
Then write the steps in the order people need them.
154
00:07:10,680 --> 00:07:12,360
What should the agent check first?
155
00:07:12,360 --> 00:07:13,920
Which screen should they open?
156
00:07:13,920 --> 00:07:16,120
What information must they confirm with the customer?
157
00:07:16,120 --> 00:07:19,280
When should they stop and send the case to another team?
158
00:07:19,280 --> 00:07:20,280
Clear steps remove guesswork.
159
00:07:20,280 --> 00:07:25,040
A good article also separates what the customer can do from what only an employee can do.
160
00:07:25,040 --> 00:07:28,680
You might include a link to a public help page for the customer, while the internal version
161
00:07:28,680 --> 00:07:32,600
explains what the agent should check behind the scenes before they close the case.
162
00:07:32,600 --> 00:07:36,120
Pictures can help too, especially when someone needs to find a button or recognize a message
163
00:07:36,120 --> 00:07:37,120
on a screen.
164
00:07:37,120 --> 00:07:38,600
But don't add pictures just to fill space.
165
00:07:38,600 --> 00:07:41,640
If a picture doesn't help someone complete a step, leave it out.
166
00:07:41,640 --> 00:07:45,720
Screen's change, and every image creates another thing the article owner needs to keep
167
00:07:45,720 --> 00:07:46,720
current.
168
00:07:46,720 --> 00:07:50,120
Once the draft has the right answer, it needs labels.
169
00:07:50,120 --> 00:07:53,680
Categories tell people the general subject such as billing, delivery, accounts, or product
170
00:07:53,680 --> 00:07:54,680
setup.
171
00:07:54,680 --> 00:07:57,760
Keywords catch the different words people use for the same problem.
172
00:07:57,760 --> 00:08:01,280
A customer may say money back while an employee searches for refund.
173
00:08:01,280 --> 00:08:04,200
Both should lead to the same article, Language Matters 2.
174
00:08:04,200 --> 00:08:08,240
If your team supports customers in more than one language, each audience needs instructions
175
00:08:08,240 --> 00:08:10,600
they can read and use with confidence.
176
00:08:10,600 --> 00:08:14,560
You can also connect related products and related articles, so a person who solves one
177
00:08:14,560 --> 00:08:18,440
problem can quickly find the next piece of guidance without starting from scratch.
178
00:08:18,440 --> 00:08:19,440
Then comes the review.
179
00:08:19,440 --> 00:08:23,080
The person writing an article may understand the customer problem very well, but they might
180
00:08:23,080 --> 00:08:24,760
not own the policy behind it.
181
00:08:24,760 --> 00:08:27,760
A subject expert checks that the advice is correct.
182
00:08:27,760 --> 00:08:31,600
An article owner decides whether the content is ready for use and who should be able to read
183
00:08:31,600 --> 00:08:32,600
it.
184
00:08:32,600 --> 00:08:34,280
This step protects both the team and the customer.
185
00:08:34,280 --> 00:08:38,400
Imagine an agent writes helpful steps for changing an address, but those steps skip an identity
186
00:08:38,400 --> 00:08:40,440
check required by company policy.
187
00:08:40,440 --> 00:08:44,400
The article may sound clear and friendly, yet it could create a security problem if people
188
00:08:44,400 --> 00:08:46,160
follow it exactly as written.
189
00:08:46,160 --> 00:08:49,240
Approval catches that before the article reaches the service desk.
190
00:08:49,240 --> 00:08:52,440
After approval, you publish the article to the right audience.
191
00:08:52,440 --> 00:08:54,480
Some articles go to employees only.
192
00:08:54,480 --> 00:08:57,040
Others can appear on a customer's self-service site.
193
00:08:57,040 --> 00:09:01,240
The same customer question may need two versions, because staff need internal instructions
194
00:09:01,240 --> 00:09:05,040
while customers need simple, safe actions they can take themselves.
195
00:09:05,040 --> 00:09:06,880
But publishing isn't the finish line.
196
00:09:06,880 --> 00:09:10,680
Products change, company rules change, a button moves, a payment process changes.
197
00:09:10,680 --> 00:09:14,600
If nobody checks the article, yesterday's correct answer can send someone down the wrong
198
00:09:14,600 --> 00:09:15,600
path next month.
199
00:09:15,600 --> 00:09:18,240
That's why articles need an owner and a review date.
200
00:09:18,240 --> 00:09:21,560
Think of each article like a paper file moving across a service desk.
201
00:09:21,560 --> 00:09:24,720
First, it receives a clear label so people can find it.
202
00:09:24,720 --> 00:09:26,560
Then an expert stamps it as checked.
203
00:09:26,560 --> 00:09:29,560
It goes into the current file drawer where staff can rely on it.
204
00:09:29,560 --> 00:09:33,360
When the process changes, you don't leave the old file on the desk beside the new one.
205
00:09:33,360 --> 00:09:37,360
You update the article, keep track of the previous version, and retire content that no
206
00:09:37,360 --> 00:09:38,840
longer belongs in daily work.
207
00:09:38,840 --> 00:09:42,240
That way, people don't pick an old answer just because it happened to appear first.
208
00:09:42,240 --> 00:09:47,240
A knowledge base gets better through this cycle, spot the missing answer, write clear guidance,
209
00:09:47,240 --> 00:09:50,960
check it, publish it, then revisit it when the work changes.
210
00:09:50,960 --> 00:09:54,920
It even a well-written article can't help anyone if it stays hidden when a customer needs an
211
00:09:54,920 --> 00:09:57,080
answer.
212
00:09:57,080 --> 00:09:59,680
Finding knowledge while helping a customer.
213
00:09:59,680 --> 00:10:01,600
So what does this look like in practice?
214
00:10:01,600 --> 00:10:04,960
Here's the moment this system really proves its value.
215
00:10:04,960 --> 00:10:09,840
A customer contacts support because they don't understand a charge on their latest bill.
216
00:10:09,840 --> 00:10:13,720
They are frustrated and want an answer now, and the agent has the case open in Dynamics
217
00:10:13,720 --> 00:10:14,720
365.
218
00:10:14,720 --> 00:10:19,000
The case gives the agent useful context, "oo, the customers account, the type of charge,
219
00:10:19,000 --> 00:10:21,560
and the words the customer used to describe the problem."
220
00:10:21,560 --> 00:10:24,120
From that same work screen, the agent can search the knowledge base.
221
00:10:24,120 --> 00:10:28,000
They might search for duplicate charge or invoice question, and the search engine looks
222
00:10:28,000 --> 00:10:31,640
through article titles, content, categories, and labels to bring back guidance that fits
223
00:10:31,640 --> 00:10:33,680
the case, and that saves a lot of switching around.
224
00:10:33,680 --> 00:10:37,760
Without this integration, an agent would copy a phrase from the case, open a separate
225
00:10:37,760 --> 00:10:42,120
site, search a shared drive, and hope the answer still applies.
226
00:10:42,120 --> 00:10:45,760
But with knowledge connected directly to customer service, the search starts right where
227
00:10:45,760 --> 00:10:46,760
the work happens.
228
00:10:46,760 --> 00:10:51,480
A long list of results doesn't solve the problem, an agent doesn't need 10 articles that vaguely
229
00:10:51,480 --> 00:10:52,480
mention billing.
230
00:10:52,480 --> 00:10:56,120
They need one current article that explains the exact charge the checks to perform the
231
00:10:56,120 --> 00:11:00,080
words to use with the customer, and when to pass the case to someone else.
232
00:11:00,080 --> 00:11:02,440
One good result beats a pile of almost right results.
233
00:11:02,440 --> 00:11:05,960
That's why clear article titles and useful search words matter so much.
234
00:11:05,960 --> 00:11:10,200
An article called "billing information" gives people very little to work with.
235
00:11:10,200 --> 00:11:16,120
While a title like "explain a duplicate monthly subscription charge" tells the agent immediately,
236
00:11:16,120 --> 00:11:18,560
whether they found the right guidance.
237
00:11:18,560 --> 00:11:20,120
Categories narrow the search too.
238
00:11:20,120 --> 00:11:25,120
Categories like "billing, account access, delivery, returns, and product setup" act as broad
239
00:11:25,120 --> 00:11:27,120
signposts.
240
00:11:27,120 --> 00:11:30,600
Once the agent enters the right area, the article title and opening lines help them decide
241
00:11:30,600 --> 00:11:32,800
if it fits this customer situation.
242
00:11:32,800 --> 00:11:36,480
Dynamics 365 can also suggest articles based on what appears in a case.
243
00:11:36,480 --> 00:11:40,280
That sounds helpful and it can be, but the system doesn't replace the person reading the
244
00:11:40,280 --> 00:11:41,280
case.
245
00:11:41,280 --> 00:11:44,880
A suggested article may match a word in the customer's message while missing the actual
246
00:11:44,880 --> 00:11:45,880
problem.
247
00:11:45,880 --> 00:11:49,120
The agent still needs to read the guidance, check the account details, and decide whether
248
00:11:49,120 --> 00:11:50,120
it applies.
249
00:11:50,120 --> 00:11:52,800
Think of it like getting a few possible answers during a quiz.
250
00:11:52,800 --> 00:11:57,040
The answers narrow the work, but you still need to choose the one that fits the question.
251
00:11:57,040 --> 00:12:00,480
Customer service works the same way, especially when billing rules account history or special
252
00:12:00,480 --> 00:12:02,160
customer needs change the next step.
253
00:12:02,160 --> 00:12:03,600
Let's stick with that billing example.
254
00:12:03,600 --> 00:12:07,480
The agent searches for the charge type and opens an approved article about duplicate subscription
255
00:12:07,480 --> 00:12:08,480
payments.
256
00:12:08,480 --> 00:12:12,440
The first part tells them to check whether the customer has more than one active subscription.
257
00:12:12,440 --> 00:12:16,400
Next, it explains how to confirm the payment dates and what to tell the customer if the
258
00:12:16,400 --> 00:12:18,640
second charge came from a separate account.
259
00:12:18,640 --> 00:12:21,880
Then the article gives a clear next step if the charge is truly matched.
260
00:12:21,880 --> 00:12:25,520
Maybe the agent can begin a refund process or maybe another team needs to check the payment
261
00:12:25,520 --> 00:12:26,520
record first.
262
00:12:26,520 --> 00:12:29,560
Either way, the agent doesn't invent a response while the customer waits.
263
00:12:29,560 --> 00:12:33,600
They follow the company's approved process, explain what will happen next, and record
264
00:12:33,600 --> 00:12:34,600
the outcome in the case.
265
00:12:34,600 --> 00:12:38,560
The customer gets a clearer answer, the agent gets less pressure, and the team can see
266
00:12:38,560 --> 00:12:40,760
which guidance helped solve the case.
267
00:12:40,760 --> 00:12:43,920
Storage also helps before a customer reaches an agent.
268
00:12:43,920 --> 00:12:48,480
A self-service site gives customers a place to search for simple answers like how to update
269
00:12:48,480 --> 00:12:52,000
contact details, find an invoice, or reset account access.
270
00:12:52,000 --> 00:12:55,760
When the instructions solve the problem, the customer can carry on without opening a support
271
00:12:55,760 --> 00:12:56,760
request.
272
00:12:56,760 --> 00:12:59,400
That doesn't mean every issue belongs in self-service.
273
00:12:59,400 --> 00:13:03,760
A locked account with unusual activity, a disputed payment, or a customer who needs personal
274
00:13:03,760 --> 00:13:05,920
help still needs a real person.
275
00:13:05,920 --> 00:13:09,800
Knowledge management supports good service, but it doesn't turn customer care into a list
276
00:13:09,800 --> 00:13:10,800
of canned replies.
277
00:13:10,800 --> 00:13:12,360
People still listen and use judgment.
278
00:13:12,360 --> 00:13:15,960
The knowledge base gives them a trusted starting point right when the customer needs one,
279
00:13:15,960 --> 00:13:21,280
but that library only stays useful when someone keeps the content clear, safe, and current.
280
00:13:21,280 --> 00:13:24,480
Keeping knowledge accurate, safe, and useful.
281
00:13:24,480 --> 00:13:27,640
A knowledge base can become unreliable, surprisingly fast.
282
00:13:27,640 --> 00:13:31,960
Someone publishes a helpful answer, a process changes six months later, and nobody returns
283
00:13:31,960 --> 00:13:32,960
to the article.
284
00:13:32,960 --> 00:13:36,600
The old steps remain easy to find, so agents keep following them because they assume published
285
00:13:36,600 --> 00:13:38,080
guidance is still correct.
286
00:13:38,080 --> 00:13:42,040
That's why every article needs a clear owner out, someone who knows who can check the facts,
287
00:13:42,040 --> 00:13:45,560
update the content, and decide when it no longer belongs in use.
288
00:13:45,560 --> 00:13:48,160
The article owner doesn't need to write every word alone.
289
00:13:48,160 --> 00:13:52,360
A support agent may spot the problem, a product team member may know the product rule, and
290
00:13:52,360 --> 00:13:54,800
a finance expert may confirm a billing step.
291
00:13:54,800 --> 00:13:58,760
Still, one person needs to own the final article and keep it on a review schedule.
292
00:13:58,760 --> 00:14:01,960
Without an owner, everybody assumes somebody else will fix it.
293
00:14:01,960 --> 00:14:05,720
Approval gives you a safety check before guidance reaches agents or customers.
294
00:14:05,720 --> 00:14:10,520
A draft may contain the right general idea, but miss a step that protects an account, follows
295
00:14:10,520 --> 00:14:13,160
a company policy or handles an exception properly.
296
00:14:13,160 --> 00:14:16,760
That's especially important when an article tells someone how to change personal details,
297
00:14:16,760 --> 00:14:18,800
discuss payments, or access an account.
298
00:14:18,800 --> 00:14:22,400
A reviewer checks the wording, confirms the process, and decides whether the article is
299
00:14:22,400 --> 00:14:23,400
ready.
300
00:14:23,400 --> 00:14:26,240
The team can then trust that an approved article has gone through more than one person's
301
00:14:26,240 --> 00:14:27,240
memory.
302
00:14:27,240 --> 00:14:28,400
Permissions matter too.
303
00:14:28,400 --> 00:14:32,040
Not everybody should edit every article, and not every article should appear in front
304
00:14:32,040 --> 00:14:33,320
of every reader.
305
00:14:33,320 --> 00:14:37,040
An agent may need internal instructions for checking a customer account, while the customer
306
00:14:37,040 --> 00:14:40,400
only needs safe steps they can take on their own.
307
00:14:40,400 --> 00:14:42,680
Dynamics 365 lets you control that access.
308
00:14:42,680 --> 00:14:47,280
You can decide who writes drafts, who approves them, who publishes them, and who can see internal
309
00:14:47,280 --> 00:14:48,280
only content.
310
00:14:48,280 --> 00:14:51,680
That keeps private work steps away from public pages, while still giving agents what they
311
00:14:51,680 --> 00:14:53,160
need during a case.
312
00:14:53,160 --> 00:14:55,320
Then you need to listen to the people using the articles.
313
00:14:55,320 --> 00:14:59,160
An agent might find an article, but notice that step 4 no longer matches the screen.
314
00:14:59,160 --> 00:15:02,880
A customer may read a self-service article and still contact support because the instructions
315
00:15:02,880 --> 00:15:03,880
feel unclear.
316
00:15:03,880 --> 00:15:07,320
Someone may search three times and find nothing that answers the question.
317
00:15:07,320 --> 00:15:08,920
Those moments are useful signals.
318
00:15:08,920 --> 00:15:12,840
Feedback tells the content owner where guidance works, where it confuses people, and where a
319
00:15:12,840 --> 00:15:14,640
new article may be needed.
320
00:15:14,640 --> 00:15:16,200
Search misses matter as well.
321
00:15:16,200 --> 00:15:19,960
If people keep looking for change delivery address, but no article appears, the knowledge
322
00:15:19,960 --> 00:15:22,360
base has shown you a gap in plain sight.
323
00:15:22,360 --> 00:15:24,440
Repeat cases can point to the same gap.
324
00:15:24,440 --> 00:15:28,120
When the same issue keeps reaching the service team, check whether an article exists, whether
325
00:15:28,120 --> 00:15:31,960
people can find it, and whether the steps actually solve the problem.
326
00:15:31,960 --> 00:15:36,080
The answer may need better wording, a clearer title or a new process behind the scenes.
327
00:15:36,080 --> 00:15:37,520
Keep the writing simple.
328
00:15:37,520 --> 00:15:41,520
Use titles that describe the customer's problem, put one topic in each article, write short
329
00:15:41,520 --> 00:15:45,280
steps in the order people follow them, and use plain words instead of internal terms
330
00:15:45,280 --> 00:15:47,800
that only long time employees understand.
331
00:15:47,800 --> 00:15:51,200
A team can publish hundreds of articles and still leave agents searching.
332
00:15:51,200 --> 00:15:52,200
Volume isn't the goal.
333
00:15:52,200 --> 00:15:56,520
Useful current answers are the goal, and that takes regular review, clear ownership, and
334
00:15:56,520 --> 00:15:58,440
feedback from people doing the work.
335
00:15:58,440 --> 00:16:01,400
Let's put all of that into one customer situation.
336
00:16:01,400 --> 00:16:03,800
A simple end-to-end example.
337
00:16:03,800 --> 00:16:05,560
Let me walk you through a real scenario.
338
00:16:05,560 --> 00:16:09,160
A customer calls in because they can automate access to their online account.
339
00:16:09,160 --> 00:16:12,040
They click the password reset link but no email arrives.
340
00:16:12,040 --> 00:16:13,720
They try again, still nothing.
341
00:16:13,720 --> 00:16:17,560
Now the item re-frustrated out, they need to place an order and connect them at sign-in.
342
00:16:17,560 --> 00:16:22,000
The agent opens the case in Dynamics 365 and searches for our password reset email, not
343
00:16:22,000 --> 00:16:24,000
received.
344
00:16:24,000 --> 00:16:28,440
I/O an approved article appears right away, and the title clearly covers what will
345
00:16:28,440 --> 00:16:32,360
the account's going on.
346
00:16:32,360 --> 00:16:34,360
The agent knows this is the right answer.
347
00:16:34,360 --> 00:16:36,160
The article starts with a checklist.
348
00:16:36,160 --> 00:16:37,640
Confirm the email address on the account.
349
00:16:37,640 --> 00:16:39,880
Check whether the account is temporarily locked.
350
00:16:39,880 --> 00:16:41,800
Ask the customer to look in their junk mail folder.
351
00:16:41,800 --> 00:16:46,360
It even gives the agent safe wording for each step, so they can explain everything without
352
00:16:46,360 --> 00:16:47,960
sharing private account details.
353
00:16:47,960 --> 00:16:51,240
Say the reset email still does no, term t show up.
354
00:16:51,240 --> 00:16:54,360
The article spells out exactly what to do next, including when to send the case to the
355
00:16:54,360 --> 00:16:55,360
account support team.
356
00:16:55,360 --> 00:16:57,360
No vague advice like "Otry again later."
357
00:16:57,360 --> 00:17:01,920
The agent follows the approved steps, records what they checked and links the article to the
358
00:17:01,920 --> 00:17:02,920
case.
359
00:17:02,920 --> 00:17:05,240
But during the call, they notice something missing.
360
00:17:05,240 --> 00:17:09,120
The article tells customers to check junk mail, but it does no tempt mention that some
361
00:17:09,120 --> 00:17:13,440
work email systems block the reset message before it even reaches that folder.
362
00:17:13,440 --> 00:17:14,880
That note goes back to the article owner.
363
00:17:14,880 --> 00:17:18,120
After checking with the right team, the owner updates the article with a short extra step
364
00:17:18,120 --> 00:17:19,840
about work email filtering.
365
00:17:19,840 --> 00:17:23,120
Future agents see the clearer guidance, and the public customer version can include a
366
00:17:23,120 --> 00:17:25,000
safe version of the same advice.
367
00:17:25,000 --> 00:17:27,680
Think of the service desk as one connected workspace.
368
00:17:27,680 --> 00:17:30,440
The case holds the customer out, TMPS issue.
369
00:17:30,440 --> 00:17:32,960
The knowledge base holds the approved guidance.
370
00:17:32,960 --> 00:17:36,760
Internal instructions stay with staff, while a controlled public area gives customers answers
371
00:17:36,760 --> 00:17:38,440
they can safely use themselves.
372
00:17:38,440 --> 00:17:44,080
One customer question exposed to missing detail, and the next customer gets a better answer.
373
00:17:44,080 --> 00:17:45,080
Conclusion
374
00:17:45,080 --> 00:17:47,080
One shared answer
375
00:17:47,080 --> 00:17:51,960
Dynamics 365 knowledge management gives your support team a single place for answers everyone
376
00:17:51,960 --> 00:17:54,120
can trust while they help customers.
377
00:17:54,120 --> 00:17:58,520
Subscribe on your favorite podcast platform for more Microsoft knowledge nuggets with me,
378
00:17:58,520 --> 00:18:00,440
Merco Peters from M365.
379
00:18:00,440 --> 00:18:05,800
FM share this episode with someone building a Dynamics 365 support team, then watch the next
380
00:18:05,800 --> 00:18:08,400
guide to see how the connected platform fits together.
