A customer starts a website chat because an order has not arrived. They explain the problem, provide the order number, and answer several questions. Later, they call the company—and the person on the phone asks them to explain everything again. For the customer, this makes little sense. They did not start a new problem. They simply changed the way they contacted the company. In this episode of Microsoft Knowledge Nuggets on M365 FM, Mirko Peters explains Microsoft Dynamics 365 Omnichannel in plain English and shows how organizations can connect customer conversations across chat, voice, SMS, social messaging, and other service channels. We explore the unified agent workspace, customer identification, queues, Unified Routing, skills-based routing, agent presence, capacity, transfers, consultations, knowledge articles, quick replies, Copilot, Smart Assist, sentiment analysis, customer history, cases, transcripts, and supervisor analytics. The central idea is simple: customers can enter through many different doors, while agents work from one connected customer service desk.
WHY SEPARATE CUSTOMER SERVICE CHANNELS CREATE PROBLEMS
Traditional customer service often treats every communication channel as a separate system. Website chats appear in one application. Emails arrive in a shared mailbox. Calls are handled through another platform. Social messages may even be managed by a completely different department. Each system may work perfectly well individually, but the customer's story becomes fragmented. An agent answering the phone may not know that the customer already spent twenty minutes chatting with another employee earlier that day. The result is repetition, longer handling times, unnecessary searching, and frustrated customers. Dynamics 365 Omnichannel attempts to connect those pieces into a more consistent service experience.
WHAT IS DYNAMICS 365 OMNICHANNEL?
Think of Dynamics 365 Omnichannel as an office building with several front doors but one reception desk. Customers can enter through different communication channels. One person might use website chat. Another calls. Another sends a text message. Another contacts the organization through a supported social messaging channel. Behind those different entry points, Dynamics 365 provides a common customer service environment. The channel still matters because a live telephone call behaves differently from an asynchronous text conversation. But agents do not necessarily need completely separate working environments for every channel.
THE UNIFIED AGENT WORKSPACE
The agent workspace is where customer conversations come together. Instead of switching continually between a chat application, telephone system, CRM, knowledge base, and customer records, agents can work with conversations alongside relevant Dynamics 365 information. Each active piece of work can appear as a session or conversation. An agent might handle one customer chat and later move to another session without losing the original context. The workspace can also provide access to customer details, previous cases, activities, knowledge, notes, and other service information. This changes the agent's starting point from: "Can you explain everything again?" to: "I can see your previous interaction. Let's continue from there."
IDENTIFYING THE CUSTOMER
Connected customer history depends on knowing who the customer is. Sometimes Dynamics 365 already knows. For example, a customer may begin a conversation while authenticated through a connected customer experience. In other situations, somebody starts as an unknown website visitor. The agent can then request information such as an email address or order number and search for an existing contact. Once the conversation is associated with the correct customer or case, the transcript, notes, activities, and related service work can contribute to that customer's history. Customer identification is therefore an important part of making omnichannel actually feel connected.
CASES KEEP CUSTOMER ISSUES TOGETHER
Some questions can be solved during a single conversation. Others require follow-up. A case provides a structured Dynamics 365 record for an issue that needs to be tracked until resolution. Imagine a customer contacts support about a missing delivery. The initial chat does not solve the problem because another department needs to investigate. The agent creates or associates a case. When another employee later works on the issue, they can open that case and review the information already collected. The customer problem now has a persistent home instead of existing only inside one temporary conversation.
ROUTING: GETTING CUSTOMERS TO THE RIGHT TEAM
A unified workspace is useful only when customer requests reach appropriate employees. This is where routing becomes important. Dynamics 365 can place incoming work into queues representing different areas of responsibility. An organization might have queues for: Billing, deliveries, technical support, sales, or another service function. Routing rules can use information collected from the customer to determine where the conversation belongs. A billing question can go toward billing. A delivery problem can go toward the delivery team. The customer does not need to understand the queue architecture. They simply describe what they need.
SKILLS-BASED ROUTING
Being available does not automatically make somebody the correct agent. A customer may need assistance in German. Another customer may require an employee who understands a particular product. Another request may require specialized account knowledge. Dynamics 365 can use skills to describe what agents can handle and match those capabilities with customer requirements. Instead of routing work only according to who happens to be free, the system can consider whether the employee is actually suitable for the conversation. This can reduce transfers and improve the chance that the first agent receiving the request can help.
PRESENCE AND AGENT CAPACITY
The correct agent also needs to be available. Presence indicates whether an employee is available, busy, away, offline, or in another configured state. Capacity helps represent how much work that employee can handle. A voice call may require almost complete attention. Messaging conversations can behave differently because customers frequently pause between messages. An organization can therefore define workload rules appropriate to its service model. This helps avoid situations where one qualified employee receives conversation after conversation while another suitable agent remains available.
TRANSFERS VS CONSULTATIONS
Sometimes a conversation reaches the wrong team. An agent discovers that a customer actually needs billing rather than technical support. In that situation, the conversation can be transferred to another appropriate queue or person. But not every specialist question requires transferring the customer. A consultation allows the original agent to involve another employee for assistance while remaining responsible for the customer conversation. Instead of saying: "I'll transfer you." the agent can effectively say: "I'm checking this with our specialist." That distinction can reduce unnecessary handoffs and provide customers with a more continuous service experience.
KNOWLEDGE ARTICLES AND QUICK REPLIES
#Agents answer many similar questions every day. How do I reset my password? How do I return an item? Where can I download an invoice? What does this error message mean? Knowledge search allows employees to find approved information while the customer conversation remains open. Agents can use the article to guide their answer and, where appropriate, provide relevant information to the customer. Quick replies provide another productivity tool. Frequently used messages can be prepared in advance so employees do not need to type identical responses repeatedly. The agent still needs to review the response and make sure it actually fits the customer's situation.
COPILOT AND SMART ASSIST
AI capabilities can provide additional assistance where the organization has enabled them. Smart Assist can surface potentially useful knowledge articles, related information, or guidance. Copilot can help summarize longer conversations and, depending on the configured capabilities, assist with suggested responses. Imagine a customer spending ten minutes interacting before reaching a human agent. Instead of forcing the agent to read the complete conversation before understanding the problem, a summary can provide a faster overview of what the customer requested and what has already happened. These capabilities support the agent. They do not remove the need for review. The employee remains responsible for making sure information provided to the customer is appropriate and accurate.
VOICE, TRANSCRIPTION AND SENTIMENT
Voice scenarios can also include additional assistance. When supported voice capabilities are configured, live transcription can convert spoken conversation into text. This can help agents review product numbers, customer concerns, or commitments made during a call. Sentiment signals can provide another indicator. If a conversation appears increasingly negative, the agent may decide to slow down, clarify the problem, or acknowledge the customer's frustration more explicitly. But sentiment should not be treated as a definitive interpretation of someone's emotions. Sarcasm, language differences, communication style, and context can all affect the signal. Sentiment is therefore best treated as another piece of information—not a verdict about the customer.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.
