Reference:
https://docs.microsoft.com/en-us/power-platform/admin/create-users
https://docs.microsoft.com/en-us/dynamics365/customer-service/create-operating-hours?tabs=customerserviceadmincenter

Reference:
https://docs.microsoft.com/en-us/dynamics365/customer-service/search-knowledge-articles-csh#knowledgebase- search-control

Reference:
https://docs.microsoft.com/en-us/dynamics365/customer-service/routing-work-distribution-oca
Topic 2, Humongous Insurance
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.

Reference:
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customer-service/set-up-queuesmanage-activities-cases