Free PL-200 Exam Dumps Preview

Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible.
Dataverse is set up with the following configuration:
1. The solution prefix 'cs' is used for all new components.
2. Only the root business unit is used.
3. All tables are stored in Dataverse and do not require rapid scaling.
4. Exchange server-side sync is not configured.

Adopters
1. Adopter information is stored in a Contact table.
2. Contacts are considered to be duplicates if they have the same email address and last name.
3. Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
4. The email reminders must not be tracked in the system.

Dogs
1. Dog information is stored in a Dog table, which is organization owned.
2. Breed, size, and weight are fields in the table.

Dog residency
1. A Resident table tracks the stay of each dog.
2. Each resident record has a lookup for the dog and its food.
3. The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
4. A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
5. A formula column named Deposit is automatically populated with 20% of the adoption fee.
6. A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.

Exercise and feedings
1. Exercise for the dogs is tracked in an Exercise table.

2. Feedings are tracked in a Feeding table.
3. Exercise and feeding records appear in a resident record timeline.

Care staff
1. The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
2. The staff must be able to update the weight of a dog on the resident record.
3. The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
4. The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.

Administrate staff
1. Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
2. When an adopter wants to adopt a dog. the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:

Commitment:
1. Obtain adopter signature in a commitment document.
2. Collect deposit

Pre-pickup:
1. Document spay or neutering date.
2. Perform spay or neutering.
3. Document pickup date.

Pickup:
Collect full payment.
Verify dog is picked up.
1. A dog must be picked up no sooner than two days after spaying or neutering.
2. A pop-up window must appear with an error message if the Pickup date is too soon.
3. Only administrative staff must be able to add new adopters and dogs.

Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible.
Dataverse is set up with the following configuration:
1. The solution prefix 'cs' is used for all new components.
2. Only the root business unit is used.
3. All tables are stored in Dataverse and do not require rapid scaling.
4. Exchange server-side sync is not configured.

Adopters
1. Adopter information is stored in a Contact table.
2. Contacts are considered to be duplicates if they have the same email address and last name.
3. Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
4. The email reminders must not be tracked in the system.

Dogs
1. Dog information is stored in a Dog table, which is organization owned.
2. Breed, size, and weight are fields in the table.

Dog residency
1. A Resident table tracks the stay of each dog.
2. Each resident record has a lookup for the dog and its food.
3. The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
4. A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
5. A formula column named Deposit is automatically populated with 20% of the adoption fee.
6. A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.

Exercise and feedings
1. Exercise for the dogs is tracked in an Exercise table.

2. Feedings are tracked in a Feeding table.
3. Exercise and feeding records appear in a resident record timeline.

Care staff
1. The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
2. The staff must be able to update the weight of a dog on the resident record.
3. The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
4. The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.

Administrate staff
1. Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
2. When an adopter wants to adopt a dog. the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:

Commitment:
1. Obtain adopter signature in a commitment document.
2. Collect deposit

Pre-pickup:
1. Document spay or neutering date.
2. Perform spay or neutering.
3. Document pickup date.

Pickup:
Collect full payment.
Verify dog is picked up.
1. A dog must be picked up no sooner than two days after spaying or neutering.
2. A pop-up window must appear with an error message if the Pickup date is too soon.
3. Only administrative staff must be able to add new adopters and dogs.

Background
ADatum Corporation provides verification and investigation services that are used by insurance companies, law firms, and other organizations in the public sector. Services include verifying an individual's background, qualifications, and specific scenarios that require onsite visit.

The thorough work ADatum Corporation performs results in highly accurate cases with minimal critical information missing. Because of these high-quality results, ADatum Corporation is quickly proving itself as one of the best in the industry. In recent months, business has significantly increased, with most new business coming from high-profile companies and individuals.

Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed.

Current environment
Data storage and retention

1. All information sent by clients for services is stored in Microsoft Dataverse with a model-driven app as the interface.
2. Clients enter their data in a website, which then uses a service account to create the records in the
Dataverse database.
3. Team members currently have full access to all Service Request records.

Service requests
1. The Service Request table includes header information about the individual or organization that is the subject of verification.
2. New Service Request records are assigned to a queue. All potential users who will be performing the verifications have access to these records.
3. A service request is assigned to a single user who will ensure that all qualifications are verified. This single user is the only one able to process Qualification records related to their own service requests.
4. Many required tasks when performing verification services are currently done by using manual processes.
5. To keep up with demand, ADatum Corporation identifies several processes that can be replaced by using Power Automate flows to hire fewer new staff and keep costs down.

