# Omnichannel Engagement and Self-Service Capabilities

> Chapter 9 of the Courseiva MB-910 curriculum — https://courseiva.com/learn/mb-910/omnichannel-and-self-service-capabilities

**Official objective:** 4.3 — Describe omnichannel engagement (chat, SMS, social media, voice) and self-service portals including a knowledge base and Power Virtual Agents (Copilot Studio).

## Introduction

Omnichannel Engagement and Self-Service Capabilities. This is the set of tools that lets customers reach a company through whatever method they prefer — phone, text, chat, social media — and still get a seamless, personalised answer. For the MB-910 exam, you need to understand how Dynamics 365 brings all those channels together and how self-service options like knowledge bases and chatbots reduce the workload on human agents.

## The Hotel Concierge Analogy

A hotel concierge is the professional responsible for managing every way a guest can make a request or get help during their stay. 

Imagine you are staying at a large hotel. You could call the front desk from your room phone to ask for extra towels. You could send a text message to the hotel's number saying your air conditioning is too cold. You could walk down to the lobby and talk to a person at the concierge desk in person. You could open the hotel's mobile app and start a live chat to ask about restaurant reservations. You could even tweet at the hotel's official account to complain about a noisy neighbour. 

Now, behind the scenes, the hotel does not have five different teams handling each of those channels separately. Instead, there is a single, centralised digital system that collects every message from the phone, the SMS, the in-person conversation, the app chat, and the social media post. It puts them all into one queue. The concierge sees everything in one screen. If you start by sending a text and then later call, the concierge already knows what you asked about. They do not make you repeat yourself. 

This is exactly what Omnichannel Engagement does for a company. It pulls together phone calls, live chat, SMS messages, social media comments, and voice conversations into one place so a customer service agent can see the whole history and give a consistent, seamless experience. The guest — the customer — does not care which channel they used. They just want their problem solved. The concierge system makes that possible.

## Core explanation

To understand Omnichannel Engagement, start by thinking about how customer service used to work. Not long ago, if you wanted help from a company, you had one choice: pick up the phone and call. You would wait on hold, speak to one person, and if you had to call back later, you would start all over again with a new person who knew nothing about your previous conversation. That system is called multichannel — meaning the company offered multiple channels (phone, email, maybe a web form) but each channel operated in its own separate silo. Information did not flow between them. 

Omnichannel Engagement is the opposite. The prefix 'omni-' means 'all' or 'every'. So omnichannel means 'all channels together'. In Dynamics 365, Omnichannel for Customer Service is a feature that pulls phone calls, live chat, SMS (text messages), social media messages (like from Facebook, Twitter, or WhatsApp), and voice conversations into a single, unified workspace. A customer service agent opens one screen — called the Omnichannel Agent Dashboard — and sees every conversation they are handling, regardless of which channel the customer used. When a customer switches from chat to phone, the agent can see the chat history. The customer never has to repeat their name, their order number, or their problem. This continuity is the core value of omnichannel. 

Now, how does this actually work? Under the surface, Dynamics 365 uses something called a 'unified routing engine'. When a message comes in from any channel, the system looks at the content, identifies the customer (if they are already in the system), determines the urgency, and then sends it to the right agent or queue. For example, a high-priority message from a VIP customer might be routed directly to a senior agent, while a simple billing question can go to a general queue. This automatic distribution is called 'work distribution' or 'routing'. 

Let us break down each channel mentioned in the exam objective: 

- Chat: A real-time text conversation that happens on a website or inside a mobile app. The customer types a message, and an agent responds live, often with the help of pre-written response snippets called 'quick replies'. 

- SMS (Short Message Service): Standard text messages sent from a mobile phone. Dynamics 365 can integrate with SMS providers so that agents can send and receive texts from the same dashboard they use for chat. 

- Social Media: Messages and comments from platforms like Facebook Messenger, Twitter (X), Instagram, and WhatsApp. Dynamics 365 can monitor a company's social media pages and turn public comments or private messages into cases that agents can respond to. 

- Voice: Phone calls. In Omnichannel for Customer Service, voice calls can be managed through the same dashboard. When a call comes in, the agent sees a 'screen pop' with the customer's details before they even answer. Calls can also be recorded and analysed for quality. 

