MB-230 · Question #373
Case Study 5 - Fourth Coffee Background You are the technology manager for Fourth Coffee. The company sells 20 types of coffees and five types of digital coffee makers. Fourth Coffee uses Dynamics 365
The correct answer is Rating; Net Promoter Score; Branching. Survey Question Types - Dynamics 365 Customer Voice This question maps three survey requirements to the correct question types available in Dynamics 365 Customer Voice. --- The Three Requirements & Their Answers Requirement 1: "Rate the service as poor, average, or great" Answer:
Question
Case Study 5 - Fourth Coffee Background You are the technology manager for Fourth Coffee. The company sells 20 types of coffees and five types of digital coffee makers. Fourth Coffee uses Dynamics 365 Customer Service with Omnichannel for Customer Service. Current environment Queues The company uses queues to service different types of customers. Each type of customer corresponds to one of the following queues:
- New customers
- Repeat customers
- Subscribers to the coffee of the month club
The company has a separate queue to manage customers who have coffee maker issues. Current environment Employees The company has 50 call representatives across five call centers. Each representative can address five calls simultaneously. Overflow calls are transferred to the back office.
- The company uses two levels of representatives to help customers with
coffee purchases: entry level and specialists.
- Supervisors monitor chats and live phone calls.
Requirements Employees Call representatives must be able to answer requests from phone calls, SMS messages, and chat. A ticket must be opened for each request. Specialists must be assigned to coffee maker calls. Specific representatives require a Dynamics 365 Customer Service workspace to perform the following activities:
- Open an assigned record in a new workspace tab.
- Use a predefined email template when representatives send an email.
- The system must notify supervisors when customers in a live session
express negative feedback about a service or product. Requirements Configuration
- If a customer starts a chat during non-working business hours, the
first representative that signs into the system must answer the chat; the customer must be able to continue the chat at any time.
- Chat sessions must start only when the customer selects the chat
icon. Chat must only be available for reorders and coffee maker repairs.
- Subscribers and new orders must always go to a live representative
unless the subscriber chooses the chat icon. Customers must be able to download a separate app to their phone or tablet for ordering coffee. The app must include only the customer’s name, address, phone number, and issue information. Requirements Support The solution must provide the following website features for external customers:
- Provide support to submit issues.
- Ensure they can log in.
The chatbot must have an option to allow users to escalate a conversation to a live representative. Live representatives must be able to send a customer back to the chatbot. Requirements Distribution of calls
- Live chat must be available for cases.
- Cases that are escalated must be distributed to the next available
agent.
- All other cases must wait for an agent to pick up the case.
- All work must be distributed evenly with no other conditions.
- The number of workstreams and routing rules must be minimized.
- Spanish-speaking customers must be sent to representatives who speak
Spanish fluently.
- Tickets must be routed to the most qualified representative for the
type of issue reported.
- All representatives must be rated on their specialty knowledge and
backup specialty. Requirements Device telemetry The solution must support the following:
- Remotely monitor coffee makers and contact a technician to help
customers with coffee maker support contracts.
- Provide a place for IoT messages to flow to the device and back to
the IoT hub.
- Automatically review messages from coffee makers and open a case when
the system indicates an error with a coffee maker.
- Provide a place for the company technology to securely connect
virtually with the coffee maker customer. Requirements Customers
- Customers must be able to sign into an external portal.
- Customers must be able to view their cases and case status
information.
- Security must be as restrictive as possible.
Requirements Surveys The survey must include the following with minimum development effort:
- A list of questions that rate the service as poor, average, or great
- A question that rates whether the customer would recommend the
company
- A question that asks if the customer would like to escalate a case
o If yes, the survey must collect an email address and phone number for the customer. o If no, another set of questions asking about open issue details must display. The solution must meet the following survey distribution requirements:
- Each survey must be standardized to include the company logo and
colors.
- Surveys must be sent out after each ticket closes.
- Quarterly surveys must be sent out to those customers who rated the
company poorly.
- Customer surveys must be available in several languages to support
global distribution. Drag and Drop Question You need to set up question types to use for the survey. Which question types should you use? To answer, drag the appropriate question types to the correct requirements. Each question type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:
Exhibit
Answer Area
Drag items
Correct arrangement
- Rating
- Net Promoter Score
- Branching
Explanation
Survey Question Types - Dynamics 365 Customer Voice
This question maps three survey requirements to the correct question types available in Dynamics 365 Customer Voice.
The Three Requirements & Their Answers
Requirement 1: "Rate the service as poor, average, or great" Answer: Rating
The Rating question type presents a scale with custom labels. You can define the endpoints and values - making "poor / average / great" a direct fit. It handles a single item on a labeled scale.
Common mistake: Choosing Likert here. Likert is a matrix question - it presents multiple statements all rated on the same agreement scale (e.g., Strongly Agree → Strongly Disagree). The requirement is a single service quality rating with custom labels, not a grid of statements. Likert would be overkill and the wrong shape.
Requirement 2: "Rates whether the customer would recommend the company" Answer: Net Promoter Score (NPS)
NPS is purpose-built for exactly this: "How likely are you to recommend us?" on a 0–10 scale. It is the industry-standard measurement for customer loyalty and recommendation likelihood. Customer Voice includes it as a dedicated question type precisely because this scenario is so common.
Common mistake: Using Rating here instead. While Rating could approximate this, NPS is the semantically correct and specifically designed type. On an exam, when the requirement says "recommend the company," NPS is always the answer.
Requirement 3: "Ask if the customer wants to escalate - if yes, collect contact info; if no, show different questions" Answer: Branching
Branching is Customer Voice's conditional logic mechanism. It routes respondents to different follow-up questions based on their answer to a prior question - which is exactly what "if yes → collect email/phone; if no → show open issue questions" describes.
Common mistake: Treating Branching as a question type rather than a behavior. It's technically a survey logic feature, but Customer Voice surfaces it as a selectable option in the question setup, so on this exam it is treated as a question type answer.
Why Likert Goes Unused
Likert is the distractor here. It is designed for rating multiple statements on a consistent agreement scale (a grid/matrix format). None of the three requirements describe that pattern, so it is never used.
Summary Table
| Requirement | Question Type | Key Reason |
|---|---|---|
| Rate service as poor/average/great | Rating | Single item, custom labels |
| Would you recommend the company? | Net Promoter Score | Standard recommendation metric |
| Escalate? → conditional follow-up | Branching | If/then conditional logic |
| (unused) | Likert | Multi-statement agreement grid - no match |
Topics
Community Discussion
No community discussion yet for this question.
