Microsoft MB-230 Practice Test - Questions Answers, Page 4

A confirmation section must be added before the resolve section.

Example: Add an on-demand action to a business process flow.

The Dynamics 365 (online), version 9.0 update introduces a business process flow feature: business process flow automation with Action Steps. You can add a button to a business process flow that will trigger an action or workflow.

Reference:

https://docs.microsoft.com/en-us/power-automate/create-business-process-flow#add-an-ondemand-action-to-a-business-process-flow

Cases that come in as phone calls must be resolved with seven business days.

Cases that come in as emails must be resolved within three business days.

Note: Service-level agreements (SLAs) enable businesses to track support policies and ensure customers are being supported per the support policy to which they are entitled. Businesses use SLAs to govern support products that customers either receive as part of their purchase or add on to their purchase. SLAs include policy details such as how quickly a customer is entitled to receive support, how many support requests a customer can make, and how long after purchases a customer can be supported as part of the agreement.

Note 2: Create SLAs to define conditions and actions that are applicable when an SLA is applied to an entity. The following steps are involved in creating the SLA:

Create an SLA.

Create an SLA item.

Configure actions for the SLA item.

Activate the SLA.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customer-service/define-service-level-agreements

Box 1: Email the knowledge base article to the customer

Support representatives must use the knowledge base first to try to solve issues.

The knowledge base article that is used to resolve a case must always be sent to the customer.

Box 2: Link to resolved case

Support representatives must be able to reference the knowledge base when it is used to resolve the case.

Box 3: Create a knowledge base article

If the answer is not in the knowledge base, a support representative needs to create a knowledge base article.

Box 1: Record Creation and Update rule Reduce the need for manually creating cases from incoming emails and increase the efficiency of customer service agents by creating automatic case creation rules in Dynamics 365 Customer Service.

Box 2: Routing Rule Unified routing is an intelligent, scalable, and enterprise-grade routing and assignment capability that can direct the incoming work item to the best-suited queue and agent by adhering to work item requirements and matching them with the agent's capabilities.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customer-service/automatically-create-case-fromemail

https://docs.microsoft.com/en-us/dynamics365/customer-service/overview-unified-routing

Box 1: 25

Customers must have contracts that allow them to call Lamna Healthcare 10 times a year for help.

In addition to the 10 free calls, customers must be able to send 15 emails a year for support.

If you want to restrict support through the phone channel to 80 hours and email to 20 hours, create individual entitlement channel records and add their total terms.

Box 2: Entitlement Channel

The Entitlement Channel section specifies the support channel through which the customer can reach the organization and seek support.

Use this section to define the channels your customers are entitled to and track the customer support term for each channel. For example, you can add phone and email as the channels through which you'll offer support. If you want to restrict support through the phone channel to 80 hours and email to 20 hours, create individual entitlement channel records and add their total terms.

Box 3: Auto-calculate

The remaining term is auto-calculated and shows the total number of hours or cases remaining for the customer's entitlement.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customer-service/create-entitlement-definesupport-terms-customer

Box 1: Private

Miscellaneous queues must be visible to everyone

The other queues must be visible only to the appropriate department.

In Customer Service, you can create two types of queues:

Private queues: Create with limited set of members to help those members easily view the queue items in that queue. Private queues streamline queue items for the members of that queue only and help to remove clutter from other user's views.

Public queues: Create to let everyone in the organization view the queue and all of its items.

Box 2: Public

Miscellaneous queues must be visible to everyone.

Reference:

https://docs.microsoft.com/en-us/dynamics365/customer-service/set-up-queues-manage-activitiescases

Box 1: Interactive dashboard

Support representatives must have a real-time view of cases assigned to them, including the status of each case.

What is an interactive dashboard?

An interactive dashboard is a data visualization tool that allows business teams to track, analyze, and display metrics of various sorts. Dashboards feature charts, tables, maps, and other visualizations to help viewers understand the story the data tells.

Box 2: Chart by account

Support representatives must be able to see a graphic view of cases by customer that are assigned to them.