Manage Cases in Customer Service practice questions

Modify the Case form XML to remove the resolution dialog and replace it with a custom business process flow stage.

Why it fails: Replacing the native case resolution dialog with a business process flow stage disrupts the standard system closure mechanics, leaving legacy cases vulnerable to closure without capturing mandatory billing or resolution categorization data.

Configure the SLA item associated with the case to automatically resolve records and populate resolution notes upon expiration.

Why it fails: Service Level Agreements govern time-bound performance targets and warning indicators, but they do not automatically synthesize resolution notes or handle the structured data entry required when agents manually close active support tickets.

Create a unified routing rule set that automatically cancels cases that lack resolution descriptions after 48 hours.

Why it fails: Routing rules focus on assigning records to appropriate queues, agents, or teams based on defined criteria. They lack the capability to evaluate data completion status for closure or execute automated cancellations based on missing notes.

Queue assignment rules

Why it fails: Queue assignment rules are outdated legacy components. They do not integrate with the modern Unified Routing framework, which uses workstreams and classification rules. Relying on these rules prevents the use of advanced features like capacity profiles and intelligent skill-based routing, leading to a less effective routing strategy for modern service teams.

Service Level Agreement (SLA) items

Why it fails: SLAs define the timeline for performance, not the routing logic for work distribution. Configuring an SLA will track compliance but will not move the case to the appropriate queue. Using SLAs for routing is a misuse of the feature, as it does not address the fundamental need to direct traffic.

Case resolution dialogs

Why it fails: Case resolution dialogs are triggered when an agent closes a case, allowing them to capture summary information or resolution codes. They have no impact on the initial assignment or routing of a case to a specific team. This functionality occurs at the end of the case life cycle, not the beginning.

Business Hours

Why it fails: Business hours define the operational time during which SLA timers run. While they are crucial for setting the working schedule, they cannot pause a timer based on a specific event like a customer response delay. They are static definitions of operational capacity rather than dynamic event-based control mechanisms.

Routing Rule Sets

Why it fails: Routing rule sets are used for determining which queue or agent receives a work item. They are not involved in managing the lifecycle of an SLA timer. Configuring routing rules will not have any effect on whether an SLA timer pauses or continues, as they serve entirely different functional purposes.

Case Merge settings

Why it fails: Case Merge settings determine how duplicate cases are combined into a single master record. This feature is unrelated to SLA timer management and does not influence the countdown logic. Using merge settings to manage wait times is not possible because they lack any logic related to SLA compliance or timer states.

Knowledge management settings

Why it fails: While knowledge management is important for overall case resolution, it is not a prerequisite for the technical display of the productivity pane itself. You can have a functional productivity pane without even enabling the knowledge base, as the pane's infrastructure is independent of the knowledge article entity configuration.

Queue routing rules

Why it fails: Queue routing rules are used for assigning incoming cases to specific queues. They are a backend process that occurs before an agent even opens the case record. Therefore, they have no impact on the configuration or the runtime behavior of the UI-based productivity pane used by the agents.

SLA policies

Why it fails: SLA policies manage the timing and compliance aspects of case management. While they might show up as information within a case form, they are not a technical dependency for the productivity pane to exist or be configured. The productivity pane's framework is independent of the SLA policy configuration.

Knowledge article

Why it fails: Knowledge articles are for information sharing, not for feedback collection. They provide answers to customer questions but have no functionality related to survey distribution or response tracking. Including them in the list of required components for an automated survey implementation is technically incorrect and irrelevant to the goal.

Queue routing rules

Why it fails: Queue routing rules are for assigning work, not for distributing surveys. They operate at the start of a case lifecycle and have no role in the resolution or post-resolution stages. Using them here demonstrates a misunderstanding of the functional roles of different Customer Service components in the platform.

Case Topic

Why it fails: Case Topics are used for analytical categorization, not for work distribution. They allow reporting engines to group cases by subject for trend analysis but do not provide the routing or organization capabilities required to manage the actual workflow of a support team effectively.

Account

Why it fails: An Account is a business entity representing a customer organization. While cases are linked to accounts, they are not grouped *by* accounts for the purpose of operational routing. Managing work based on accounts would be inefficient, as agents need to handle tasks based on support priority and expertise.

Knowledge Base