Now let us talk about Self-Service. The idea is simple: many customers prefer to solve their own problems without talking to a human. Self-service capabilities allow them to do that. Dynamics 365 offers two main self-service tools: a Knowledge Base and Power Virtual Agents (which is now part of Microsoft Copilot Studio). 

A Knowledge Base is a searchable library of articles, guides, FAQs, and troubleshooting steps. It is like a detailed help centre on a website. Customers can type a question into a search bar, and the system returns relevant articles. Agents can also use the knowledge base internally to find answers quickly while helping a customer. The content inside a knowledge base is managed by authors who write and update articles. Good knowledge bases reduce the number of incoming support requests because customers find answers on their own. 

Power Virtual Agents (renamed Copilot Studio) is a tool for building chatbots without writing code. A chatbot is a computer program that simulates a conversation with a human. With Copilot Studio, you design conversation flows using a visual drag-and-drop interface. You define topics — like 'Reset my password' or 'Check order status' — and the bot guides the customer through a series of questions and answers. If the bot cannot solve the problem, it can hand the conversation off to a human agent, along with the full chat transcript. This is called 'escalation'. 

The combination of a knowledge base and a chatbot is powerful. The chatbot can answer common questions by pulling answers from the knowledge base. If the chatbot cannot help, it passes the conversation to a human agent who already has context from the chatbot conversation. This reduces wait times and agent workload. 

Why does all of this exist? Before omnichannel and self-service, companies ran separate systems: a phone system, an email system, a separate chat tool, and a different help centre website. Agents had to switch between multiple screens. Customers got frustrated repeating themselves. Companies had no central view of customer interactions. Omnichannel and self-service solve those problems by creating a single platform where all customer interactions live in one place, and where customers can help themselves when they want to.

## Real-world context

Imagine you are a customer service manager at a中型 online retailer called 'ShopEasy'. Your company sells home goods. Customers contact you through many ways: they call your support line, they send emails, they use the live chat on your website, they send DMs on Instagram, and they text a short code number. Previously, you had separate teams and separate software for each channel. Your call centre used one system, your chat team used another, and your social media person used a third. Customers repeatedly complained that they had to explain their issue from scratch every time they switched channels. 

You decide to implement Dynamics 365 Omnichannel for Customer Service. Here is what happens step by step: 

First, you configure the channels. You connect your phone system (using a provider like Twilio or Azure Communication Services) to Dynamics 365. You set up a live chat widget on your website using a simple snippet of code. You link your Facebook and Instagram business pages so that incoming DMs appear inside Dynamics 365. You activate an SMS number through a third-party messaging service. Now, every single incoming message from any of these channels lands in one unified queue inside the Omnichannel Agent Dashboard. 

Second, you set up routing rules. You decide that any message containing words like 'refund' or 'cancel' should go to the billing team queue. Messages with 'damaged' or 'broken' go to the returns team. Messages from customers who have spent more than £500 in the last year get tagged as 'VIP' and go to a dedicated senior agent. The routing engine does this automatically based on keywords and customer data. 

Third, your agents are trained. They log into Dynamics 365 and see a dashboard that shows all their active conversations. For each conversation, the agent can see the customer's name, their past orders, previous support tickets, and any notes from other agents. If a customer sends a chat message, then calls five minutes later, the agent who answers the phone sees the chat transcript immediately. The agent does not need to ask 'What is your order number?' because it is already on the screen. 

Fourth, you build a self-service portal. You create a knowledge base with 200 articles covering topics like 'How to track your order', 'Return policy', and 'Troubleshooting a faulty blender'. You install it on your website as a help centre. Customers can search and read articles without logging in. 

Fifth, you use Copilot Studio to build a chatbot. You design a conversation flow for the top five reasons customers contact you: order status, returns, billing, product information, and shipping delays. The chatbot asks questions, pulls answers from the knowledge base, and resolves about 40 percent of conversations without needing a human. When the chatbot cannot help, it creates a new case in Dynamics 365 and transfers the conversation to an agent, including a summary of what the customer already said. 

The result? Your average response time drops from 15 minutes to under 2 minutes. Customer satisfaction scores improve by 20 percent. Your agents handle more conversations per hour because they are not wasting time switching screens or asking for basic information. Your company saves money because fewer customers need to speak to a human. 

