MB-230 Microsoft Dynamics 365 for Customer Service Questions and Answers

Box 1: Two

You must create two types of Omnichannel queues: regular and escalated.

Box 2: Add a routing rule for a push on owner assignment in Omnichannel

Tickets assigned to a representative must be automatically placed in that representative's queue.

A customer initiates a conversation from the portal, and the conversation reaches the Omnichannel system. Now, based on the routing rules condition defined in the routing system, it starts routing the conversation to the appropriate queues.

When the conversation reaches to the queues, the work assignment system assigns the conversation based on triggers.

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.

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.

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.

Step 1: In Service Management, create a Routing Rule set.

Scenario: If a case is open more than 30 days, the case must automatically be routed to the supervisor.

Create routing rulesets to route cases.

Use routing rules in Customer Service to route cases to the right agents at the right time without any manual intervention. You can also use routing rules to route cases that are escalated to specific queues.

Step 2: Enter Name, Select Save, and select the plus sign to add a rule item

On the General tab, in Routing Rule Set Information, Enter Name and Description for the routing ruleset.

Select Save. The routing ruleset is saved, and the Rule Items section is displayed.

In the Rule Items section, select the Add Rule Item button + to specify conditions for routing cases to a queue.

Step 3: Add conditions

Under Then Conditions, specify the queue to which the cases will be routed or the user or team to which the cases will be assigned if the conditions in the If Conditions section are met.

Step 4: Save and activate.

Select Save and Close.

In the routing ruleset record, select Activate so that the ruleset is applied to the cases matching the conditions in the rule.

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.

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.

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.

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.

Customer Service Insights is now embedded in Dynamics 365 Customer Service. After it is enabled, this experience allows you to start seeing historical analytics directly within the Customer Service environment. Several reports and dashboards can be viewed by your management team.

An email alert must be sent to representatives for SLA violations as follows: HMO 2 hours prior and PPO 1 hour prior.

Box 1: Automation

The automation dictionary maintains the contextual data for sessions. You can use the keys from the automation dictionary to pass the parameter in an action.

While creating templates and macros in the admin app, you can pass parameter keys such as title of a session, title of notification, title of an application tab template, and custom parameter values for application tab types. These keys are replaced based on the contextual information available at the time of execution.

Box 2: Macro

Automate tasks with macros

Overview of macros

In the customer service industry, agents have to click often to perform simple tasks, such as open a form, fill, and save it, and many repetitive and monotonous actions, such as greeting and verifying a customer, sending acknowledgment mail, and taking notes. These clicks and repetitive tasks can lead to human errors when agents copy and paste the data across different operations.

Macros are a set of sequential actions that are performed by a user. They enable users to perform daily operations efficiently in a fast and process-compliant manner. You can reuse macros with different sessions based on the context parameters that are specific to the session.

The value propositions of the macros are as follows:

Automate repetitive and monotonous tasks with a single click.

Minimize human errors.

Adhere to business processes.

Lower average handling time.

Improve customer satisfaction.

Create contextual and reusable macros.

Box 1: Countall

COUNT (Azure Stream Analytics) returns the number of items in a group. COUNT always returns a bigint data type value.

Syntax:

-- Aggregate Function Syntax

COUNT ( { [ [ALL | DISTINCT] expression ] | * } )

Arguments:

ALL - Applies the aggregate function to all values. ALL is the default.

Box 2: Share the personal chart and add the user giving each one read permission

Apply SLAs on demand.

With the enhancements made to SLAs, you can now apply SLAs to records manually. You can also automatically apply SLAs to records based on your business logic by using workflows or custom plug-ins.

Box 1: Omnichannel supervisor

Case managers schedule shifts and are a point of escalation.

Omnichannel supervisor: Required for performing supervisor tasks.

Businesses need to monitor and manage the efficiency levels of agents in their ongoing conversations with customers. The enhanced supervisor experience provides supervisors with timely insights and metrics on the efficiency of the service delivery of agents and opportunities to help agents deliver better support to customers.

In this enhancement to the supervisor experience in Omnichannel for Customer Service, supervisors can:

Drill down to specific agents and look at their operational metrics.

Manage agent availability remotely.

Box 2: Omnichannel agent

Case representatives handle incoming calls, provide information to patients for appointments, and schedule follow-up calls with doctors. Case representatives can also help with people who want to chat online.

Omnichannel agent: Required for performing agent tasks.

As an Omnichannel agent, you can use queues to manage the work items that are assigned to you via queues. Therefore, you can focus on the tasks at hand and ensure better customer service. The application empowers you to work on simultaneous conversations with multiple customers. You get a holistic view of a customer's data and can see the details of the customer's previous interactions. In this way, you can be sure that you have all the available information that you might need to resolve the customer's issue.

Box 3: Productive tools user

Customer satisfaction representatives monitor all activity and ensure that there is a uniform process for all calls.

Productivity tools user: Required by users of Dynamics 365 Productivity Tools.

Agent productivity tools use intelligence and automation to enable agents to find answers to customer questions and help resolve customer issues quickly, thereby improving satisfaction in service delivery.

Incorrect:

Not Productivity tools administrator:

Productivity tools administrator: Required by administrator users of Dynamics 365 Productivity Tools.