Microsoft Dynamics 365 Customer Service Functional Consultant (MB-230) — Questions 1–75

Real-time Sentiment Analysis is the native capability designed specifically for this purpose. It analyzes chat text in real-time, displaying a sentiment score and icon in the agent's interface, allowing them to instantly adapt their approach to the specific emotional state of the customer during the session.

The Channel Integration Framework (CIF) is specifically designed to integrate third-party communication widgets with Dynamics 365 Customer Service. It provides a set of JavaScript APIs that allow the external widget to interact with the Customer Service workspace, including creating sessions, passing context data, and handling events. This is the correct technology for this scenario.

The Similar Cases feature uses AI to suggest cases that are similar to the current case based on attributes like title and description. It helps agents find resolutions from past cases. Adding a Knowledge Articles subgrid allows agents to link relevant knowledge articles to the case. This combination meets both requirements.

Routing rules are evaluated in order, and you can use conditions with AND logic. The first rule handles the specific combination of Platinum and High priority. The second rule acts as a catch-all for any case not matching the first, ensuring correct routing. This meets the requirement precisely.

Knowledge management must be turned on so articles can be authored, published, and searched from within the case form. Enabling it surfaces the knowledge controls and the search experience that drives suggestions. Without it, agents would have no article search pane on the case, so the suggestion experience cannot function.

HTML web resources are the primary supported way to embed custom UI content. By using HTML, CSS, and JavaScript, you can create a fully interactive interface that interacts with the session context and updates dynamically based on the data being viewed, providing a truly customized experience for the support agent.

The Timeline control on the case form displays all activities related to the case, including phone calls, emails, tasks, and appointments, in a chronological view. It provides a consolidated history of interactions, allowing the agent to quickly review past communications. This is the standard feature for viewing case-related activities and is available out of the box.

Workstreams are the central construct for managing incoming work in Unified Routing. They define the channel type, the routing rules, and the capacity settings. During migration, you must map your existing legacy queues and rules into the workstream structure to enable the new, unified routing engine's features.

A rule set defines the order of evaluation for routing rules. It contains a list of rules that are evaluated sequentially, and the first rule that matches determines the routing action. This allows you to prioritize conditions such as product category before region, ensuring the correct queue or agent is selected based on the defined sequence.

Customer summary is a feature that displays a consolidated view of a customer's key information, including recent cases, entitlements, and recent interactions, directly within the customer service agent's workspace. It is designed to provide quick context during interactions, exactly as required in this scenario.

Skill-based assignment uses the skills and proficiency levels defined for agents to match work items. By configuring the queue with a skill-based assignment method and specifying the 'English' skill, you ensure that only agents with that skill are considered. This directly meets the requirement of routing to agents with the 'English' skill.

SLA pause conditions allow administrators to specify exact criteria, such as specific case statuses, that trigger a temporary stop in SLA time tracking. When the status changes away from the specified value, the SLA timer automatically resumes.

This approach uses separate queues and an overflow condition on the Spanish queue to redirect after a timeout if no agent is assigned. Unified routing supports queue overflow based on wait time, enabling the desired fallback to the English queue after 5 minutes, ensuring timely service.

Because 'Closest Match' is active and the agent's proficiency of 4 is above the 'minProficiency' threshold of 3, the engine identifies this agent as the best available match. It will proceed with the assignment even though the agent does not meet the ideal level 5 requirement.

A workstream defines the routing logic and conditions for a specific type of work item, such as cases from a particular queue. It is essential for specifying how cases should be routed, including the rules for agent assignment. Without a workstream, unified routing cannot determine how to handle the cases.

Unified routing in Dynamics 365 Customer Service supports skill-based routing, allowing you to define skills for agents and route cases to those with matching skills. This ensures that cases are assigned to the most qualified agent. Unified routing also considers capacity and other factors, but the skill-based component directly addresses the requirement.

Longest idle is designed to assign work to the agent who has been waiting the longest without an assignment. This directly matches the manager's requirement to prioritize idle time over case count. It helps balance workload by ensuring agents who have been available longer get the next case, improving fairness and reducing agent burnout.

Agent Experience Profiles allow admins to create tailored experiences for different agent groups by managing productivity tools, channel providers, and session settings. This ensures that agents only access the specific features required for their roles, effectively streamlining the user interface and reducing overall cognitive load.

A workflow can be triggered on the creation of a case. It can use an email template that includes dynamic fields for the case number and a hyperlink to the case record. The workflow sends the email and creates an email activity associated with the case. This activity record allows tracking of delivery status, such as whether the email was sent, delivered, or failed. This fully meets the requirement.