Why it fails: The Knowledge Base is a library of reference articles used to resolve cases. It is not an organizational structure for the cases themselves. Using the knowledge base as a case bucket would lead to severe process failures, as it lacks any functionality for task assignment or work item tracking.

Assign to a queue

Why it fails: Queues are for case management, not knowledge article management. Assigning an article to a queue serves no functional purpose in the lifecycle and would be a confusing practice for content owners. Knowledge lifecycle actions are managed through status transitions, not via the assignment logic used for work items.

Merge article into case

Why it fails: Merging articles is not a supported or logical operation. Articles exist as independent records of truth. While an article can be associated with or suggested for a case, merging them into a case record would destroy the structured data and make the knowledge content inaccessible for future use.

Customer service schedule calendars

Why it fails: Customer service schedule calendars define working hours, holidays, and support availability for service-level agreements and entitlements. They are not required components for the fundamental operational setup of unified routing record rules.

Parent-child case relationship controls

Why it fails: Parent-child case relationship controls dictate how status changes cascade between master cases and associated sub-cases. They operate independently of the unified routing engine and are not prerequisites for directing new work.

Customer voice survey metrics

Why it fails: Customer voice survey metrics capture post-interaction customer satisfaction feedback and CSAT scores. They are used for reporting and analytics purposes after cases close rather than driving the initial routing logic.

Define case merge settings to specify the maximum number of child cases that can be associated with a single master case record during consolidation.

Why it fails: Case merge functionality consolidates duplicate records by merging activities, notes, and specific fields into a designated master case, but it does not enforce a configurable limit on the number of associated child cases. Administrators manage child case hierarchies through parent-child case settings rather than merge threshold configurations.

Set up unified routing diagnostic tools to manually override automated rule evaluation orders whenever an agent rejects an incoming case assignment.

Why it fails: Unified routing diagnostics provide visibility into why a record was routed in a specific manner, but they do not support manual rule-order overrides triggered by agent rejections. Rejected cases typically return to the queue or trigger exception workflows according to predefined routing rule setups rather than diagnostic overrides.

Enable automatic SLA pause conditions within the case merge settings to temporarily stop countdown timers while duplicate records are being evaluated.

Why it fails: Service Level Agreement pause conditions are managed independently within SLA KPI configurations and service calendars rather than case merge settings. Mixing merge rules with SLA logic would introduce unpredictable timer behaviors and violate standard compliance tracking frameworks for customer service metrics.

Case Resolution dialog with required fields

Why it fails: The Case Resolution dialog allows you to require certain fields before resolving a case, but it does not automatically create follow-up activities based on the resolution status. It only enforces data entry, not subsequent actions. To trigger a follow-up activity, you need a workflow or business rule that reacts to the resolution status change. This option does not meet the requirement of automatically prompting for a follow-up activity.

SLA KPI that tracks cases with resolution status 'Not Resolved'

Why it fails: SLAs track time-based performance against service level agreements; they do not trigger the creation of follow-up activities. An SLA KPI can monitor cases but cannot create tasks or prompt agents. The requirement is to automatically prompt for a follow-up activity, which is an action, not a measurement. Thus, an SLA KPI is not the appropriate feature.

Business rule that displays a prompt when the resolution status is 'Not Resolved'

Why it fails: Business rules can show messages or set field values based on conditions, but they cannot create new activity records. They are limited to client-side actions on the current record. To create a follow-up task, a workflow or Power Automate flow is required. Therefore, a business rule alone cannot automatically create the follow-up activity as required.

Add a custom field to the Case entity for resolution notes and add it to the case form.

Why it fails: Adding a custom field allows manual entry of resolution notes, but it does not integrate with the resolution process or automatically capture details. It also does not provide a mechanism to reuse resolutions for similar cases. The built-in Case Resolution dialog is designed specifically for this purpose and includes knowledge article creation.

Create a business rule that requires the Resolution field to be populated before the case can be resolved.

Why it fails: A business rule can enforce that a field is populated, but it does not provide the resolution dialog or automatically capture resolution details. It also does not facilitate reusing resolutions for similar cases. While it could enforce data entry, it lacks the integrated resolution experience and knowledge article creation that the Case Resolution dialog provides.

Configure a workflow that sends an email to the customer with the resolution text.

