MB-230: Designing Customer Service That Resolves Cases Reliably

A customer-service system succeeds when the right person has enough context to solve a problem promptly, not merely when the software records many activities. MB-230, Microsoft Dynamics 365 Customer Service Functional Consultant, examines how an organization configures case management, knowledge, service-level agreements, representative workspaces, routing, and customer-service automation. Microsoft's March 11, 2026 outline concentrates on managing cases, configuring representative experiences and routing, and extending Customer Service. The exam is active as of this October 10 checkpoint.

Functional consultants have to translate operating policies into practical application behavior. A requirement such as 'urgent cases must receive priority' is incomplete until urgency, ownership, escalation, availability, and reporting are defined. A good implementation provides staff with a coherent path from new request to verified resolution, while preserving records for quality review and operational improvement.

Define case data and the meaning of resolution

A case represents an issue or request that needs coordinated handling. Before configuring forms and queues, identify how a case is created, what makes it unique, which customer or asset it belongs to, and which states are meaningful. A case created from email may contain incomplete identity information; one created from a portal may already be associated with an authenticated contact. The application should validate and enrich records without forcing representatives to repeat information that customers have already provided.

Case categories must support real operating decisions. If the classification is too broad, managers cannot learn where problems originate. If the taxonomy is extremely detailed, staff may choose inconsistent categories and analytics become unreliable. Start with the actions each category enables, such as selecting a knowledge base, routing to a specialist, or applying a particular service commitment. Review classifications against actual case samples before treating the taxonomy as final.

The case lifecycle should express the difference between waiting for customer input, actively investigating, escalated to a specialist, and resolved with evidence. Automatically resolving a case because a response was sent can conceal unresolved problems. Define the conditions under which a case may be closed, reopened, merged, or linked to a parent case. Preserve a useful history of changes so a new representative can understand what was attempted without reading every unrelated activity.

A case management and entitlements comparison shows the general principle, even though the implementation platform is different: customer eligibility, issue ownership, and response obligations must align. In Dynamics 365, configure relevant tables, forms, views, business rules, and security roles around the agreed process rather than using every available field simply because it exists.

Make knowledge management usable at the point of service

A searchable knowledge base reduces repeated work only when staff trust its content and can find the right article quickly. Define the article lifecycle: drafting, technical review, translation where needed, publication, and periodic revalidation. A troubleshooting document that was accurate six months ago may now reference a retired product interface or old policy. Knowledge quality requires ownership and effective dates, not merely a publishing button.

Knowledge should be written for actual situations. An article might begin with symptoms, eligibility checks, diagnostic questions, supported resolution steps, and clear escalation conditions. Distinguish instructions suitable for customers from internal procedures that require privileged access or reveal sensitive operational details. Access controls and content visibility need to match that distinction; not every internal note belongs in a self-service portal.

The ideas in knowledge management for self-service are transferable: content structure, search relevance, revision discipline, and feedback determine whether documentation reduces case load. In Dynamics, test whether representatives can find the right entry from the context of a case, not merely by typing its exact title into an administrative search page.

AI-assisted knowledge suggestions can save time, but suggestions are not validated operating procedures. Representatives need to inspect source accuracy, authorization, and applicability before sending generated instructions to customers. A model may blend rules from different product versions or produce steps that are inappropriate for a customer's entitlement. Establish a process for reporting bad suggestions and correcting underlying source content, rather than treating a fluent answer as verified knowledge.

Configure entitlements and service-level agreements carefully

Service-level agreements define measurable commitments such as response or resolution objectives for defined categories of cases. Their value depends on precise clocks and qualifying conditions. Does a target pause when the organization waits for the customer's response? Does it use business hours or continuous elapsed time? Which calendar applies to international customers? A timer configured without answering these questions can report compliance while customers experience a very different service.

Entitlements can reflect contractual eligibility, included units, or service coverage. They should not be confused with SLAs: an entitlement may establish whether a particular support service is available, whereas an SLA sets expected timing or performance for covered work. A customer might be entitled to support but not to the highest-priority response target. This difference should be visible to routing and assignment rules rather than left to individual staff interpretation.

Build and test applicable conditions, warnings, success actions, and escalations. An SLA breach notification must reach someone empowered to intervene. If every approaching target generates a generic alert, staff may ignore the few cases that genuinely need help. Choose practical thresholds and define the response. Examine sample cases that cross non-business hours, change priority, switch owners, or pause while awaiting third-party information.

