CCNA Manage Cases Customer Service Questions

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Power Automate is the most flexible and robust tool for triggering automated notifications. By using a 'When a row is modified' trigger, the flow can evaluate the escalation field and immediately send an email to the correct manager, meeting the business requirement for timely and proactive notification.

Automatic record creation rules are specifically designed to convert incoming activities like emails into cases. They allow for mapping fields, applying filters, and triggering workflows. This is the out-of-the-box, recommended method for ensuring that all incoming customer emails are converted into trackable work items within the system.

The 'Resolve by' KPI measures the time from case creation until the case is resolved. Setting a pause condition on the status 'On hold' will pause the timer when the case is on hold and resume when the status changes. This meets both requirements. The SLA KPI will track the elapsed time excluding the paused periods.

A subgrid on the case form can display cases filtered to the same customer, using a related view. Clearing the allow editing setting makes the subgrid read-only, so agents can see repeat contacts without modifying those records. This satisfies both requirements: visibility of related cases and prevention of edits directly from the form.

A business rule on the case table can set field values based on conditions, such as populating the entitlement lookup when the customer field is filled. This runs in the form without code and can also set the product field, reducing manual entry. Business rules are the supported no-code way to drive field values during case creation.

Merge Cases is a built-in feature in Dynamics 365 Customer Service that allows users to combine multiple cases into one. The representative can select the cases to merge and choose which one becomes the primary case. The activities and notes from the other cases are consolidated. This directly meets the requirement to merge related cases.

Similar Cases is a feature in Dynamics 365 Customer Service that uses text analysis to find cases with similar subjects and other fields. It helps agents quickly reference previously resolved cases with the same issue. By using Similar Cases, the agent can see a list of cases that match the current case's product and subject, enabling faster resolution based on past solutions.

The Customer Service admin center provides a setting to automatically close cases after a specified number of days of inactivity. This is a built-in feature that respects case status and can be enabled without custom development, directly fulfilling the requirement.

The error code 'InsufficientPrivileges' directly points to a security role deficiency. By navigating to the Security Roles section and granting the agent the necessary 'Write' and 'Publish' permissions for the Knowledge Article entity, the agent will gain the required access level to perform the action successfully.

The Customer Service workspace is a unified agent interface that includes the case form, timeline, knowledge search, and similar cases. It allows agents to view all relevant information in one place and quickly reference past resolutions. This is the designated feature for enhancing agent productivity in Dynamics 365 Customer Service.

A workflow can be triggered on the escalation action or status change of the original case. It can create a new case record, copy relevant information, and assign it to the specialist team. This approach keeps the original case open and separate, ensuring both cases are tracked independently.

Similar Cases is a feature in Dynamics 365 Customer Service that uses text analytics to suggest cases with similar titles and descriptions. When enabled, it displays a list of similar cases on the case form, helping agents find relevant resolutions. This directly meets the requirement. Enabling this feature is a simple configuration in the Customer Service Hub settings.