Why it fails: A workflow can send an email, but it does not capture resolution details in a structured way or enable reuse of resolutions. It addresses communication, not the core requirement of capturing and reusing resolution information. The Case Resolution dialog is the appropriate feature for capturing and reusing resolution details.

Power Automate flow that sends an email with a survey link when the case status changes to Resolved.

Why it fails: While a Power Automate flow can send an email with a survey link, it does not automatically prompt the agent to complete a survey within the case resolution process. The requirement specifies that the system should prompt the agent, which is better achieved with an integrated survey solution.

Case resolution dialog with a custom field for survey feedback.

Why it fails: Adding a custom field to the case resolution dialog does not automatically prompt the agent to complete a survey. It simply adds a field, but the survey would need to be manually filled out. The requirement is for an automatic prompt, which is not met by this approach.

Unified routing rule that assigns the case to a survey team upon resolution.

Why it fails: Unified routing rules are used to route cases to queues or agents based on conditions. They do not trigger surveys or prompt agents for feedback. This option misuses the routing feature and does not fulfill the requirement of automatically prompting for a survey upon resolution.

Set up a server-side synchronization rule to convert emails to cases.

Why it fails: Server-side synchronization is used to synchronize emails, appointments, and tasks between Dynamics 365 and Exchange. It does not convert emails to cases. The Email to Case feature is the correct mechanism for automatically creating cases from emails. Server-side sync only ensures email records are available in Dynamics 365.

Configure a queue that automatically creates cases from emails.

Why it fails: Queues are used to hold work items, including cases and emails, but they do not automatically create cases from emails. Queues can route items to agents, but case creation from emails is handled by the Email to Case feature. Queues alone do not provide the automation required.

Create a Power Automate flow that triggers on new emails and creates cases.

Why it fails: While Power Automate can be used, it is not the out-of-the-box feature for email-to-case. The native Email to Case feature provides a no-code configuration with built-in matching and title setting. Using Power Automate would require custom development and may not handle all the built-in logic such as customer matching and case creation rules.

Use a workflow that triggers on email creation and creates a case record.

Why it fails: While a workflow can create a case from an email, it is a custom approach and does not leverage the built-in email-to-case feature. Workflows are asynchronous and may not handle attachments or conversation threading as effectively. The native configuration is simpler and more maintainable. Therefore, a workflow is not the recommended solution here.

Set up a server-side synchronization rule to convert emails to cases.

Why it fails: Server-side synchronization is used to synchronize emails, appointments, and tasks between Dynamics 365 and Exchange. It does not convert emails into cases. The conversion is handled by the email-to-case feature, which is configured separately. Thus, server-side synchronization alone cannot achieve the desired automatic case creation with field mapping.

Create a Power Automate flow that triggers on email creation and creates a case with mapped fields.

Why it fails: A Power Automate flow can create cases from emails, but it is not the native method and requires additional configuration. The out-of-the-box email-to-case feature already handles this mapping without custom flows. Using Power Automate would add unnecessary complexity and potential points of failure. The requirement is best met with built-in settings, not custom automation.

Set the SLA KPI's 'Stop when case status' to Escalated.

Why it fails: There is no 'Stop when case status' setting for SLA KPIs. The available options are typically to pause or cancel the timer based on conditions. Using a non-existent setting would not achieve the desired behavior, and the timer would continue to run.

Create a workflow that cancels the SLA when the case status changes to Escalated.

Why it fails: While a workflow could be used to update the case and potentially interact with the SLA, it is not the standard method to stop an SLA timer. The SLA KPI itself must be configured to pause or cancel based on status. A workflow would be an indirect and less reliable approach.

Set the SLA KPI's 'Cancel when case status' to Escalated.

Why it fails: Canceling the SLA KPI would remove the KPI from the case entirely, which is different from pausing the timer. The requirement is to stop the timer from running, not to cancel the KPI. Canceling would also prevent any further tracking, which may not be desired.

Case resolution dialog with a required field for activity status.

Why it fails: Adding a required field for activity status in the case resolution dialog would not automatically check for open activities. The agent would have to manually verify and update the field. The requirement is for an automatic check, which this approach does not provide.

A plug-in registered on the Resolve message that throws an exception if open activities exist.

Why it fails: A plug-in can indeed prevent resolution by throwing an exception, but it requires custom code development, which is more complex than using a business rule. The scenario does not specify a need for custom code, and a business rule is a simpler, no-code solution that achieves the same result.

