Introduction to Microsoft Dynamics 365 Customer Consultant Flashcards

You are setting up a case entity's business process flow. Every case needs to be marked for inspection. The business process flow configuration has to be finished. Solution: Change the action's input parameter type to Option set. Is the aim being met by the solution?

Answer: No

No, changing an action's input parameter type to Option Set does not inherently mark every case for inspection. An Option Set merely defines a list of choices for a field. To ensure every case is marked for inspection, you would need to add a specific field (e.g., an Option Set or Two Options field) to the case entity and then incorporate a step in the BPF that requires users to select an inspection status or triggers an action based on it.

For a case entity, you are setting up a business process flow. A review flag must be placed on each case. The business process flow needs to be configured in its entirety. Solution: Create an action that adds the text Ready for review to the case subject and creates a task record with the case reviewer's assignment on it. If so, does it achieve the desired result?

Answer: Yes

Yes, this solution achieves the desired result. By creating an action within the business process flow that modifies the case subject to include 'Ready for review' and simultaneously creates an assigned task for a reviewer, each case is effectively flagged for inspection. This approach ensures both a clear visual indicator on the case record and a traceable action item for the review process.

Business process flows must be developed. What three entities are you able to use?

Answer: Case

Business Process Flows (BPFs) in Dynamics 365 are versatile tools that can be applied to various entities to standardize workflows. The Case entity is a primary example, as BPFs are crucial for guiding customer service agents through the resolution process. BPFs can also be used with other out-of-the-box entities like Social Activity and Letter, which are types of activities, to manage their specific lifecycles and ensure consistent handling.

Dynamics 365 Customer Service is employed by a business. You are setting up sophisticated similarity rules. Making an exact match for the Modified On field in the Match Fields tab allows you to construct a similarity rule on cases. You put the rule to the test and find that no exact matches show up. You must ascertain the cause of the rule's failure. What are the two potential causes for the rule's failure?

Answer: The Modified On field is not set to searchable in the customization of the case entity in the solution.

When a similarity rule fails to find exact matches on a field like 'Modified On', two common causes are that the field is not configured for searching or the rule itself is inactive. For similarity rules to function correctly, the fields they evaluate must be marked as 'Searchable' in the entity's customization settings. Additionally, if the similarity rule is deactivated, it will not execute and therefore cannot return any matches.

You work as a help desk agent for a company that makes use of Dynamics 365 Customer Service. Users must look for related cases within the system. The default settings haven't been altered in any way. Which search options are accessible by default must be determined. Which two search options are offered?

Answer: Quick Find

By default, Dynamics 365 Customer Service provides users with two primary search options: Quick Find and Advanced Find. Quick Find offers a simple search bar to rapidly locate records within a specific entity view. Advanced Find provides more robust querying capabilities, allowing users to construct complex searches across multiple entities with detailed criteria, whereas Relevance Search requires explicit enablement and configuration.

For a consumer, you establish a default entitlement. You must make sure that a case is automatically associated with the default entitlement. What are the two potential means through which this can be done?

Answer: Update the customer, contact, or product field on an existing case

To automatically associate a case with a default entitlement, there are two main methods. Firstly, when a new case is created, if the associated customer (account or contact) or product has a default entitlement, it will be automatically applied. Secondly, if an existing case's customer, contact, or product field is updated to one that has a default entitlement, the system will also attempt to associate that entitlement.

The administrator of Dynamics 365 Customer Service, you. Cases are created automatically from emails. Emails are reportedly no longer being turned into cases, according to users. What might be the reason?

Answer: The workflow process has been deactivated

If emails are no longer being automatically converted into cases in Dynamics 365 Customer Service, a very common reason is that the underlying workflow process or Automatic Case Creation rule has been deactivated. These processes are responsible for monitoring incoming emails and initiating case creation based on predefined conditions. If the process is not active, it cannot execute, leading to a halt in automatic case generation.