Service-management incident and problem handling illustrates why resolving an immediate customer incident differs from eliminating an underlying recurring cause. Customer Service can coordinate individual cases while a broader operations process investigates root cause. The functional consultant should make escalation and feedback explicit so repeated incidents can inform product reliability instead of being handled as isolated tickets forever.

Route work based on skills, context, and available capacity

Routing is a business decision implemented through configuration. A request may need a language specialist, a product specialist, or an employee authorized to handle a sensitive account. Basic queue assignment can organize work, while advanced routing may consider skills, availability, capacity, and channel. The consultant must distinguish what the organization actually requires from features that add complexity without improving resolution quality.

Build an assignment example with a new software support request, a billing dispute, and an urgent safety-related issue. Which group should receive each? What happens if that group has no available representatives? Can the work be reassigned without losing the relevant context? Routing rules should include fallbacks and a clear place for unmatched cases to land. An issue that silently disappears because no rule matched is worse than one that arrives in a monitored general queue.

Multi-session representative experiences can support several conversations or cases, but excessive parallel work may increase errors and reduce empathy. Configure workspaces and session templates around genuine operational tasks. A representative handling a billing issue may need account history and entitlement context, while a technical support specialist needs product diagnostics and knowledge search. Tooling should reduce context switching, not multiply distractions.

Teams collaboration and Copilot features can help staff assemble context or obtain input from colleagues. Governance still matters: external chat participants should not receive private customer details without authorization, and generated conversation summaries require validation before they become part of an official record. Measure routing quality through transfers, reopened cases, waiting time, and customer outcomes, not only whether every request was assigned somewhere.

Extend Customer Service without undermining maintainability

Microsoft Power Platform capabilities can support workflow automation, approvals, notifications, forms, reporting, and controlled extensions. The functional consultant should prefer supported configuration patterns where they meet requirements, and request custom development only when it adds clear value. A bespoke integration that reimplements an existing capability may increase future maintenance cost, security exposure, and upgrade risk.

Consider automatic case creation from an external system. The integration must decide how to match contacts, avoid duplicate cases, preserve source identifiers, and handle API failures. If the same event is retried, the target should not create another issue each time. Define error monitoring and replay before deployment. An integration is successful when it handles repeated and malformed inputs predictably, not merely when a demonstration event produces a new record.

Data permissions and privacy span the integrated workflow. A Power Automate flow may run under credentials with access broader than the representative who triggered it. Design automation identities, connection references, and auditability to prevent accidental disclosure. Customer records can contain personal, financial, or contractual information that requires differentiated access and retention rules. Restricting an on-screen form is not sufficient if another automated path exposes the same fields.

Reporting should reveal whether changes improve service. Track case age, first-contact resolution, transfers, SLA attainment, reasons for reopening, knowledge reuse, and workload by channel. Interpret trends cautiously: a drop in reopened cases could reflect better resolution, or it could reflect a configuration that prevents customers from reopening cases. Validate metric definitions and check representative feedback before declaring the system improved.

Prepare MB-230 with an end-to-end customer-service scenario

Design a fictional organization supporting two product lines and three customer tiers. Start with a new case received by email, enrich the contact information, classify the request, and apply eligibility and timing rules. Route it to the right team, suggest relevant knowledge, escalate it when needed, and define what evidence is required to resolve it. Then test unusual paths: an unidentified customer, a duplicate case, no available specialist, and a target crossing a holiday.

Use the same scenario to explain the distinct responsibilities of configuration, workflow automation, reporting, and customer-service governance. A candidate should be able to defend why a field is required, when an SLA clock pauses, and which representative sees sensitive information. Try deliberately misconfiguring a routing rule or a knowledge search filter, then identify which operational metric or user complaint would reveal the problem.

Customer Service differs from legacy Dynamics 365 Field Service, which historically focused on technicians, work orders, assets, scheduling, and mobile field execution. The MB-240 exam retired in June 2026, so it should not be presented as an equally available current next step. These applications can interact, but a customer case is not automatically a field work order; a well-designed process defines when service must transition from remote support to onsite work.

The core MB-230 skill is turning organizational service promises into dependable daily workflows. Candidates who understand case state, knowledge accuracy, entitlements, routing, automation, and outcome metrics can reason about unfamiliar configurations far more effectively than candidates who memorize screen locations. Recheck Microsoft's current outline before scheduling; Customer Service features and licensing arrangements evolve, but the need for traceable, effective resolution remains constant.