A Power Automate flow that cancels the resolution if open activities exist.

Why it fails: A Power Automate flow can be triggered on case resolution, but it cannot prevent the resolution from occurring in the first place. It would run after the fact, which does not meet the requirement of preventing resolution until activities are closed. Thus, it is not suitable.

Create a business process flow that includes an approval step.

Why it fails: Business process flows guide users through stages but do not provide an automated approval mechanism. While you can add a stage for approval, it does not automatically route the case to a manager or capture approval decisions. The manager would still need to manually review and update the case, which does not meet the requirement for automated routing and direct approval.

Set up a queue that routes the case to the manager and use SLA to track approval time.

Why it fails: Routing the case to a queue for the manager and using SLA to track time does not provide an approval action. The manager would still need to manually review and update the case. SLA tracking is for performance measurement, not for capturing approval decisions. This approach does not meet the requirement for a direct approval mechanism.

Use a workflow that assigns the case to the manager and sends an email notification.

Why it fails: A workflow can assign the case to the manager and send an email, but it does not provide a direct approval mechanism. The manager would need to manually update the case after receiving the email, which is not as efficient or trackable as an automated approval process. The requirement specifies that the manager must be able to approve or reject directly from the case record.

Add a required option set field to the case form for resolution and create a chart for reporting.

Why it fails: Adding a required option set field to the case form does not enforce selection during the resolution process; it only enforces it when the form is saved. The resolution process uses a separate dialog, so this would not prevent closure without a resolution. Also, creating a chart does not automatically track resolution usage; it would require manual data entry and reporting setup, which is not the built-in tracking feature.

Create a business rule that sets the case status to resolved only when a resolution is selected.

Why it fails: A business rule can enforce conditions on form fields, but it cannot control the resolution dialog or the resolve action. The resolve action is a system action that uses the resolution dialog. A business rule on the case form would not prevent an agent from resolving the case without selecting a resolution because the resolution dialog bypasses the form. Therefore, this does not meet the requirement.

Create a resolution activity and add it to the case form.

Why it fails: A resolution activity is automatically created when a case is resolved, but it does not enforce selection of a resolution before closure. The resolution activity records the resolution details, but the requirement is to make the selection mandatory and to track usage. Configuring a resolution activity alone does not provide the mandatory selection or the tracking of frequently used resolutions.

Use a synchronous plug-in on the Case entity that reads the email subject from the regarding field and sets the title.

Why it fails: A plug-in can set the title from the email subject, but it requires custom code and registration. It also may not work reliably if the case is created through other channels. The email-to-case feature is designed specifically for this scenario and requires no code. Plug-ins also add complexity and potential performance overhead.

Create a Power Automate flow that triggers on email arrival and creates a case with the subject as the title.

Why it fails: A Power Automate flow can create cases from emails, but it requires custom configuration and may not handle all email scenarios, such as replies or forwarded messages. It also does not use the built-in email-to-case functionality, which is designed for this purpose. The flow would need to parse the email and map fields, which is more complex than using the native feature.

Create a workflow that triggers on case creation and updates the title with the subject from the associated email.

Why it fails: A workflow can update the case title after creation, but it runs asynchronously by default, so there may be a delay. It also requires that the email is already associated with the case. The email-to-case feature sets the title during creation, providing a better user experience. Workflows are also being replaced by Power Automate, which is more modern.

Set the case resolution activity to close all related activities.

Why it fails: The case resolution activity does not have a built-in option to close all related activities. While resolving a case can prompt the agent to close activities manually, there is no automatic closure of all related activities from the resolution dialog. This configuration does not exist in Dynamics 365 Customer Service, so it would not meet the requirement.

Enable the 'Close all activities' setting in the Customer Service admin center.

Why it fails: The Customer Service admin center does not have a global setting to automatically close all activities when a case is resolved. Such automation requires custom logic, such as a workflow or Power Automate flow. Relying on a non-existent setting would leave open activities unresolved and fail the requirement.

Create a synchronous workflow that runs on case resolution and updates all related activities to closed.

Why it fails: A synchronous workflow on case resolution could close activities, but it would run in the context of the resolving user and might cause performance issues or timeouts. A Power Automate flow is more robust and recommended for this scenario. The workflow approach is technically possible but not the best practice and may not be reliable.