Microsoft Dynamics 365 Customer Service Functional Consultant (MB-230) — Questions 76–150

Macros allow administrators to record or script a series of actions that the system executes automatically. In this scenario, a macro can be configured to populate an email template, send it, and then update the case status and resolution fields, all triggered by a single agent action.

The 'Similar Cases' feature in Dynamics 365 Customer Service uses natural language processing to suggest cases that are similar to the current case based on title and description. Enabling this feature allows agents to see a list of suggested cases directly on the case form. This is the standard, built-in functionality that meets the requirement without custom development.

Routing rule sets evaluate conditions against context variables provided by the channel. By creating a rule set with a condition on the language context variable and associating it with the workstream, you ensure that conversations are routed to the appropriate queue based on the customer's language.

Creating a 1:N relationship from Case to the custom feedback entity establishes the association, enabling users to add feedback records from a case. This is the foundational step before adding the entity to the app or customizing forms. It ensures that feedback can be linked to cases and viewed in the case's related records.

Knowledge article templates provide pre-structured resolution content that agents can apply to a case and reuse, avoiding retyping. This satisfies the requirement to capture recurring resolutions quickly and apply them to future cases within Dynamics 365 Customer Service.

The JSON clearly defines a 24-hour delay ('24h') triggered by the 'Case_Resolved' event. This confirms that the survey is queued for delivery one full day after the case status changes to resolved, which is the intended business process for collecting delayed customer feedback.

Customer summary is a feature in the Customer Service workspace that automatically displays a 360-degree view of the customer, including recent cases, orders, and other relevant information. When a call arrives, the summary is presented to the agent, enabling quick context. This directly meets the requirement to view recent orders and case history during a call.

The JSON policy clearly maps cases meeting the premium criteria to the 'premium_support_team' queue. Since the priority is set to 1, this rule will take precedence, ensuring the routing engine directs the record to the specified target queue immediately upon evaluation of the business logic.

The 'Update a record' action in the Common Data Service (current environment) connector allows you to modify fields on any entity, including the Case entity. This is the correct way to update a case record from a Power Automate flow, ensuring the change is tracked and triggers any associated business logic.

This option correctly describes a Power Automate flow that triggers on case resolution, evaluates the customer's consent field, and conditionally sends a Customer Voice survey. This meets the requirement of sending the survey only if consent is recorded. Power Automate can easily check a field value and branch logic. This is the most accurate and complete solution.

The Related Cases subgrid is a standard component that surfaces other cases linked to the same customer record. By adding it to the case form and applying a view filter for Resolved status, agents see prior resolutions in context without navigating away. This meets the requirement directly and uses native form configuration.

PCF is the standard, fully supported framework for creating custom controls. It provides a robust API for interacting with Dataverse data and ensures that custom components are performant, accessible, and follow the standard model-driven application lifecycle, which is vital for enterprise-grade customer service deployments.

In Customer Service workspace, a session template defines the layout of a session, including which tabs appear and their sequence. Each tab is represented by a session template tab record that references an app page, entity form, or custom page. This is the correct component to configure the desired agent experience with multiple tabs.

Advanced Find allows agents to create custom queries with multiple conditions, such as customer and escalated status, to locate specific cases. It provides a flexible way to search across entities and filter results. This feature is ideal for ad-hoc searches when predefined views do not meet the need.

The Timeline control on the case form displays all activities related to the case, including phone calls, emails, appointments, and notes. It provides a consolidated view, allowing the representative to see the complete interaction history without navigating away, which directly satisfies the requirement.

The Timeline control on the case form displays all activities and posts related to the case in a chronological view. It includes emails, phone calls, appointments, tasks, and notes, allowing the representative to see the complete interaction history. This is the standard feature for viewing all customer interactions in one place.

These rules are used to inspect the incoming work item and assign attributes such as 'Language' or 'Region' based on values in the record or related data. This step is critical because it prepares the record with the specific tags needed for the subsequent queue assignment logic to function.

In unified routing, you can define multiple queues within a workstream. Each queue can have its own assignment method. By creating a high-priority queue with 'Highest capacity' assignment and a low-priority queue with 'Round robin', and then using routing rules to direct cases to the appropriate queue based on priority, you achieve the desired behavior. This approach leverages queue-level assignment methods, which is the correct way to implement different assignment strategies per priority.

Escalation rules in Customer Service are time-based: they can run after a set number of minutes or hours from case creation and take actions such as assigning to a queue. Configuring a 30-minute rule that targets the Tier 2 queue meets the scenario without code, and the rule can include conditions so only High priority cases are escalated.