In a real deployment, an IT professional would be responsible for setting up the channel integrations (connecting phone numbers, social media accounts, SMS providers), configuring the routing rules, building the knowledge base structure, creating the chatbot in Copilot Studio, and training the agents on how to use the new dashboard. The IT professional would also monitor reports and dashboards to see how many conversations are happening per channel, how many are resolved by the chatbot, and how long customers are waiting.

## Exam focus

The MB-910 exam tests your understanding of what each channel is, how omnichannel differs from multichannel, and the purpose of self-service tools. You will not be asked to configure anything. This is a fundamentals exam, so you need to recognise definitions and benefits. 

Here are the exact concepts the exam loves to test: 

- The definition of Omnichannel Engagement: they will ask you to identify that omnichannel means all channels are unified in one system, as opposed to multichannel where channels are separate. A typical question might say 'A company uses phone, email, and chat but each system is managed separately. Is this omnichannel or multichannel?' The answer is multichannel. The trap is that the word 'multi' sounds like 'many' so beginners think it means the same thing. It does not. 'Multi' means separate silos. 'Omni' means unified. 

- The channels: you need to know which channels are supported. Chat, SMS, social media, and voice. They might list a channel that is NOT supported (like carrier pigeon or fax) and ask which one is not included. 

- Knowledge Base: they will ask what a knowledge base is used for. The correct answer is 'to store and search articles that help customers and agents solve problems'. A trap is describing it as a tool for building chatbots — that is Copilot Studio, not the knowledge base. 

- Copilot Studio (Power Virtual Agents): they will ask what this tool is used for. The answer: building chatbots without code. They might also ask what happens when a chatbot cannot resolve an issue — the correct answer is 'escalation to a human agent'. 

- Self-service benefits: they love to ask why a company would implement self-service. Correct reasons include: reducing agent workload, lowering support costs, providing 24/7 availability, and improving customer satisfaction by letting customers find answers quickly. A trap is suggesting that self-service eliminates the need for human agents entirely — it does not; it reduces but does not eliminate. 

- Unified routing: they may ask what happens when a message comes in from a customer. The system uses routing rules to send it to the right agent or queue. A common trap is thinking that all messages go to the same person. 

- Customer context: they will test that omnichannel preserves the history of interactions across channels. For example, a question might describe a customer who starts with chat and then calls, and ask what the agent sees. The correct answer: the agent sees the chat history. 

- The Agent Dashboard: they might refer to the 'Omnichannel Agent Dashboard' and ask what it shows. Answer: all active conversations from all channels in one view. 

- Exam trap pattern: the exam often gives a scenario where a customer uses multiple channels but the company has no way to connect the interactions. The question asks: 'What is this called?' The answer is multichannel, not omnichannel. They also love to ask: 'Which tool would you use to build a FAQ chatbot?' The answer is either Power Virtual Agents or Copilot Studio (both names may appear, but they are the same product). 

Key definitions to memorise: 
- Omnichannel: unified customer experience across all channels. 
- Multichannel: multiple channels managed separately. 
- Knowledge Base: searchable library of articles. 
- Copilot Studio / Power Virtual Agents: no-code chatbot builder. 
- Routing: automatically sending conversations to the right agent or queue. 
- Escalation: transferring a conversation from a chatbot to a human agent. 
- Agent Dashboard: single view of all customer conversations. 
- Self-service: customers solving problems without human help.

## Step by step

1. **Customer Initiates Contact** — A customer sends a message through any channel — for example, they start a live chat on the company website, send a direct message on Instagram, or text an SMS number. This message enters the Dynamics 365 Omnichannel system.
2. **Message is Routed by the Engine** — The unified routing engine analyses the incoming message. It checks the customer's identity (if they are known), looks for keywords like 'refund' or 'order status', and applies the rules set by the administrator. This determines which queue or agent the message should go to.
3. **Agent Receives the Conversation in the Dashboard** — The assigned agent sees the new conversation appear in their Omnichannel Agent Dashboard. The dashboard shows the channel (chat, SMS, social, or voice), the customer's name, and any previous interaction history. The agent can accept the conversation with a single click.
4. **Agent Resolves or Escalates (If Needed)** — The agent uses the knowledge base to find articles, or uses pre-defined quick replies to answer the customer quickly. If the issue is complex, the agent can transfer the conversation to another agent or team, keeping the full history intact.
5. **Conversation is Closed and Logged** — Once the issue is resolved, the agent closes the conversation. Dynamics 365 saves the entire transcript, along with any notes, into the customer's record. This history is available for future interactions, regardless of which channel the customer uses next.
6. **Self-Service Alternative: Customer Uses Bot or Knowledge Base First** — Before contacting an agent, the customer might interact with a Copilot Studio chatbot or search the knowledge base. The chatbot can answer simple questions using articles. If the chatbot cannot help, it creates a new case and transfers the conversation to a human agent at step 3.