Qualification verification
1. The qualification table contains details about an individual school degree, professional qualifications, and other qualifications that must be verified.
2. A service request can have one or more Qualification records associated with it.
3. Record status is pending verification until the initial team member finishes, at which point the member changes the status to Complete.
4. When all qualification records related to a service request are verified either by manual or automated processes, the results are made available to ADatum Corporation's client.
5. In the rare event that results are questioned, a new service request is created and verified independently of the previous work that took place.
6. To complete a service request, users perform the following actions

Microsoft Power platform environment
1. The following environments exist: development, testing, user acceptance testing (UAT), and production.
2. Managed solutions are used to move customizations from the development environment to other higher-level environments. These solutions are created and maintained by the power users and provided to internal IT for deployment when they are ready.
3. Two managed solutions, Verification Process Automation and Onsite Visit, share several components.
4. All customizations to Power Platform components are performed by several power users who have received training and are certified as subject matter experts.
5. Power users have been granted the System Administrator security role in the development environment.
6. Corporate policy prohibits power users from writing code due to lack of a formal code review process.
7. Internal IT will not be able to supply any development resources for this project due to a lack of staff.
This means that any customizations and automation created for this project must be low-code/no-code for the power users to implement them.
8. Customizations created by power users are deployed by internal IT.

Requirements
Process automation
ADatum Corporation plans to establish a new QV department to verify completed work so that the quality of work is maintained. The new process for verifying professional qualifications must automate the following:
1. Enter data and navigate the authority's website. The authority website UI changes frequently because the company constantly improves the user experience.
2. Search page contents for a specified value to determine validity.
3. Update the corresponding Qualification record in Dataverse.

The new process for completing a service request must automate the following:
1. Set the Service Request record status to Complete when work on all Qualification records is finished.
2. Send an email to the client with the results when the service request is completed.
3. The email must list each qualification as either Valid or Not Valid, depending on the verification.

Qualification verification
Service request results will not be released to clients until all related Qualification records are set to a Complete status.
1. To check work done by a wide array of users, 10 percent of Qualification records must be double checked.
2. Qualification records must be automatically assigned to a queue.
3. Qualification records must be flagged with a new status field named Assigned to ensure that records are rechecked.
4. Ensure that only QV team members can change the status from Assigned to In Progress to Complete.
5. Record the name of the QV team member who performed the work and the date completed.

Governance and security
1. All components required for the verification process must be included in a new solution.
2. Corporate security requires that deployments to non-development environments must be automated using service accounts.
3. User security and data access must also be consistent across environments, except for the elevated access of the power users in the development environment.
4. The Onsite Visit managed solution has a table that is not in the Verification Process Automation managed solution. This table must be upgraded prior to the go-live date without the other shared components.
5. A VP of sales requires a test environment to demonstrate to potential clients the security policies that

are included in their initial offering.

Issues
1. More employees than are required can access individual client information and continue to have access after a service request is completed.
2. When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.
3. Currently, testing the new QV functionality outside the development environment is not possible due to corporate security policies requiring the same security role across all environments.
4. Internal IT reports that the solution import to the test environment failed because of missing dependencies related to the flow for completing service requests.

Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible.
Dataverse is set up with the following configuration:
1. The solution prefix 'cs' is used for all new components.
2. Only the root business unit is used.
3. All tables are stored in Dataverse and do not require rapid scaling.
4. Exchange server-side sync is not configured.

Adopters
1. Adopter information is stored in a Contact table.
2. Contacts are considered to be duplicates if they have the same email address and last name.
3. Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
4. The email reminders must not be tracked in the system.

Dogs
1. Dog information is stored in a Dog table, which is organization owned.
2. Breed, size, and weight are fields in the table.

Dog residency
1. A Resident table tracks the stay of each dog.
2. Each resident record has a lookup for the dog and its food.
3. The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
4. A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
5. A formula column named Deposit is automatically populated with 20% of the adoption fee.
6. A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.

Exercise and feedings
1. Exercise for the dogs is tracked in an Exercise table.

2. Feedings are tracked in a Feeding table.
3. Exercise and feeding records appear in a resident record timeline.

Care staff
1. The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
2. The staff must be able to update the weight of a dog on the resident record.
3. The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
4. The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.

Administrate staff
1. Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
2. When an adopter wants to adopt a dog. the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:

Commitment:
1. Obtain adopter signature in a commitment document.
2. Collect deposit

