Domain 4.2 of the MB-910 exam focuses on how businesses use technology to handle customer issues efficiently. The concept of case management and service processes is the engine that turns a messy customer complaint into a tracked, measurable, and solvable task. For anyone studying for the exam, understanding this process is crucial because it is the backbone of every customer service job in Dynamics 365, and questions about it appear frequently.
Jump to a section
A simple way to picture Case Management and Service Processes
Have you ever had a problem at a restaurant, like receiving the wrong dish or waiting too long for your meal? How did the restaurant handle it? That process is a perfect map for understanding case management in Dynamics 365 Customer Service.
When you tell your server about the issue, that is like creating a 'case'. The server listens, notes your table number and the problem, and then determines if your complaint is valid based on the restaurant's policies — that is your 'entitlement'. For example, if you have a loyalty card that promises a free dessert if your meal is late, that entitlement guarantees a specific response.
Your case is then 'routed' to the right person. A simple cold soup might go straight to the kitchen, while a billing error goes to the manager. The restaurant promises to resolve issues within ten minutes — that is the 'service level agreement' (SLA). A timer starts ticking. If ten minutes pass and nothing happens, an alert goes off, similar to an SLA warning.
The manager updates you, offers a solution (like a replacement meal or a discount), and when you accept, the case is 'resolved'. Finally, they check that you are happy before 'closing' the case. This structured flow from complaint to closure is exactly how Dynamics 365 manages customer service requests, ensuring no problem falls through the cracks.
In the world of Dynamics 365 Customer Service, a 'case' is basically a digital file folder that holds everything about a single customer issue. It is not a computer virus or a briefcase; it is a record in the system that tracks a problem from the moment a customer reports it until the moment it is solved. Think of it as a dedicated notebook page for one specific complaint, where every update, conversation, and internal note is written down in one place.
Before computers, or even simple spreadsheets, customer service agents often used sticky notes, phone messages, or their own memories to track problems. This was a nightmare. Issues were forgotten, customers had to repeat their story to every new person they spoke to, and managers had no idea how long things were taking. Case management software like Dynamics 365 solves all that by digitising the entire workflow.
The process has several key stages. First is 'creation'. A case can be created in many ways: a customer sends an email that the system automatically converts into a case; a customer calls and an agent manually creates one; or a customer fills out a web form that triggers a case in the system.
Once a case exists, it needs to be 'routed' to the right person or team. A simple question about a bill should not go to a technical support engineer who fixes software bugs. Routing is the automatic process of sending the case to the queue or agent best suited to handle it, based on rules you set up. For example, all cases with the word 'refund' in the subject line go to the billing team.
After routing, the case is 'managed' or worked on. This is where the agent interacts with the customer, researches the problem, and tries to fix it. Every action is logged on the case timeline, giving a complete history.
Two critical concepts that govern this whole flow are 'Service Level Agreements' (SLAs) and 'Entitlements'. An SLA is a contract or a promise. It defines how quickly a case must be addressed. For example, a 'Gold' customer might have an SLA that says their case must be acknowledged within one hour and resolved within eight hours. The system tracks this with a timer. If the timer is about to run out, the system can escalate the case to a manager.
An 'Entitlement' defines what a customer is allowed to receive. It is like a pre-approved service coupon. If a customer has purchased a support plan that covers ten support hours per month, the entitlement tracks that usage. When an agent opens a case, the system checks if the customer has remaining entitlement. If they do, the case can proceed. If not, the system might block the creation of a new case or flag it for the billing department first.
Finally, the case is 'resolved' and 'closed'. Resolution means a solution has been provided. Closure happens after the customer confirms the issue is solved. A closed case is archived for reporting.
Why does this matter? It replaces chaos with order. Instead of wondering who is doing what, everyone can see the status of every case. SLAs ensure customers are not ignored. Entitlements prevent abuse of support services. In the MB-910 exam, you need to know the order of these steps and the purpose of SLAs and entitlements.
Case Creation
A case is generated when a customer submits a request via email, phone, web form, or social media. The system automatically creates a record containing customer details and the issue description. This starts the formal tracking process.
Entitlement Validation
The system checks the customer's active entitlements to confirm they are owed support for this issue. If no entitlement exists or it is exhausted, the case may be flagged or blocked, preventing free service without authorization.
SLA Timer Initiation
An SLA timer starts based on the customer's tier or the case urgency. This timer measures how long until a response or resolution is due. If the timer expires, an escalation event is triggered.
Case Routing
The system applies routing rules to assign the case to a specific queue or agent that matches the skills and availability needed. For example, a billing question goes to the billing queue, not a technical team.
Case Work and Resolution
The assigned agent investigates the issue, communicates with the customer, and logs all actions on the case timeline. Once a solution is applied, the agent marks the case as 'Resolved'.
Case Closure
After resolution, the customer confirms the fix is satisfactory. The agent then closes the case, which archives the record. Closed cases are available for reporting and audit but are no longer active.
Let us walk through a realistic scenario at a company called 'CloudyTech', which sells cloud storage subscriptions. CloudyTech uses Dynamics 365 Customer Service. A customer named Priya is a 'Premium' subscriber, which means she has a support contract that includes unlimited support calls and a guaranteed two-hour resolution time.
Priya sends an email to support@cloudytech.com saying she cannot upload files to her account. The exchange server automatically recognises the email as a service request. Dynamics 365 receives the email and creates a new case. The system looks up Priya's account using her email address. It sees she is a Premium subscriber, so it automatically associates an 'Entitlement' with the case that allows for unlimited support minutes.
The new case is then 'routed'. The system uses a routing rule that sends all cases from premium customers to the 'Level 1 - Senior Support' queue, skipping the standard queue. An agent named John, who is a senior support specialist, sees the case pop up in his dashboard.
John opens the case. The system immediately shows an 'SLA Timer' counting down from two hours. Because Priya is a premium customer, the SLA is strict: TTR (Time to Resolve) is two hours. John sees the timer and prioritises this case over others.
John diagnoses the problem. He realises Priya's local internet firewall is blocking the upload port. He sends her instructions to update her firewall settings. He logs this action in the case timeline. Priya tries it and confirms it works.
John checks the 'Case Resolution' activity. He enters a summary: 'Resolved by guiding customer through firewall configuration.' He sets the status to 'Resolved' and clicks 'Close Case'. The SLA timer stops at 47 minutes, well within the two-hour window. The system records this for reporting.
If the two hours had expired without resolution, the SLA would have triggered an escalation. A manager, Sarah, would have received an alert. Sarah could reassign the case, call Priya directly, or take other actions to ensure the SLA was met.
What does the IT professional do here? They do not necessarily fix the firewall. Their role is to:
Configure the system to automatically create cases from incoming emails.
Set up routing rules based on customer tier and issue type.
Define SLA terms (like 'two-hour resolution for Premium') in the system.
Create entitlement templates that match the support contracts sold to customers.
Monitor dashboards to spot cases that are about to breach their SLAs.
Train agents on how to use the case timeline and resolution features.
Run reports to see if SLAs are being met and which agents are performing well.
This scenario shows the full cycle: creation from email, routing to the right agent, management with a tracking SLA, resolution once the fix is applied, and closure with a record. For the exam, you do not need to know how to configure the system, but you must know what each component does and the order of events.
When you sit the MB-910 exam, questions about case management and service processes will test your understanding of definitions and the flow of events. Microsoft loves to test the distinction between similar-sounding terms. They do not ask you to perform tasks in the software; they ask you to identify the correct concept.
Here is exactly what to expect and how to avoid the traps:
Question type: Definition matching. The exam will give you a scenario and ask what the next step should be. For example: 'A customer calls about a bug. After the agent fixes it, what should the agent do next?' The answer is 'Resolve the case'. The trap is offering 'Close the case' immediately. The correct order is to first resolve, then confirm with the customer, then close.
Question type: SLA vs. Entitlement. This is the most common trap. Questions will describe a customer's right to a set number of support hours and ask what defines that. The wrong answer is 'SLA', because people confuse a promise about time with a promise about scope. The correct answer is 'Entitlement'. An SLA defines the time target (e.g., respond in one hour). An Entitlement defines what service is owed (e.g., five hours of support).
- Key concepts that appear frequently: - Case creation sources: email, web portal, phone call, social media. - Routing rules: match to queue based on keywords, customer tier, or product. - SLA: tracks time; can trigger escalation. - Entitlement: tracks usage against a contract; can block service if exhausted. - Case lifecycle: Create, Route, Work, Resolve, Close.
Trap pattern: The 'Automatic' assumption. A question might say: 'When a customer emails support, a case is created automatically.' That is true. But then they might ask: 'When a customer emails, the case is routed automatically.' That is also true. The trap is that they might phrase a question implying manual steps are the norm. In Dynamics 365, nearly all of this is automated once configured.
Trap pattern: The 'Close' shortcut. Beginners think that once a fix is applied, the case disappears. The exam wants you to know that 'Resolve' and 'Close' are two separate steps. Resolving means the work is done. Closing means the customer has confirmed and the record is archived.
- Specific definitions to memorize: - Case: A record for a single customer issue. - Queue: A list of cases waiting to be assigned. - SLA: A contract about time performance. - Entitlement: A contract about service permissions. - Escalation: An event triggered when an SLA is breached.
Exam focus on Relationships: Understand that a single customer can have multiple entitlements (if they buy multiple products) and multiple cases (if they have different problems). Each case is linked to one primary customer record.
What they do NOT test: You will not be asked to write a routing rule or configure an SLA term. The exam is about knowledge, not implementation. Focus on 'what is it?' and 'when does it happen?'
To prepare, practise distinguishing between SLA and entitlement with sample questions. Write out the case lifecycle from memory. Understand that the entire process is designed to make customer service consistent and measurable. If you can explain to a friend how a case moves from creation to closure without looking at notes, you are ready for this section.
A case in Dynamics 365 Customer Service is a digital record that tracks a single customer issue from creation through to resolution and closure.
Service Level Agreements (SLAs) define the promised timeframes for responding to and resolving a case, such as 'respond within 1 hour'.
Entitlements define what service a customer is owed, such as a fixed number of support hours or a specific severity level, and they track usage against that allowance.
The case lifecycle follows a specific order: create, route, work, resolve, and close — 'resolve' and 'close' are two separate steps.
Cases can be created automatically from email, web portals, or social media, not only by manual entry from an agent.
Routing ensures cases are sent to the most appropriate queue or agent based on rules like customer tier, issue type, or product.
Escalation is an automated process triggered when an SLA is about to be breached, notifying a supervisor to intervene.
Entitlements can block case creation or flag issues if the customer has exhausted their prepaid support allowance.
These come up on the exam all the time. Here's how to tell them apart.
SLA (Service Level Agreement)
Defines time-related promises (e.g., respond in 1 hour).
Measures performance against a clock/timer.
Triggers escalation if time is breached.
Entitlement
Defines scope of service owed (e.g., 10 hours of support).
Tracks usage against a quantity allowance.
Can block service if allowance is exhausted.
Resolve Case
Marks the case as completed from the agent's view.
Solution has been provided and logged.
Does not archive the record permanently yet.
Close Case
Finalises and archives the case record.
Usually requires customer confirmation first.
Removes the case from active queues.
Manual Case Creation
Agent enters details into the system by hand.
Slower and prone to human error.
Used for phone calls or walk-in requests.
Automatic Case Creation
System creates case from email, web, or social media.
Faster and consistent with pre-defined rules.
Reduces agent workload for standard requests.
Queue
A virtual bucket holding unassigned cases.
Cases wait in a queue until an agent picks them.
Routing sends cases to specific queues.
Agent
A human who works on and resolves cases.
Agents claim cases from queues.
Agents have individual dashboards and worklists.
Mistake
A 'case' and a 'ticket' are completely different things in Dynamics 365.
Correct
In Dynamics 365 Customer Service, 'case' and 'ticket' are used interchangeably. Both refer to the record tracking a single customer issue.
Beginners often hear 'ticket' in other software contexts (like IT help desks) and assume it is a distinct feature in this system, but it is just a synonym here.
Mistake
Resolving and closing a case are the same action.
Correct
Resolving applies the solution and marks the case as 'Resolved'. Closing is a separate final step that archives the case, typically after customer confirmation.
In everyday language, we say 'close a case' to mean 'finish it', so beginners merge the two steps into one. The exam tests the distinct separation.
Mistake
An SLA tells you what a customer is allowed to receive (like number of hours of support).
Correct
An SLA defines the timeline for response and resolution. An Entitlement defines the scope of service a customer is allowed to receive.
Both concepts govern service, but beginners mix up 'time' (SLA) and 'scope' (Entitlement). The terms sound similar in a business context.
Mistake
Cases can only be created by customer service agents manually.
Correct
Cases can be created automatically from multiple sources including email, web portals, social media, and other integrations, without any human action.
Beginners think of the 'creation' step as something a person does, because that is how it worked in old systems. Modern systems automate this process.
Mistake
An entitlement is just another word for a warranty.
Correct
An entitlement defines support terms like hours allowed or severity levels, which is broader than a product warranty and can include service plans and prepaid support.
The word 'entitlement' sounds legal and warranty-like, but in Dynamics 365 it is specifically about service delivery permissions, not just product guarantees.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
An SLA (Service Level Agreement) defines time targets, such as how quickly a case must be responded to or resolved. An Entitlement defines what service a customer is allowed to use, like 10 hours of support per month.
Yes, cases can be created automatically from emails, web portal submissions, or social media posts using rules in Dynamics 365 Customer Service.
Routing is the automatic process of sending a new case to the right queue or agent based on predetermined rules, such as the customer's tier or the subject of the issue.
'Resolved' means a solution has been provided and the case is complete from the agent's perspective. 'Closed' is a final step that archives the case, usually after the customer confirms the fix.
When an SLA timer expires, an escalation is triggered. This notifies a supervisor or manager, who can reassign the case or take other actions to meet the service commitment.
Yes, a single customer can have multiple entitlements, for example one for product A and another for product B, and each is tracked separately for usage.
You've finished Case Management and Service Processes. Continue through the MB-910 study guide to build a complete picture of the exam.
Done with this chapter?