## Comparisons

### Omnichannel vs Multichannel

**Omnichannel:**
- All channels are connected into one unified system
- Customer history and context are preserved across channels
- Agents see all conversations in a single dashboard

**Multichannel:**
- Each channel operates in its own separate system or silo
- Customer must repeat information when switching channels
- Agents switch between different screens for each channel

### Knowledge Base vs Copilot Studio (Chatbot)

**Knowledge Base:**
- A library of written articles and guides
- Customers and agents search for answers manually
- Content is static and updated by authors

**Copilot Studio (Chatbot):**
- A conversational program that simulates a human
- Customers answer questions through a back-and-forth dialogue
- Conversation flows are designed visually and can escalate to agents

### Self-Service vs Agent-Assisted Service

**Self-Service:**
- Customer solves problem without human interaction
- Available 24/7 but limited to predefined answers
- Reduces cost and agent workload

**Agent-Assisted Service:**
- Customer interacts with a human agent
- Available during business hours or based on agent availability
- Handles complex, nuanced, or emotional issues

## Diagram

_This diagram shows how a customer can reach a company through four channels (chat, SMS, social media, voice), which all feed into a unified routing engine and then to the agent dashboard. The customer can also interact directly with the knowledge base or the chatbot for self-service._

```mermaid
flowchart TD
    A[Customer] -->|Chat| B[Live Chat Widget]
    A -->|SMS| C[SMS Provider]
    A -->|Social Media DM| D[Facebook/Instagram API]
    A -->|Phone Call| E[Voice System]
    B --> F[Unified Routing Engine]
    C --> F
    D --> F
    E --> F
    F -->|Routes to Queue| G[Agent Dashboard]
    A -->|Searches| H[Knowledge Base]
    A -->|Interacts with| I[Copilot Studio Chatbot]
    I -->|Escalates| G
    H --> I
```

## Common misconceptions

- **Misconception:** Omnichannel and multichannel mean the same thing. They both just mean a company has multiple ways to contact them. **Reality:** Omnichannel means all channels are connected and share data, so the customer gets a seamless experience. Multichannel means the channels exist but operate in separate silos, so the customer has to repeat themselves. (The words sound similar, and many study materials use them interchangeably in casual conversation. Beginners do not realise the technical distinction matters for the exam.)
- **Misconception:** A knowledge base is the same as a chatbot. **Reality:** A knowledge base is a library of articles. A chatbot is a conversational program. They often work together — the chatbot pulls answers from the knowledge base — but they are separate components. (When customers see a search bar and a chat window on the same help page, they think it is one feature. In reality, the knowledge base provides the search results, and the chatbot provides the conversation.)
- **Misconception:** Self-service means customers never need to talk to a human agent. **Reality:** Self-service handles common issues, but complex problems still require human agents. Self-service reduces the volume of conversations, but it does not eliminate the need for people. (The phrase 'self-service' sounds like 'do it yourself' which implies total independence. Beginners assume the goal is to automate everything, but real businesses know some issues need human judgement.)
- **Misconception:** Omnichannel only works for chat and SMS, not for phone calls. **Reality:** Omnichannel for Customer Service in Dynamics 365 includes voice (phone calls) as a first-class channel. Phone calls can be integrated, recorded, and handled from the same agent dashboard. (People think of omnichannel as a 'digital' concept and forget that voice is a channel too. The exam explicitly lists voice alongside chat, SMS, and social media.)
- **Misconception:** Copilot Studio (Power Virtual Agents) is an AI that thinks for itself and can handle any question automatically. **Reality:** Copilot Studio is a tool for building rule-based chatbot flows. The chatbot only handles topics that someone has explicitly designed. It does not think independently or learn on its own without additional AI services. (The term 'AI' is used loosely in marketing. Beginners assume the chatbot is as smart as ChatGPT and can magically answer anything. In reality, it follows pre-written scripts.)
- **Misconception:** If a company has a website FAQ page, that is the same as having a knowledge base in Dynamics 365. **Reality:** A static FAQ page is a list of questions and answers. A knowledge base in Dynamics 365 is a searchable, categorised, and continuously updated repository that both customers and agents can use. It also integrates with routing and the chatbot. (The word 'knowledge base' sounds fancy for 'FAQ page'. Beginners think they are interchangeable, but the Dynamics 365 knowledge base has features like article versioning, permissions, and analytics that a simple FAQ page does not.)