Pre-pickup:
1. Document spay or neutering date.
2. Perform spay or neutering.
3. Document pickup date.

Pickup:
Collect full payment.
Verify dog is picked up.
1. A dog must be picked up no sooner than two days after spaying or neutering.
2. A pop-up window must appear with an error message if the Pickup date is too soon.
3. Only administrative staff must be able to add new adopters and dogs.

Background

Bellows College is a postsecondary school that wants to start a football team. The college uses Microsoft Power Platform to manage its recruiting efforts. The registration team and assistants use modeldriven apps. The coaches use canvas apps on their mobile devices.

Prospects are considered underage if they are younger than 18 years old at the time of registration.

Current environment
Environment
1. Custom code is not allowed in the system.
2. Serverside synchronization is configured for emails, appointments, contacts, and tasks.
3. The database and file storage of Dataverse must be minimized to keep costs low.

Contact table
1. Birthdate is a custom date and time field.
2. Age at Registration is a calculated field that displays the age of the prospect at the time of registration.
3. Current Age is a calculated field that displays the age of the prospect based on the current date and time.

Evaluation table
1. The Evaluation table is a custom table used to track evaluation criteria.
2. Evaluation records cannot be manually created.
3. Users must not be able to continue until an evaluation record is created automatically for the prospect.

Consent table
1. The consent forms completed by the parents are stored as records in the Consent table.
2. Occasionally, a parent cannot complete the consent online and a paper copy must be printed. The signed copy must be scanned and stored with the consent record.

Team website
1. The team website is created by using Power Pages.
2. A starter layout template was used to create the site.
3. The site consists of five pages:
4. Home: A page open to everyone to view the announcements from the team.

5. Schedule: A page open to everyone to view the tryout and game schedule.
6. Evaluations: A page that displays tracking from the evaluation table. Prospects are able to view their own information only.
7. Forms: A page that displays the consent form.
8. Contact Us: A page for anyone to submit questions and comments.
9. Two web roles for authenticated users are created: Primary Contact User and Prospect User.
10. All primary contacts and prospects are assigned to their respective roles.

Requirements
Registration

1. Parents and prospects are created as contacts and must be linked.
2. The registration team must be able to rapidly create prospects without navigating away from the Parents form. Only the First Name, Last Name, and Birthdate fields should be displayed for the team.
3. Assistants must be able to update prospect information and add teams that the prospect has previously played on to a subgrid.

Parental consent
1. When a prospect is underage, a Primary Contact field will appear. The field must be populated before the prospect record can be saved.
2. A view named Underage Prospects that lists all underaged prospects is required.
3. The Underage Prospects view must run once a week without requiring modifications to display correct information.
4. A consent email must meet the following requirements:
5. be sent to the primary contact of each new underage prospect
6. contain a link to the team website
7. be automatically sent weekly and tracked to the contact record in Dataverse
8. include the current date using the full month name, date, and year

Evaluations
1. Coaches rate prospects each day on a scale of 110 in three categories: endurance, coordination, and skill.
2. The total of the three categories is displayed at the bottom of the form. If the total for the day is greater than 25, the number should appear green.

Background

Bellows College is a postsecondary school that wants to start a football team. The college uses Microsoft Power Platform to manage its recruiting efforts. The registration team and assistants use modeldriven apps. The coaches use canvas apps on their mobile devices.

Prospects are considered underage if they are younger than 18 years old at the time of registration.

Current environment
Environment
1. Custom code is not allowed in the system.
2. Serverside synchronization is configured for emails, appointments, contacts, and tasks.
3. The database and file storage of Dataverse must be minimized to keep costs low.

Contact table
1. Birthdate is a custom date and time field.
2. Age at Registration is a calculated field that displays the age of the prospect at the time of registration.
3. Current Age is a calculated field that displays the age of the prospect based on the current date and time.

Evaluation table
1. The Evaluation table is a custom table used to track evaluation criteria.
2. Evaluation records cannot be manually created.
3. Users must not be able to continue until an evaluation record is created automatically for the prospect.

Consent table
1. The consent forms completed by the parents are stored as records in the Consent table.
2. Occasionally, a parent cannot complete the consent online and a paper copy must be printed. The signed copy must be scanned and stored with the consent record.

Team website
1. The team website is created by using Power Pages.
2. A starter layout template was used to create the site.
3. The site consists of five pages:
4. Home: A page open to everyone to view the announcements from the team.