Capacity profiles are the standard, intended component for workload management. They allow administrators to define 'units' of work and assign them to agents, ensuring that the system enforces limits on concurrent interactions based on the agent's skill level and the complexity of the specific work being assigned.

Smart Assist provides real-time suggestions to agents, including knowledge articles, based on the context of the conversation. It uses machine learning to analyze chat text and surface relevant articles. It also tracks which suggestions are accepted, allowing measurement of effectiveness, aligning with the requirement.

Unified routing evaluates rules in order. If a catch-all rule with no conditions is placed before the specific priority rule, it will match all cases and route them to the General queue, preventing the priority rule from ever executing. Ensuring rule order and activation is critical for correct routing behavior.

The Similar Cases control employs machine learning models to identify and recommend previously resolved cases sharing similar characteristics. Agents can inspect these recommendations directly within the workspace and apply proven resolution steps with minimal effort.

SLA KPIs support pause conditions based on field values. By setting a pause condition on the Case Status field when it equals 'On Hold', the SLA timer for the KPI will pause when that condition is met and resume when the condition is no longer true. This directly meets the requirement to pause and resume the resolution time KPI based on case status changes.

Work item priority rules allow you to define the priority of work items within a queue based on attributes such as the case priority field. By setting up a rule that assigns higher priority to cases with higher priority values, the routing engine will assign those cases first. This directly meets the requirement.

SLA items support pause and resume conditions that evaluate case fields. Setting 'Pause When' to detect the waiting-on-customer state and 'Resume When' to detect the customer reply makes the KPI timer pause while waiting and resume when the customer responds. This directly implements the required behavior without changing the KPI's success or failure criteria.

Macros are a core component of Agent Scripts, allowing the script to execute automated tasks in the background when the agent clicks the step. This reduces manual data entry and ensures that complex operations, such as creating a follow-up task and closing a case simultaneously, are performed accurately.

The 'Assignment' stage in Routing Diagnostics lists all agents in the queue and explains why they weren't chosen. Common reasons include 'Agent is at capacity', 'Presence does not match', or 'Missing required skills'. This is the most direct way to understand why available agents are not receiving work.

Unified routing uses work classification and routing rule sets to evaluate incoming records, such as high-priority cases, against defined criteria. It automatically matches and assigns these items to the correct queues, ensuring they reach qualified senior support agents immediately.

Entity Auditing is specifically designed to track data changes across the system. By enabling it for the Case entity, administrators ensure that all field updates, including status changes, are logged with the user, timestamp, and old/new values, providing a complete history of the case's lifecycle for review.

Power Automate can trigger on the status change of a case (e.g., when resolved) and use the Dynamics 365 Customer Voice connector to send a survey. This is the standard method to automate survey distribution. It requires no code and integrates seamlessly with Customer Service. The flow can be configured to include case details and personalize the survey.

Skill-based routing rules in the workstream allow you to define conditions that match case requirements to agent skills. By specifying that the 'Technical' skill must be 3 or higher, the routing engine will only consider agents who meet that proficiency. This is a core component of unified routing for skill-based assignment.

In Omnichannel, routing rules can use context variables that are populated from session or customer data. To use a custom field on the Contact, you must define it as a context variable in the workstream and map it to the corresponding Contact field. This makes the value available to the routing engine for evaluation.

Unified Routing excels by using intelligent classification and assignment methods. By evaluating agent skills, capacity, and presence, it ensures that every work item is assigned to the most appropriate agent. This directly translates to faster resolution times and better customer outcomes, which is the core business value of the feature.

A synchronous pre-operation plug-in registered on the Resolve message for the Case entity runs before the resolution is committed and can throw an InvalidPluginExecutionException if the resolution description is empty. This blocks the resolution regardless of the client or integration used, satisfying the requirement that all case forms and resolution paths enforce the same rule consistently and reliably.

The session template record has specific fields for 'Tab Title' and 'Icon'. By configuring these fields, administrators can ensure that every session initiated from a specific channel or for a specific entity has a consistent and recognizable visual identity for the agent using the workspace.

In the OnSave event, you can use executionContext.getEventArgs().preventDefault() to cancel the save operation. This is the supported method to prevent the save when validation fails. The function must be registered as an OnSave handler and receive the execution context. This approach allows you to display an error message and stop the save from proceeding, ensuring data integrity.