Adding a note on the case timeline and attaching the file directly to that note is the standard way to record customer-visible communication with supporting documentation. The note and attachment become part of the case's activity history, so other agents can see the interaction and open the file from the timeline. This meets the requirement of visibility and accessibility within the case record.

A customer service schedule defines the working hours and is applied to the SLA to ensure that the timer only runs during those hours. By setting the first response KPI to use this schedule, the SLA timer will pause outside business hours and resume at the next business hour. This precisely meets the requirement to only count business hours and handle cases created outside business hours appropriately.

Routing rule sets evaluate conditions and route cases to queues or users in real time. They can use the product field as a condition to determine the destination queue. This feature is specifically designed for automatic case routing upon creation or update, ensuring immediate assignment based on the specified criteria.

Placing the generated embed code into the website's HTML is the standard method to surface the chat widget. The embed code includes the necessary script references and configuration to load the Omnichannel live chat widget. Once deployed, the widget connects to the Omnichannel service, allowing website visitors to start conversations that are routed to agents. This step is essential after creating the widget in the Omnichannel Administration app.

Routing rules in workstreams can evaluate conditions, including message content. By creating a rule that checks if the message contains 'urgent', you can route the chat to a high-priority queue. This directly satisfies the requirement. Routing rules are evaluated in order and can trigger immediate queue changes based on real-time input.

The workstream defines the routing for the voice channel, and the queue must contain agents with the required skill. This ensures that only qualified agents receive the call. Without this, calls could go to unskilled agents, violating the skill requirement. This is a necessary component to achieve skill-based routing for voice.

Customer Voice is the built-in survey tool in Dynamics 365 Customer Service. You can create a survey and use Power Automate to trigger sending the survey when a case is resolved, with conditions on priority and contact preference. This is the recommended and supported method to automate satisfaction surveys based on case events.

Knowledge management lets you author searchable knowledge base articles and link them to cases, so agents can locate existing resolutions and insert them without retyping. This satisfies the recurring-issue requirement for fast, consistent resolution reuse.

This is the mandatory first step. Enabling the entity for routing registers it with the Unified Routing service. Once this is done, you can proceed to define intake rules, workstreams, and assignment logic specific to that entity type to ensure records are distributed correctly to agents.

In Power Virtual Agents, you can call a Power Automate flow from a topic by adding a 'Call an action' node. This node allows you to select a flow that has been made available to the bot. The flow must be created and then added to the bot's actions. This is the correct way to invoke a flow from the bot.

This filter correctly identifies the team relationship. By using the 'Current User's Teams' criteria, the system dynamically evaluates the agent's team memberships and filters the record list to show only cases assigned to those specific teams, providing a relevant and accurate view of team-based work.

Routing rule sets in Dynamics 365 Customer Service allow you to define rules that automatically route cases to queues based on conditions such as product and priority. They are designed for this purpose and can be easily managed and prioritized. This is the correct feature for rule-based queue assignment.

Unified Routing supports custom routing rules that can invoke Power Automate flows. By using a flow, you can call the external AI service via an HTTP action or custom connector, then return a value that sets a routing attribute such as priority. This approach uses low-code tools, is maintainable, and integrates directly into the routing decision process without writing plug-ins or custom code.

Longest idle assigns the next work item to the agent who has been idle for the longest period. This directly matches the requirement to prioritize agents based on idle time. In unified routing, this method helps balance workload by ensuring that agents who have not received work recently are given priority, improving agent satisfaction and reducing burnout.

The chat widget is the client-side component that customers interact with. It includes settings for pre-chat surveys, where you can add questions to collect information such as email address and product interest. These responses can be used for routing and context. Configuring the survey in the chat widget ensures the data is captured before the conversation is initiated.

This approach correctly uses an SLA with a business hours calendar to count only business hours. The KPI can be configured to pause when the case status changes to 'Waiting on Customer'. The SLA can be applied conditionally based on case priority. This meets all the stated requirements using out-of-the-box SLA capabilities.

A custom field to count reopenings and a business rule to enforce a reason when the status changes to Reopened directly address the requirement. Business rules can set a field as required based on another field's value or status change, and can also increment a counter. This provides both tracking and enforcement without custom code, which is the recommended no-code approach in Dynamics 365 Customer Service.

Round robin assignment distributes work items evenly among available agents in a sequential order. It does not consider current workload, making it suitable when the goal is equal distribution. This method is ideal for the scenario because it ensures each agent receives a similar number of emails over time, regardless of their existing assignments.