5. Schedule: A page open to everyone to view the tryout and game schedule.
6. Evaluations: A page that displays tracking from the evaluation table. Prospects are able to view their own information only.
7. Forms: A page that displays the consent form.
8. Contact Us: A page for anyone to submit questions and comments.
9. Two web roles for authenticated users are created: Primary Contact User and Prospect User.
10. All primary contacts and prospects are assigned to their respective roles.

Requirements
Registration

1. Parents and prospects are created as contacts and must be linked.
2. The registration team must be able to rapidly create prospects without navigating away from the Parents form. Only the First Name, Last Name, and Birthdate fields should be displayed for the team.
3. Assistants must be able to update prospect information and add teams that the prospect has previously played on to a subgrid.

Parental consent
1. When a prospect is underage, a Primary Contact field will appear. The field must be populated before the prospect record can be saved.
2. A view named Underage Prospects that lists all underaged prospects is required.
3. The Underage Prospects view must run once a week without requiring modifications to display correct information.
4. A consent email must meet the following requirements:
5. be sent to the primary contact of each new underage prospect
6. contain a link to the team website
7. be automatically sent weekly and tracked to the contact record in Dataverse
8. include the current date using the full month name, date, and year

Evaluations
1. Coaches rate prospects each day on a scale of 110 in three categories: endurance, coordination, and skill.
2. The total of the three categories is displayed at the bottom of the form. If the total for the day is greater than 25, the number should appear green.

Background

Bellows College is a postsecondary school that wants to start a football team. The college uses Microsoft Power Platform to manage its recruiting efforts. The registration team and assistants use modeldriven apps. The coaches use canvas apps on their mobile devices.

Prospects are considered underage if they are younger than 18 years old at the time of registration.

Current environment
Environment
1. Custom code is not allowed in the system.
2. Serverside synchronization is configured for emails, appointments, contacts, and tasks.
3. The database and file storage of Dataverse must be minimized to keep costs low.

Contact table
1. Birthdate is a custom date and time field.
2. Age at Registration is a calculated field that displays the age of the prospect at the time of registration.
3. Current Age is a calculated field that displays the age of the prospect based on the current date and time.

Evaluation table
1. The Evaluation table is a custom table used to track evaluation criteria.
2. Evaluation records cannot be manually created.
3. Users must not be able to continue until an evaluation record is created automatically for the prospect.

Consent table
1. The consent forms completed by the parents are stored as records in the Consent table.
2. Occasionally, a parent cannot complete the consent online and a paper copy must be printed. The signed copy must be scanned and stored with the consent record.

Team website
1. The team website is created by using Power Pages.
2. A starter layout template was used to create the site.
3. The site consists of five pages:
4. Home: A page open to everyone to view the announcements from the team.

5. Schedule: A page open to everyone to view the tryout and game schedule.
6. Evaluations: A page that displays tracking from the evaluation table. Prospects are able to view their own information only.
7. Forms: A page that displays the consent form.
8. Contact Us: A page for anyone to submit questions and comments.
9. Two web roles for authenticated users are created: Primary Contact User and Prospect User.
10. All primary contacts and prospects are assigned to their respective roles.

Requirements
Registration

1. Parents and prospects are created as contacts and must be linked.
2. The registration team must be able to rapidly create prospects without navigating away from the Parents form. Only the First Name, Last Name, and Birthdate fields should be displayed for the team.
3. Assistants must be able to update prospect information and add teams that the prospect has previously played on to a subgrid.

Parental consent
1. When a prospect is underage, a Primary Contact field will appear. The field must be populated before the prospect record can be saved.
2. A view named Underage Prospects that lists all underaged prospects is required.
3. The Underage Prospects view must run once a week without requiring modifications to display correct information.
4. A consent email must meet the following requirements:
5. be sent to the primary contact of each new underage prospect
6. contain a link to the team website
7. be automatically sent weekly and tracked to the contact record in Dataverse
8. include the current date using the full month name, date, and year

Evaluations
1. Coaches rate prospects each day on a scale of 110 in three categories: endurance, coordination, and skill.
2. The total of the three categories is displayed at the bottom of the form. If the total for the day is greater than 25, the number should appear green.

Background

Alpine Ski House is a boutique mountain resort that offers year-round spa and outdoor activities such as snow sports, hiking, mountain biking, and more. The resort has been family owned and operated for more than 50 years. The company has been able to remain profitable while not needing to adopt new technologies.

Current environment. General

Bookings at the resort have decreased. The company has decided to focus on creating a tailored, first-class experience for guests. The company also plans to target corporate meetings and events.