## Key takeaways

- Omnichannel unifies all customer communication channels (chat, SMS, social media, voice) into a single agent dashboard so that agents see the full conversation history regardless of how the customer contacts the company.
- A knowledge base is a searchable library of articles that helps customers find answers themselves and helps agents respond faster with accurate information.
- Copilot Studio (formerly Power Virtual Agents) is a no-code tool for building chatbots that can handle common questions and escalate complex issues to human agents.
- The key difference between multichannel and omnichannel is that multichannel operates separate systems for each channel, while omnichannel connects them so the customer never has to repeat themselves.
- Self-service capabilities reduce agent workload, lower support costs, and provide 24/7 availability, but they do not completely replace human agents.
- In Dynamics 365 Omnichannel for Customer Service, incoming messages are automatically routed to the right agent or queue based on rules using keywords, customer data, or priority levels.

## FAQ

**What is the difference between omnichannel and multichannel in Dynamics 365?**

Multichannel means a company offers multiple ways to contact them (phone, email, chat) but each channel is managed separately, so information does not flow between them. Omnichannel means all channels are connected in one system, so agents see the full history regardless of how the customer contacts them.

**Do I need to know how to set up omnichannel in Dynamics 365 for the MB-910 exam?**

No. The exam only tests your understanding of what omnichannel is, what channels are supported, and why a company would use it. You do not need to know configuration steps.

**What is a knowledge base in Dynamics 365?**

A knowledge base is a searchable collection of articles that contain solutions, FAQs, and guides. Both customers and customer service agents can use it to find answers without reinventing the wheel.

**What is Power Virtual Agents / Copilot Studio used for?**

It is used to build chatbots without writing code. You create conversation flows by dragging and dropping topics. The chatbot can answer common questions and escalate to a human agent if it cannot resolve the issue.

**Does omnichannel include phone calls?**

Yes. Voice is one of the channels supported in Omnichannel for Customer Service. Phone calls can be managed from the same agent dashboard as chat, SMS, and social media.

**Will the exam ask me about specific social media platforms?**

Not by name. The exam will refer to 'social media' as a general channel. You just need to know that social media messages (like from Facebook or Twitter) can be handled in the omnichannel system.

**What happens if a customer contacts Support through chat and then later calls on the phone?**

With omnichannel, the agent who answers the phone will see the chat transcript and all prior interaction history. The customer does not need to repeat their information.

## Check your understanding

1. **A company uses separate systems for phone calls, email, and live chat. Customers have to repeat their issue every time they switch channels. Is this omnichannel or multichannel?**

   Answer: This is multichannel because the channels are not connected; they operate in separate silos.

2. **Which Dynamics 365 tool would you use to build a chatbot that can answer common customer questions without writing code?**

   Answer: Copilot Studio (formerly Power Virtual Agents).

3. **What is the main purpose of a knowledge base in Dynamics 365?**

   Answer: To store searchable articles that help customers and agents find answers to common questions.

4. **When a customer starts a conversation via live chat and then calls the support line, what does the agent see when they answer the phone in an omnichannel system?**

   Answer: The agent sees the chat transcript and the customer's interaction history from the previous channel.

5. **What happens if a Copilot Studio chatbot cannot resolve a customer's issue?**

   Answer: The chatbot escalates the conversation to a human agent, including the full transcript of the chat.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/mb-910/omnichannel-and-self-service-capabilities