Creating child cases from the parent case links them through the parent-child relationship, and setting the parent case closure preference to require resolved child cases enforces the dependency. Each child case carries its own priority, owner, and resolution notes, which satisfies the requirement for independent tracking while keeping the work associated with the original customer issue.

Creating two capacity profiles—one for technical cases with a limit of 2 and one for billing with a limit of 5—allows the system to track each workload separately. This ensures that the agent never exceeds the specific limit for either category, providing precise control over their concurrent tasks.

To route based on language, agents must have a corresponding skill defined. In unified routing, skills are attached to users via the skill attachment. Without a language skill on the agent, the routing engine cannot match the caller's language requirement to an agent.

Condition-based routing rules in unified routing allow you to evaluate case attributes such as customer tier. By creating a rule that checks if the customer tier is 'Platinum', you can automatically route those cases to the 'Platinum Support' queue upon creation, meeting the requirement for immediate routing.

Enabling Knowledge Management is a two-step process: enabling it at the system level and then enabling it for specific entities. If this is not done, the Knowledge Search control cannot function because the underlying relationship between the entity and the knowledge base has not been established.

Session Templates control the agent's environment for a specific record type. By adding a tab to the 'Additional Tabs' list in the Session Template, you can automate the workspace so that opening a case also triggers the opening of other relevant URLs or entity views in separate tabs.

Round robin distributes work items sequentially to available agents in a predefined order, ensuring an even distribution. This matches the requirement to balance workload and prevent overloading any agent, as each agent receives work in turn.

Advanced Find allows the representative to build a query that filters cases based on the Product field. It provides precise results and can be saved as a personal view for future use, directly addressing the need to find cases related to a specific product.

An HTML web resource can be embedded on the Case form and use JavaScript to call the external REST API, then render the order data in a section. This provides real-time data without navigating away. Web resources are a standard way to extend forms with custom UI and integrate with external services, making this the correct approach.

This is the correct origin. Pre-chat surveys allow customers to provide info (like their tier) before the session begins. Alternatively, developers can use the 'setContextVariable' method in the portal's Javascript to pass authenticated user data directly into the Omnichannel routing engine for immediate rule evaluation.

The JSON explicitly defines the action as 'assign_to_queue' with the target set to 'Emergency_Support_Queue'. This confirms that the logic correctly maps the high-priority case to the specified queue, which is the intended behavior for prioritizing sensitive or time-critical support requests within the system.

Automatic record creation and update rules explicitly transform incoming activities like emails into cases. Rule items apply criteria and map fields such as email subject to case title, while integrated settings manage automated response configurations seamlessly.

Exact match requires that the agent's skill level exactly equals the required level. If the case requires 'Advanced' proficiency, only agents with 'Advanced' Networking skill will be matched. This ensures precise routing and prevents agents with lower or higher proficiency from receiving the case, which is critical when the requirement is strict.

Capacity profiles define the maximum number of concurrent work items an agent can handle. By creating a capacity profile with a limit of 2 for chat and assigning it to agents, the routing engine will prevent agents from being assigned more than two chats at a time, ensuring they are not overloaded.

When an incoming record fails all defined routing rule conditions within a workstream, the Unified Routing engine directs the item to the default queue. This ensures that every work item is captured and assigned to a location where it can eventually be handled by an agent.

By creating a custom presence and mapping it to a base presence like 'Busy' or 'Do Not Disturb', the system understands that the agent is not available for new work. The custom name 'Training' provides the specific context needed for management and reporting purposes in the dashboard.

Activities such as phone calls, tasks, and appointments can be created directly from a case and are linked to it through the regarding lookup. Adding a phone call captures the callback interaction, its duration, and notes on the same case, preserving a complete timeline. This is the intended way to log a new customer interaction on an existing case without creating a new case record.

SLA warning actions execute at the warning time threshold defined in the SLA KPI item. By setting up email notifications or tasks at this point, agents are alerted while the case is still compliant. This proactive notification is the correct mechanism for ensuring that teams address cases before failure occurs.

Templates provide a pre-defined layout that ensures every article includes mandatory sections. This consistency makes it easier for agents to scan articles for answers, improving the speed and quality of support provided during customer interactions, which is a core benefit of a well-organized knowledge base.

Custom actions in Dynamics 365 are exposed as messages. To execute a plug-in when a custom action is invoked, you register a step on that custom action's message. Post-operation ensures the plug-in runs after the action's core logic, allowing you to use the action's output parameters and perform additional updates. This is the standard pattern for extending custom actions with plug-ins.

