How do businesses stop losing track of customer complaints, support emails, and phone messages without paper chaos or missed follow-ups? Dynamics 365 Customer Service solves this by giving companies a single, organised system to manage every customer interaction, from a broken product to a billing question, so that nothing slips through the cracks. For the MB-910 exam, understanding this core problem and its solution—case management via the service hub—is essential because it is the foundation of most customer service scenarios you will be tested on.
Jump to a section
A simple way to picture Introduction to Dynamics 365 Customer Service
A hotel concierge desk is the central hub for guest requests. Every hotel guest, just like every customer, has needs, problems, or questions that require a structured response. The concierge's notepad is the case management system. Each request gets written down, assigned a unique number (the case ID), and recorded with the guest's room number (customer details), the time of the request (timestamp), and a description of the issue, such as 'lost room key' or 'noisy air conditioner'.
The service hub is the concierge's physical desk, the centralised workspace where they manage all these notes, check their status, and coordinate with other hotel staff like housekeeping or maintenance. When a guest requests a late checkout, the concierge opens a new 'case', logs the request, and routes it to the front desk team. They can track whether the request is 'open' (waiting for action), 'in progress' (housekeeping is cleaning a late-checkout room), or 'resolved' (the guest has extended their stay). The hotel manager uses the same desk to view a dashboard of all outstanding requests, spotting patterns like too many complaints about the breakfast buffet. This single, organised system replaces frantic Post-It notes, lost phone messages, and confused guests walking from department to department. Dynamics 365 Customer Service operates exactly this way: it is the digital concierge desk for any company, ensuring every customer issue is tracked, prioritised, and never forgotten.
Dynamics 365 Customer Service is a software application from Microsoft that helps businesses handle customer support requests in a structured, efficient way. Before systems like this existed, companies relied on shared email inboxes, spreadsheets, or paper notes to track customer problems. This was chaotic. Emails got buried, phone call details were lost on sticky notes, and customers often had to repeat their entire story to every new person they spoke to. Dynamics 365 Customer Service solves this mess by providing a central database, often called a Common Data Service, where every single customer interaction becomes a digital record called a 'case'.
A 'case' is the core building block of the system. Think of it as a digital folder for one specific customer issue. When a customer emails support saying, 'My laptop won't turn on,' a support agent creates a case. That case automatically captures the customer's name, contact details, the date and time the issue was reported, a full description of the problem, and a unique case number. Every email reply, every phone call note, and every internal discussion about that laptop gets attached to this single digital folder. This means anyone in the company can open the case ten minutes or ten days later and see exactly what has happened so far. The customer never has to repeat themselves.
The 'Service Hub' is the main interface or dashboard where customer service agents do their work. It is a web-based application, meaning it runs inside a web browser like Chrome or Edge, so agents can access it from any computer with an internet connection. The Service Hub shows agents a queue of all the cases assigned to them, prioritised by urgency or age. It includes tools for quickly looking up customer records, searching for knowledge base articles (pre-written answers to common questions), and logging activities. The Service Hub replaced the old 'Service Management' interface in older versions of Dynamics 365, making the experience cleaner and more modern for users.
Case management involves several key processes that work together. First is case creation: when a customer contacts the company, a new case record is born. This can happen automatically when an email arrives in a monitored inbox, or manually when an agent gets a phone call. Second is case routing: the system can automatically assign cases to the right team or agent based on rules. For example, a case about a billing issue can be sent directly to the accounts team, while a technical question goes to the support engineers. This saves managers time from manually distributing work. Third is case resolution: when the agent has solved the problem, they mark the case as 'Resolved'. At this point, the system may send a satisfaction survey to the customer, asking them to rate the service. Finally, a resolved case can be 'Closed' permanently after a set period, often after the customer confirms they are happy.
Why does all of this exist? The business value is enormous. Instead of losing customer requests, companies get visibility into their support workload. Managers can see reports showing how many cases were opened today, how long it takes to resolve common issues, and which agents are handling the most work. This allows businesses to spot training needs, improve their products (if many people complain about the same feature), and ultimately keep customers happier. For the MB-910 exam, you need to know that Dynamics 365 Customer Service is not just a digital notebook—it is a full system for managing the lifecycle of a customer issue from start to finish, with the Service Hub as the agent's workspace and case management as the engine that tracks everything.
Customer contacts support via email
An email arrives at a monitored mailbox (e.g., support@company.com). The system identifies it as a new request and automatically creates a new case record. The email subject becomes the case title, and the email body becomes the description. The customer's email address is matched to an existing or new contact record.
Case is created and assigned to a queue
The new case appears in a shared queue based on predefined routing rules. For example, cases with the word 'billing' go to the 'Billing Queue.' An agent or an automatic assignment rule then picks the case from the queue and assigns it to an individual agent or team.
Agent opens the case in the Service Hub
The assigned agent logs into the Service Hub and sees the case in their personal queue. They open it to read the full conversation history, customer details, and any attachments. This is their central workspace for all future actions on this issue.
Agent searches the knowledge base and logs activities
The agent uses the built-in knowledge search to find a relevant article. They send the article link to the customer via email. They also log a phone call activity if they called the customer, recording notes directly into the case timeline.
Agent resolves and closes the case
Once the customer confirms the issue is solved, the agent changes the case status to 'Resolved.' After a configurable waiting period (e.g., 7 days), the system automatically moves the case to 'Closed.' The case record remains in the database for reporting and auditing purposes.
An IT professional, let's call her Priya, works as a Customer Service Manager for a medium-sized company that sells ergonomic office chairs. Her company receives about 200 support requests every day via email, phone calls, and a chat widget on their website. Before Dynamics 365, they had three different people managing three different inboxes, and customers frequently complained about being transferred multiple times. Priya's boss asked her to implement Dynamics 365 Customer Service to fix this chaos.
Priya starts by configuring the system. She sets up an email mailbox that automatically creates a new case whenever a customer sends an email to support@chairs.com. Each email's subject line becomes the case title, and the body becomes the description. She then creates routing rules: cases containing the word 'delivery' are sent to the logistics team, cases with 'broken' are flagged as 'high priority' and sent to the technical support squad, and cases with 'invoice' go to the billing department. Agents log into the Service Hub each morning and see a personalised queue showing only the cases assigned to them.
One afternoon, a customer named Raj calls to report that the armrest on his new chair snapped off. The agent, Maria, answers the phone and quickly opens the Service Hub. She searches for Raj's name, finds his existing customer record, and creates a new case. She types 'Broken armrest on Model X' as the title and logs the phone call as an activity attached to the case. Since her routing rule recognised 'broken' as high priority, the case appears at the top of the queue for the technical team. Within an hour, a technician reviews the case, sees that the same part has failed three times this month, and decides to escalate the issue to the product quality team. He also sends Raj a pre-written knowledge base article about how to remove the broken armrest and a link to request a free replacement part.
Priya uses the built-in dashboards in the Service Hub to monitor team performance. She sees a chart showing that 'armrest' issues are taking an average of 48 hours to resolve, much longer than other problems. She schedules a training session for the team on identifying and fast-tracking part replacements. She also exports a monthly report showing the top five reasons for customer contacts, which she presents at the company's product development meeting. Because of the system, the company reduces its average case resolution time from four days to 24 hours, and customer satisfaction scores increase by 20%. Priya's IT role in this scenario involved configuring the email integration, setting up the routing rules, training the agents on using the Service Hub, and customising the dashboards to show the data her boss needs. She did not write any code; she simply used the point-and-click customisation tools built into Dynamics 365.
The MB-910 exam tests your understanding of 'Introduction to Dynamics 365 Customer Service' by asking questions that require you to recognise core terminology and basic workflows. You will not be asked to configure the system or write code. The exam is multiple-choice, and many questions present a short scenario followed by a single correct answer among four options. The traps are designed to catch candidates who confuse similar-sounding features.
Here are the concepts the exam loves to test:
A case is the central record in Dynamics 365 Customer Service, representing a single customer issue from start to finish.
The Service Hub is the dedicated workspace where agents manage their cases, access knowledge articles, and view dashboards.
Cases can be created manually by an agent or automatically from incoming emails using email-to-case functionality.
The standard case lifecycle includes Active, Resolved, and Closed stages, and a resolved case can be reactivated if needed.
Knowledge articles are pre-written solutions that agents can search and attach directly to a case to speed up resolution.
Routing rules automatically assign incoming cases to the correct team or agent based on keywords, category, or customer attributes.
Dynamics 365 Customer Service replaces ad-hoc tools like spreadsheets and shared inboxes, providing audit trails and performance analytics.
The system integrates with other Microsoft 365 tools, so emails from Outlook automatically link to existing cases or create new ones.
These come up on the exam all the time. Here's how to tell them apart.
Case
Represents an entire customer issue from start to finish.
Has its own unique ID, status, and priority.
Can contain multiple activities linked to it.
Activity
A single interaction like a phone call, email, or note.
Logged on a case record, not a standalone issue.
Does not have a resolution status; it is an action, not a problem.
Service Hub
The older interface for agents, though still widely used.
Accessible via a web browser on any device.
Designed for general case management tasks.
Customer Service Workspace
A newer, more modern interface built on the same platform.
Integrates more deeply with Microsoft Teams and Outlook.
Offers a unified view of cases, conversations, and knowledge all in one screen.
Resolved Case
Agent has provided a solution to the customer.
Customer may still respond or re-open the case.
The case is still considered active for reporting purposes.
Closed Case
No further action is expected from either side.
The case is archived and can only be re-opened manually.
Used for long-term storage and historical analysis.
Queue
A shared list of cases waiting for any team member to pick up.
Managed by a supervisor who can reassign items.
Useful for first-come-first-served work distribution.
Personal Queue
A list of cases specifically assigned to one agent.
Only visible to that agent and their supervisor.
Allows an agent to focus on their own workload without distraction.
Mistake
Dynamics 365 Customer Service can only handle phone calls and nothing else.
Correct
It handles emails, phone calls, web chats, social media messages, and even automated messages from Internet of Things (IoT) devices.
Beginners associate 'customer service' with call centres, so they forget the system is designed to manage all types of communication channels.
Mistake
The Service Hub and the Power Platform are completely separate products that do not integrate.
Correct
The Service Hub is built on the Power Platform (Power Apps, Power Automate, Power BI), so data flows seamlessly between them.
Novices see different product names and assume they are unrelated, missing the fact that Dynamics 365 is part of a larger Microsoft ecosystem.
Mistake
Once a case is marked 'Resolved,' you cannot re-open it.
Correct
A resolved case can be reactivated if the customer writes back with the same issue within a specific timeframe, depending on the system configuration.
The term 'Resolved' sounds final, leading people to think it is irreversible, but in practice, a reactivation feature exists to prevent creating duplicate cases.
Mistake
Creating a case manually is the only way to log a customer issue.
Correct
Cases can also be created automatically from incoming emails, or from customer interactions on a web portal, using automation rules.
Beginners think the system is entirely manual because they focus on the agent's role, ignoring the powerful automation capabilities of the Power Platform.
Mistake
Knowledge articles are only for customers, not for agents.
Correct
Knowledge articles are primarily used by agents to find quick answers while working on a case, though they can be published on a customer portal for self-service.
The word 'knowledge base' sounds like a public wiki, so novices forget it is an internal agent tool as well.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A contact is a record for a person (customer), storing their name, phone number, and address. A case is a record for a specific problem or request, linked to a contact. Think of it like this: the contact is the person, the case is the ticket they opened.
The Service Hub is the primary interface, but Dynamics 365 Customer Service also works within other apps like the Customer Service workspace app or even custom Power Apps. For the MB-910 exam, always associate Customer Service work with the Service Hub.
You configure a mailbox in Dynamics 365 to monitor a specific email address (like support@company.com). Then you set up a rule that says 'when an email arrives, create a new case and attach the email as an activity.' This is called the Email-to-Case feature.
No, a closed case is not deleted. It remains in the system as a historical record. You can still view it, run reports on it, or reactivate it if needed. Deleting is a separate action and is not part of the standard case management workflow.
Yes, it is a type of help desk software, but more powerful. A basic help desk might just log tickets. Dynamics 365 Customer Service integrates with knowledge bases, automates routing, provides dashboards, and connects with other Microsoft products like Outlook and Teams.
No, the core features for agents and managers do not require any coding. You use a web interface with drop-down menus, buttons, and forms. However, customising deeper integrations or creating complex automations might require Power Automate flows, which use no-code drag-and-drop logic.
You've finished Introduction to Dynamics 365 Customer Service. Continue through the MB-910 study guide to build a complete picture of the exam.
Done with this chapter?