Unit-based capacity allows administrators to assign a specific number of capacity units to agents. Each incoming work item consumes a fixed amount of these units, and the system prevents further assignments once the agent's total available units reach zero, ensuring manageable workloads.

Advanced Find allows the user to build complex queries against any entity. By selecting the Case entity, adding a condition for Customer, and another for Status Reason with a date filter, the representative can retrieve exactly the cases needed. The results can be viewed as a list and even saved as a personal view for future use. This meets the requirement without creating a custom view from scratch.

To allow the bot to access Dynamics 365 data securely, you must register an application in Azure AD, grant it API permissions to Dynamics 365 (such as user impersonation or application user), and configure the bot to authenticate using the application's client ID and secret. This enables the bot to obtain an access token and call the Dynamics 365 Web API. This is the standard secure method for server-to-server integration.

Routing rule sets are used to automatically route cases to queues based on conditions. By creating a rule that evaluates the case origin field and routes to the 'Web Support' queue, the case will be directed appropriately. This is the standard method for channel-based routing in Dynamics 365 Customer Service.

This is correct because unified routing evaluates workstreams in priority order. By assigning a higher priority to the workstream that routes Platinum cases, those cases are processed before lower-priority workstreams, ensuring they reach the dedicated queue first. The route-to-queue rule with a condition on the customer tier field directly targets the required cases.

This is correct because 'Auto-open on assignment' is a setting in the Customer Service admin center that automatically opens the record in the agent's session when it is assigned. This ensures the agent can immediately begin working on the case without manually searching for it. It streamlines the workflow and reduces response time.

This is correct because a custom web resource can be embedded on the Case form and use formContext to subscribe to the OnChange event of the customer field. When the field changes, the script can call an external API and update the control's content dynamically without reloading the entire form. This is the standard extensibility approach for dynamic, in-form custom UI.

In unified routing, each workstream must have an assignment method configured. If the assignment method is set to 'None', the system will not assign work items to agents, even if eligible agents exist. This would result in chats remaining unassigned. Configuring an assignment method such as 'Round Robin' or 'Highest Capacity' is necessary for automatic assignment.

Routing rules in Omnichannel are used to evaluate conditions, such as pre-chat survey responses, and route conversations to specific queues. You can create a rule that checks the product interest question and directs the conversation to the appropriate queue. This is the correct component for conditional routing based on survey data.

This is correct because in the presence configuration, each presence status can be associated with a routing status. Setting 'Do not disturb' to 'Do not route' ensures that agents in that presence are not assigned new work items. This is the standard way to prevent assignment based on presence.

In unified routing, a workstream must be activated to process incoming work items. If the workstream is in a draft or inactive state, routing rules within it are not evaluated, and items will not be routed to any queue. Activating the workstream ensures that the classification and routing logic executes, directing emails to the specified queue based on the configured rules.

Work streams act as containers for incoming work items of a specific channel or record type, defining routing behavior and agent capacity allocation. They are fundamental prerequisites for unified routing, grouping incoming cases before rule sets evaluate them.

Power BI embedded dashboards support real-time data refreshing, which is ideal for supervisor monitoring. By integrating these into the workspace, you provide a dynamic view of team metrics, allowing supervisors to respond immediately to changes in volume or performance without needing to switch between different applications to access reports.

Round robin distributes work items evenly across available agents in a circular order, which matches the requirement for even distribution. It also respects capacity if configured, so agents at maximum capacity are skipped. This method is ideal when the goal is fairness and load balancing without prioritizing specific skills or capacity levels.

Knowledge Articles provide a structured entity specifically designed for content creation, categorization, and publication. They support rich text, versioning, and lifecycle states like draft, approved, and published. This makes them the only appropriate choice for maintaining a repository of solutions that agents can leverage during their daily work.

Capacity profiles define the maximum workload for agents. When assigned to a queue, unified routing respects these limits and will not assign cases to agents who have reached their capacity. This directly addresses the problem of agents receiving cases when at maximum capacity, ensuring fair distribution and preventing overload.

Advanced Find allows users to build queries across multiple entities and filter by fields such as product and escalation status. It can also filter by date ranges, like the last week. This is the correct tool for ad-hoc searches that combine conditions. It provides a flexible way to locate specific cases without needing custom views.

Prioritization rules evaluate attributes on incoming work items and dynamically assign a rank value. The unified routing engine processes items based on this rank, ensuring VIP customer emails are positioned at the front of the queue for immediate pickup by available senior agents.

A custom action (a real-time workflow) can be invoked from the command bar and can create a Phone Call, set its regarding field to the case, and populate the subject from the case title. This approach is server-side, reliable, and does not require the agent to leave the case form. It also respects security roles and can be reused in other contexts, such as from a business process flow or a web resource.