The company recently purchased a chatbot named FAQbot from AppSource. The chatbot uses the resort's existing FAQs.

Current environment. Communication

1. Communication between staff members is primarily conducted through email and SMS text messages.
2. Conversations between staff members and guests are often lost.
3. Conference calls are used for all group meetings.

Current environment. Event registration

1. Corporate customers can reserve a meeting room at the resort to host meetings. The meetings will include lunch and choice of either an inside-spa experience or a seasonally appropriate outdoor activity.
2. Event registration is conducted three weeks prior to start of the event. It is assumed that all event attendees will attend the meeting.

Current environment. Check-in progress

1. Guests wait in lines to check in and obtain name badges. At this time, guests can specify any dietary restrictions and select their activity preference. This can result in long wait times and crowding at the front desk.
2. For health and compliance reasons, guests must answer a series of questions with a yes or no answer during check-in. The front desk will ask and record these answers for the resort's records.

Current environment. Marketing

At the check-in counter, the guests can drop their business cards into a bowl for a chance to win an all-inclusive weekend stay at the resort. The resort uses the business card information to send announcements about promotions and upcoming events.

Current environment. Resort policies and event inquiries

1. A guest can call or send an email to the event coordinator at the resort to get information about hotel policies, snow conditions, or to pre-select their after-meeting event.
2. Guests can also go to the website to view the extensive list of frequently asked questions (FAQ) compiled over the years. Many of the answers to the FAQ's are out of date.

Requirements. General

Alpine Ski House does not employ technical staff and does not have the budget to hire an external firm to develop solutions. There are two team members who are proficient at Microsoft Excel formulas. Any solution created must use the capabilities of current team members.

All solutions must be simple to use, easy to maintain, and represent the brand of the resort.

You must implement the following solutions:

1. a centrally managed communication solution
2. a customer service solution
3. a resort portal
4. a chat solution
5. a check-in solution

Requirements. Communication

1. Communication between team members must be centrally managed and unified in Microsoft Teams.
2. When the company confirms an event, they must provide a list of guest's names and email addresses.
3. You must send guests a welcome email that includes a unique registration number for authentication with the resort's portal.
4. Guests must receive a separate email to verify proof of ownership for their registration.

Requirements. Event attendance

1. Guests must create an account and sign into a resort portal to confirm their attendance to an event and pre-select an after-meeting event.
2. Prior to the event, guests must be able to identify any personal dietary restrictions.

Requirements. Check-in processes

1. Check-in processes must be self-service. Each screen must ask for specific data from the guest. The check-in solution will use some data that is stored in Microsoft Excel.
2. The check-in solution must continue to function if there are internet issues. If the self-service kiosks are not available, staff must be able to use the check-in solution from within their communication solution.
3. The check-in solution must have a screen where the guest will select either yes or no to health and wellness questions. Guests must physically interact with each answer before proceeding to the next screen.
4. Guests must be able to confirm any dietary restrictions they may have entered from the portal or add new ones at this time.
5. Data must be entered in each screen before users move on to the next screen.

Requirements. Marketing

1. To eliminate the handling of business cards, the check-in solution must be able to translate the contents of the business cards into Alpine Ski House's marketing system.
2. The solution must not require any effort or manual entry from the guest to prevent any mistyped information and to make it more appealing to the guest to participate.

Requirements. Hotel policies and event inquiries

The portal must allow the guests to ask questions about hotel policies, event information, weather reports, and current weather conditions at the resort.

Requirements. Chat solution

The chat solution must specifically address the following key words. No additional key words will be added until a later implementation phase:

1. Snow reports
2. Weather conditions
3. Start time
4. End time
5. Event date
6. Outdoor activities
7. Indoor activities
8. Most popular

The chat solution must be available always and not require staff to answer all of the questions. If a question does require a staff member's attention, the solution must determine which staff member is best to assist the customer with the question.

The information in the FAQ on the legacy website must be used in the chat solution but retyping all the data from the website should not be required. If guests ask about topics that are not listed in the FAQ the chat solution must identify the issue and escalate to a staff member.

Team members must be able to ask their own questions through a centrally managed communication solution instead of using the guest portal. Team members must be able to access the same FAQ across multiple solutions.

Issue

Guest1 inquires about snow conditions several times during each day of their stay.

Background

Alpine Ski House is a boutique mountain resort that offers year-round spa and outdoor activities such as snow sports, hiking, mountain biking, and more. The resort has been family owned and operated for more than 50 years. The company has been able to remain profitable while not needing to adopt new technologies.

