Erläuterung

Erläuterung
Step 1: Create a new ruleset in a workstream.
To create a logical work classification ruleset, do the following steps:
1. In Customer Service admin center, Omnichannel admin center, or Customer Service Hub, select a workstream, and in the Routing rules area, for the Work classification (optional) option, select Create Ruleset.
2. On the Work classification page, select Create new, and in the Create work classification ruleset dialog, select Logical rules in Rule type, and enter a name and description. By default, the root record is selected and displayed at the top of the condition builder for ease of reference and visibility of the record for which you are creating the rule.
Step 2: Create a new manual rule named Bronze.
3. In the Decision list area, select Create Rule, and on the Create work classification rule dialog, enter a name.
Step 3: Create a condition for the Bronze rule.
4. In the Conditions area, define the conditions according to your business needs. If you are creating classification rules for records, then the top-level condition is automatically populated. You can define conditions for up to two levels of the related records and attributes.
5. In the Output area, select the attribute for which value needs to be set if the conditions are met.
6. Repeat steps 3 through 5 to create the demand rules.
Step 4: Create a rule named 5-hour response from the decision list.
Step 5: Create a demand rule for the Bronze rule.
Referenz:
https://docs.microsoft.com/en-us/dynamics365/customer-service/configure-work-classification

Erläuterung

Erläuterung

Referenzen:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customer-service/define-service-levelagree

Erläuterung
Graphical user interface, text, application Description automatically generated

Referenz:
https://docs.microsoft.com/en-us/dynamics365/customer-service/resources-service-scheduling

Erläuterung
Graphical user interface, application Description automatically generated with medium confidence

Box 1: Resources
Establish a one-step process to send a predefined email to customers once a representative is done helping them.
Box 2: Security roles
Ensure that representatives ask predefined questions to identify a customer before troubleshooting a case.
Assign a security role
Security roles control a user’s access to data through a set of access levels and permissions. The combination of access levels and permissions that are included in a specific security role sets limits on the user’s view of data and on the user’s interactions with that data.
Box 3: Working hours
Have chatbots available to help make recommendations in typed conversations.
Operating hours define the hours when your organization’s customer support team is active and available to serve customers. By setting up operating hours, you help your customers and your organization work together to resolve issues.
The operating hour schedules cater to the following scenarios:
Display the non-availability of customer support on public holidays that are otherwise operating hours.
Accommodate change of calendar timings for daylight saving time twice an year for timezones that have implemented the daylight saving time.
*-> Set up separate schedules for agents, bots, and queues to cater to different business scenarios and product lines seamlessly for any channel.
Define schedules to transition customer queues from bots to agents.
Customize the display and other settings of the chat widget during non-business hours.
Referenz:
https://docs.microsoft.com/en-us/power-platform/admin/create-users
https://docs.microsoft.com/en-us/dynamics365/customer-service/create-operating-hours?tabs=customerservicead

Referenz:
https://docs.microsoft.com/en-us/dynamics365/customer-service/oc-monitor-real-time-customer-sentimentsessio
Topic 2, Humongous Insurance
Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the button to return to the question.
Background
Humongous Insurance is contracted to process all insurance claims for a health facility that accepts the following types of health insurance:
* Health maintenance organization (HMO)
* Preferred-provider organization (PPO)
* Gold
Cases are classified as new claims, claim disputes, and follow-ups. Each insured person is entitled to open 25 new cases each calendar year.
Support representatives specialize by and process claims by insurance type.
Humongous Insurance currently accepts claims only by telephone. The call center is open from 06:00 GMT to
24:00 GMT daily. Call center staff work one of the following shifts: 06:00 GMT to 12:00 GMT, 12:00 GMT to 18:00 GMT, and 18:00 GMT to 24:00 GMT.
When a case is received by email, a staff member categorizes the case as email and closes the case immediately.
Current environment
* Humongous Insurance has three departments to handle claim types: HMO, PPO, and Gold.
* The company uses handwritten forms to send claims information to the correct department.
* Each department maintains a workbook to record calls received.
Requirements. Support desk
* Configure the system to track the number of insurance claims filed each year.
* Categorize claims by type as they are opened.
* Configure the system to track staff responsiveness to service-level agreements (SLAs).
* Ensure that business hours reflect the hours that support staff are scheduled.
Requirements. Case handling
* All new cases must be automatically placed into a queue based on insurance type after the type is selected.
* All insurance types need to be automatically moved to the proper queue when the subject is picked.
* All cases must be created and closed immediately when received.
* The status reason must be set to Email Sent or Phone Call.
* Information must be restricted by insurance and phone call type.
* Managers must be alerted when customers reach their limit of 25 cases for the year.
* Changes to cases must not be counted against entitlements until the case is closed.
Requirements. Disputes
* Claim disputes must be categorized as low priority.
* The status for all disputed cases must be set to Review by a Manager before a disputed case may be closed.
Requirements. Knowledge base
* A knowledge base must be used as a repository for all answers.
* Representatives must be able to search the knowledge base when opening a new case for similar claims.
* Representatives must be able to search across all entities at all times.
* Searches must check any field in the entity for matches in a single search.
* Searches must return results in a single list and sort the list so that the most relevant results appear at the top of the list.
* Representatives must be able to link the knowledge base to cases when applicable.
* Representatives must create a new knowledge base article if an answer is not found in the existing knowledge base.
* Representatives must be able to use SQL-like syntax to search the knowledge base.
Requirements. Service-level agreements
When a customer calls to open a claim, the company must respond to the caller within the following time frames:

Requirements. Alerts
* Cases must be flagged when they are past the SLA threshold.
* An email alert must be sent to the manager to indicate an SLA noncompliance.
* An email alert must be sent to representatives for SLA violations as follows: HMO 2 hours prior and PPO 1 hour prior.
* Send an email alert to support managers when disputes are ready to be closed.
* Send an email alert to customers when cases are closed.
Requirements. Issues
* The current process is all manual and not efficient.
* There is no easy way to determine whether the company is meeting its SLAs.
* Representatives are often inconsistent regarding how they handle customers and answer customer questions.
* There is no accountability for any of the representatives who take calls.

Omni-channel: An omni-channel solution offers two or more channel experiences to customers, and the customer experience is consistent across channels. The context of the case and customer is used to streamline the experience across apps. For example, a customer starts on a self-service portal but then starts a chat conversation. All the pages that the customer has opened are available to the agent.
By providing multi-channel or omni-channel solutions to your customer, you help guarantee that each customer can interact with your organization by using the option that’s best for him or her. When you provide multi-channel or omni-channel solutions, you must also consider the effect on the organization. Although it’s important to make sure that customers have a consistent experience when they work with the different channels, it’s also important to remember that each channel is different.
Referenz:
https://www.globalits.bh/how-customer-service-can-handle-entitlement-channels-in-dynamics-365/

Erläuterung
Graphical user interface, text, application Description automatically generated

Referenz:
https://docs.microsoft.com/en-us/dynamics365/customer-service/resources-service-scheduling

Erläuterung
Graphical user interface, application Description automatically generated with medium confidence

Box 1: Resources
Establish a one-step process to send a predefined email to customers once a representative is done helping them.
Box 2: Security roles
Ensure that representatives ask predefined questions to identify a customer before troubleshooting a case.
Assign a security role
Security roles control a user’s access to data through a set of access levels and permissions. The combination of access levels and permissions that are included in a specific security role sets limits on the user’s view of data and on the user’s interactions with that data.
Box 3: Working hours
Have chatbots available to help make recommendations in typed conversations.
Operating hours define the hours when your organization’s customer support team is active and available to serve customers. By setting up operating hours, you help your customers and your organization work together to resolve issues.
The operating hour schedules cater to the following scenarios:
Display the non-availability of customer support on public holidays that are otherwise operating hours.
Accommodate change of calendar timings for daylight saving time twice an year for timezones that have implemented the daylight saving time.
*-> Set up separate schedules for agents, bots, and queues to cater to different business scenarios and product lines seamlessly for any channel.
Define schedules to transition customer queues from bots to agents.
Customize the display and other settings of the chat widget during non-business hours.
Referenz:
https://docs.microsoft.com/en-us/power-platform/admin/create-users
https://docs.microsoft.com/en-us/dynamics365/customer-service/create-operating-hours?tabs=customerservicead

Erläuterung

1 – Create a knowledge article
2 – Mark the knowledge article for review
3 – Approve the article
4 – publish the article
Referenzen:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customer-service/customer-service-hubuser-guide-knowledge-article