Embedded Microsoft Teams chats within Dynamics 365 allow agents to link conversations directly to the case record. This preserves the single source of truth, enables seamless cross-functional collaboration, and ensures all internal stakeholder notes are captured contextually without fragmenting the overarching support workflow or requiring duplicate data entry.

Customer identification rules in Omnichannel for Customer Service automatically identify customers based on attributes like phone number or email. If no match is found, you can configure the system to create a new contact record. This is exactly the feature designed for this requirement.

Creating a new case and setting its Parent Case field to the original case establishes a parent-child relationship. This allows the representative to track the new issue separately while maintaining a link to the original case. The original case remains open, and both cases can be managed independently. This is the correct way to handle related but distinct issues.

A Power Automate flow can trigger when a case is escalated, create a new case, copy the customer and subject, and link it to the original. This keeps the original open and automates the process. It provides the flexibility to set the new case's fields and relationship as needed.

Work item prioritisation rules in the unified routing work stream let you define conditions that rank incoming records, so high-priority chats are matched to agents ahead of low-priority cases. This directly satisfies the requirement to assign high-priority work items before lower-priority ones, rather than relying on capacity alone.

Virtual entities allow integration with external data sources without data replication. By creating a virtual entity with an OData provider, you can surface external ERP data as if it were native. Adding it to the workspace enables agents to view recent orders. This requires minimal custom development, typically just configuration of the data source and entity.

Context variables are used to store and pass data within a conversation. To route based on language, you must define a context variable that captures the language from the incoming message. This variable can then be used in routing rules to direct the conversation to the appropriate queue. Without a context variable, the routing engine has no data to evaluate for language-based routing.

Capacity profiles define the maximum number of concurrent sessions an agent can handle, so assigning a three-session profile to standard agents and a one-session profile to VIP agents enforces the differing limits. This satisfies the stem's constraint that VIP agents receive no simultaneous chats while standard agents handle up to three.

Under the Exact Match and Round Robin configuration, the system requires the specific skill to be present. If qualified agents are at capacity, the work item persists in the queue backlog until an agent's capacity frees up to accept the specific skill-tagged work item as defined.

Classification rules allow the system to perform logical evaluations and lookups to update the work item with additional context. By using these rules, the system can fetch the tier value from the related account and use it to set a priority level or attribute that determines routing.

Routing rules evaluate conditions on the case record, such as the Product field, and then route the case to a designated queue. This is exactly what the manager needs: when a case is created with a specific product, the rule matches and assigns it to the corresponding queue. The rule set must be activated, which is already done, so only the rule itself needs to be configured.

For a custom entity to be searchable in Customer Service Hub, it must have a Quick Find view configured with the relevant columns. The search index relies on the Quick Find view to know which fields to index. Without this, even if the entity is enabled for search, no data is indexed. This is the missing step in the scenario.

The Ribbon Workbench is the standard tool for customizing command bar buttons in model-driven apps. It allows you to add a button and define enable rules that control visibility based on form state, such as the case status. An enable rule can use a JavaScript function or a value rule to check if the status is Active. This meets the requirement without custom code beyond the rule logic.

Parent-child case closure settings define the behaviour applied when a parent case reaches a terminal status, automatically resolving its active child cases. Configuring this satisfies the requirement directly, without custom workflows or plugins, because the platform applies the closure cascade natively.

Round robin assignment distributes work items evenly among available agents in a rotating fashion. This method is designed to balance the workload over time, ensuring each agent gets a similar number of cases, which matches the manager's requirement.

The 'First Response By' KPI is engineered to track the duration from the moment a case is created until the first response activity is generated. This is the precise metric required to enforce responsiveness standards, ensuring that agents prioritize acknowledging new cases within the defined timeframe in the SLA policy.

The Command Designer is the official, low-code tool provided by Microsoft for updating command bars. It allows for the easy addition of buttons with associated Power Fx logic, making it the standard and most efficient way to extend the workspace interface while ensuring the changes remain supported and easy to manage.

A workstream defines the routing logic for a specific channel or entity. Within it, a routing rule set contains rules with conditions. To route based on priority and location, you must create a workstream and add a rule set with those conditions. This is the foundational step to evaluate case attributes and direct them to the appropriate queue.

Automatic record creation and update rules are designed to convert incoming activities like emails into cases. You can configure the rule to set the case title from the email subject and include the email body as a note. This is the native, supported method for email-to-case automation, ensuring consistent case creation without custom development.