Current environment. General

Bookings at the resort have decreased. The company has decided to focus on creating a tailored, first-class experience for guests. The company also plans to target corporate meetings and events.

The company recently purchased a chatbot named FAQbot from AppSource. The chatbot uses the resort's existing FAQs.

Current environment. Communication

1. Communication between staff members is primarily conducted through email and SMS text messages.
2. Conversations between staff members and guests are often lost.
3. Conference calls are used for all group meetings.

Current environment. Event registration

1. Corporate customers can reserve a meeting room at the resort to host meetings. The meetings will include lunch and choice of either an inside-spa experience or a seasonally appropriate outdoor activity.
2. Event registration is conducted three weeks prior to start of the event. It is assumed that all event attendees will attend the meeting.

Current environment. Check-in progress

1. Guests wait in lines to check in and obtain name badges. At this time, guests can specify any dietary restrictions and select their activity preference. This can result in long wait times and crowding at the front desk.
2. For health and compliance reasons, guests must answer a series of questions with a yes or no answer during check-in. The front desk will ask and record these answers for the resort's records.

Current environment. Marketing

At the check-in counter, the guests can drop their business cards into a bowl for a chance to win an all-inclusive weekend stay at the resort. The resort uses the business card information to send announcements about promotions and upcoming events.

Current environment. Resort policies and event inquiries

1. A guest can call or send an email to the event coordinator at the resort to get information about hotel policies, snow conditions, or to pre-select their after-meeting event.
2. Guests can also go to the website to view the extensive list of frequently asked questions (FAQ) compiled over the years. Many of the answers to the FAQ's are out of date.

Requirements. General

Alpine Ski House does not employ technical staff and does not have the budget to hire an external firm to develop solutions. There are two team members who are proficient at Microsoft Excel formulas. Any solution created must use the capabilities of current team members.

All solutions must be simple to use, easy to maintain, and represent the brand of the resort.

You must implement the following solutions:

1. a centrally managed communication solution
2. a customer service solution
3. a resort portal
4. a chat solution
5. a check-in solution

Requirements. Communication

1. Communication between team members must be centrally managed and unified in Microsoft Teams.
2. When the company confirms an event, they must provide a list of guest's names and email addresses.
3. You must send guests a welcome email that includes a unique registration number for authentication with the resort's portal.
4. Guests must receive a separate email to verify proof of ownership for their registration.

Requirements. Event attendance

1. Guests must create an account and sign into a resort portal to confirm their attendance to an event and pre-select an after-meeting event.
2. Prior to the event, guests must be able to identify any personal dietary restrictions.

Requirements. Check-in processes

1. Check-in processes must be self-service. Each screen must ask for specific data from the guest. The check-in solution will use some data that is stored in Microsoft Excel.
2. The check-in solution must continue to function if there are internet issues. If the self-service kiosks are not available, staff must be able to use the check-in solution from within their communication solution.
3. The check-in solution must have a screen where the guest will select either yes or no to health and wellness questions. Guests must physically interact with each answer before proceeding to the next screen.
4. Guests must be able to confirm any dietary restrictions they may have entered from the portal or add new ones at this time.
5. Data must be entered in each screen before users move on to the next screen.

Requirements. Marketing

1. To eliminate the handling of business cards, the check-in solution must be able to translate the contents of the business cards into Alpine Ski House's marketing system.
2. The solution must not require any effort or manual entry from the guest to prevent any mistyped information and to make it more appealing to the guest to participate.

Requirements. Hotel policies and event inquiries

The portal must allow the guests to ask questions about hotel policies, event information, weather reports, and current weather conditions at the resort.

Requirements. Chat solution

The chat solution must specifically address the following key words. No additional key words will be added until a later implementation phase:

1. Snow reports
2. Weather conditions
3. Start time
4. End time
5. Event date
6. Outdoor activities
7. Indoor activities
8. Most popular

The chat solution must be available always and not require staff to answer all of the questions. If a question does require a staff member's attention, the solution must determine which staff member is best to assist the customer with the question.

The information in the FAQ on the legacy website must be used in the chat solution but retyping all the data from the website should not be required. If guests ask about topics that are not listed in the FAQ the chat solution must identify the issue and escalate to a staff member.

Team members must be able to ask their own questions through a centrally managed communication solution instead of using the guest portal. Team members must be able to access the same FAQ across multiple solutions.

Issue

Guest1 inquires about snow conditions several times during each day of their stay.