The pre-chat survey in Omnichannel for Customer Service supports branching logic, allowing you to show or hide questions based on responses to earlier questions. This is configured directly in the survey designer. It enables dynamic, personalized data collection before the conversation starts, exactly as required for the scenario.

Macros are specifically built to automate sequential tasks that an agent would otherwise perform manually. By using the macro designer, consultants can create a sequence of actions like opening an email form, populating data, and updating case status, which agents trigger to save significant time.

Post-conversation surveys are designed to be sent automatically after a conversation ends. They allow you to collect customer feedback on the interaction. By configuring a post-conversation survey on the messaging workstream, you ensure that the survey is triggered when the agent closes the conversation, meeting the requirement directly.

Rejection handling in unified routing allows you to define what happens when an agent rejects a work item. You can configure it to return the item to the queue after a specified timeout, ensuring it is re-routed. This directly addresses the requirement of automatically routing the case back to the same queue after rejection.

A custom action can be defined as global, meaning it is not bound to a specific entity and can be called from any entity or process. It can contain multiple steps, such as updating a record and creating a task. This makes it reusable and suitable for the scenario.

This setting ensures that resolving a parent case automatically resolves all associated child cases. It is essential for maintaining data consistency and preventing orphaned child cases. By enabling this, the supervisor meets the requirement that resolving the parent also resolves children, streamlining case management and ensuring no child cases remain open unintentionally.

Separate workstreams for cases and chats allow you to apply distinct routing rules. Each workstream can have a route-to-queue rule that checks for the required skill, ensuring cases go to agents with 'Case Management' skill and chats to agents with 'Chat' skill. This meets the requirement precisely.

The Timeline control on the case form allows you to add notes and attach files directly. These attachments are stored as part of the case record and are accessible to anyone with access to the case. This is the standard way to add notes with attachments in Dynamics 365 Customer Service, meeting the requirement to store the file within the case.

Work item skills are the skills required to handle a particular work item. These are typically specified on the work item (e.g., a case) or derived from the queue or routing rules. The routing engine compares the work item's required skills with the agents' skills to find a match. Without defining required skills for work items, skill-based routing cannot occur because there is no criteria to match against.

The capacity profile defines the maximum number of work items an agent can handle simultaneously. By assigning a numeric capacity value, the routing engine stops assigning new work when the agent reaches that limit. This directly satisfies the requirement to enforce a work item cap and automatically remove the agent from assignment once full.

Custom command buttons on the ribbon can be configured with enable rules and display rules that use JavaScript to evaluate conditions like the case status. The JavaScript can also open a URL in a new tab. This is the standard supported method to add a button with dynamic visibility and custom action on a form.

The Historical Analytics dashboard includes specific reports for queues and routing. It allows users to drill down into wait times, session lengths, and assignment durations, providing the necessary insights to understand why items are delayed and how the routing configuration might be improved.

The Knowledge Base Search control is a customizable control that must be added to the form where agents need it. By using the form designer, you can insert the control into the case form, typically in a tab or section. This makes the knowledge base search functionality directly accessible to agents within the case record.

In unified routing, workstreams define the routing pipeline for a channel and record type, and the attached routing rule set contains the conditions and decision logic. To route by skills, you must create a workstream for cases and configure routing rules that evaluate skills, which then direct the case to the appropriate queue or agent. This component is mandatory for skill-based routing to function.

Canvas apps embedded in model-driven forms can receive parameters through the URL. By configuring the canvas app to read a parameter using the Param function, and setting the URL in the form's custom control properties to include the case ID, the app can access it. This is the supported method for passing contextual data to embedded canvas apps.

Skill-based assignment matches work items to agents based on the skills required by the work item and the skills possessed by the agent. By configuring the workstream to use skill-based assignment and specifying the 'Spanish' skill as required, the system will only assign calls to agents who have that skill and are available. This directly meets the requirement of routing to Spanish-speaking agents.

Assignment methods utilize capacity profiles to evaluate the current workload of agents. By configuring the 'Least Active' method, the system identifies agents with the lowest number of assigned items. This ensures optimal distribution of incoming cases, directly addressing the requirement to balance work across the service department effectively.

Business rules can validate field values and show an error message conditionally. By setting a condition that checks the length of the Resolution field and then showing an error message, you can prevent saving when the condition is not met. This works across forms and is a no-code solution. However, note that business rules do not run on server-side operations like API or email, so additional validation might be needed for those channels.