MB-230 · Question #421
Case Study 6 - Lucerne Publishing Background Lucerne Publishing is a publishing company in Canada. The company publishes books for higher education. It also invests in multiple cloud-based solutions t
The correct answer is Install Dynamics 365 Productivity Tools solution.; Assign the Productivity Tools administrator security role.; Configure the productivity automation connector.; Configure the macro action.. Explanation: Creating a New Agent Script in Dynamics 365 Productivity Tools > Note: The question states "five actions" but the provided correct arrangement only lists four. The fifth item - Configure the session automation connector - almost certainly belongs at position 4, pushi
Question
Case Study 6 - Lucerne Publishing Background Lucerne Publishing is a publishing company in Canada. The company publishes books for higher education. It also invests in multiple cloud-based solutions to support the customer service, publishing, and sales departments. Current Environment Lucerne Publishing uses the following:
- The Customer Service app for the publishing customer service division.
- Omnichannel capabilities in the Customer Service app.
- Third-party apps for e-commerce so students and parents can order books or courses online.
- Customer service agents as the representatives who will resolve customers issues using
various channels.
- Resident employees who work for Lucerne Publishing and live in the buildings inside the
business center.
- A technician dispatch team that includes dispatchers who review and schedule work orders and
assign the work orders to resources on the schedule board. The company has an internal division that provides repair services such as plumbing and electrical. The division provides services to the buildings inside the company business center, and some of those are used as residences by printing employees. Requirements Customer Service - Contact Center The company has the following requirements:
- Improve agent response time in live chats with customers.
- Improve agent productivity by automating tasks. For example, the customer service manager
requests that a new case is created automatically when an agent is on a chat with a customer.
- Provide instructions for agents to use when processing book returns. The instructions must
include the following: o Greet the customer. o Automatically open the case form for the book return, o Close the session with the customer.
- Allow agents to use different channels such as short message service (SMS), social, and call
when providing service to customers.
- Enable a new text SMS channel for the agents.
- Improve the agents' capability to search using AI suggestions.
- Provide agents with real-time recommendations on similar cases and knowledge-base articles.
- Allow agents to know the customer’s point of view on the service.
- Provide a solution that will identify an agent's supervisor when a customer has a negative
experience.
- Improve how the agents' skills and profiles are maintained.
- Route calls to agents who can support French-speaking customers.
- Configure the French language as a skill for agents who support French-speaking customers.
- Provide access to the Omnichannel agent app and productivity tools for supervisors and agents.
- Provide the customer service supervisor with the ability to create agent scripts for Omnichannel
agents and a workstream for SMS. The customer service supervisor must also be able to edit an existing workstream.
- Provide the customer service supervisor with the ability to track sentiment in real time.
- Provide agents with AI suggestions on the recent contact that worked on similar cases.
Customer Service - Repairs The company has the following requirements for repair requests:
- Dispatchers must be able to track a technician and schedule jobs for technicians based on
availability.
- A dispatcher named UserA must be able to create a new view to display only unscheduled work
orders. The view must be displayed only when the work orders are open-unscheduled, and the substatus is ready to dispatch work orders.
- The technician dispatch team must be able to create a Schedule tab in the schedule board.
- Dispatchers must be able to track technicians' utilization by using personal color codes.
- The field technician's security role must be field service technician.
Issues The company reports the following issues:
- Agents spend most of their time doing repetitive tasks during support calls or chats.
- There is no guided process for agents to follow the steps when a customer calls for a book
return.
- Customer service managers are not able to provide real-time recommendations to customers
using AI suggestions.
- A new channel for SMS is not sending conversations to agents. Agents are required to answer
conversations manually.
- The company is not able to retain customers who have a negative experience with the customer
service agents.
- Agents are not able to use the schedule board to schedule repair work orders by using a custom
view.
- The skills and proficiency model are not defined for the agents. Calls from French-speaking
customers are not routed to the appropriate agents. Drag and Drop Question You need to create a new agent script for the agents. Which five actions should you recommend be performed in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:
Exhibit
Answer Area
Drag items
Correct arrangement
- Install Dynamics 365 Productivity Tools solution.
- Assign the Productivity Tools administrator security role.
- Configure the productivity automation connector.
- Configure the macro action.
Explanation
Explanation: Creating a New Agent Script in Dynamics 365 Productivity Tools
Note: The question states "five actions" but the provided correct arrangement only lists four. The fifth item - Configure the session automation connector - almost certainly belongs at position 4, pushing "Configure the macro action" to position 5. The complete correct sequence is:
| # | Action |
|---|---|
| 1 | Install Dynamics 365 Productivity Tools solution |
| 2 | Assign the Productivity Tools administrator security role |
| 3 | Configure the productivity automation connector |
| 4 | Configure the session automation connector |
| 5 | Configure the macro action |
Why This Order?
1. Install Dynamics 365 Productivity Tools solution This is a hard prerequisite - nothing else can exist until the solution is deployed to the environment. Agent scripts, macros, and connectors are all components within this solution. Installing it first is non-negotiable.
2. Assign the Productivity Tools administrator security role After installation, you need the right permissions to configure anything. Without this role assigned, the administrator cannot access the configuration surfaces for connectors and macros. This must happen before any configuration work begins.
3. Configure the productivity automation connector Macros rely on Power Automate connectors to execute automated actions (e.g., opening a form, creating a case). The productivity automation connector enables macro-driven automation and must be set up before macros can be defined.
4. Configure the session automation connector The session automation connector handles session-level actions within Omnichannel (e.g., opening sessions, managing tabs). It is a peer connector to the productivity connector and must also be configured before macros reference session-based steps.
5. Configure the macro action Only after both connectors are in place can you build macros - which are the automated step sequences that agent scripts invoke. Macros reference the connectors configured in steps 3 and 4.
Common Mistakes
- Skipping the security role step (step 2): Many candidates assume they can configure connectors as a global admin without explicitly assigning the Productivity Tools administrator role. In practice, the configuration UI is gated by this role.
- Reversing steps 3 and 4: The two connectors are independent of each other, but both must precede macro configuration. Candidates sometimes place the session connector before the productivity connector - the order between these two is less critical, but both must come before macros.
- Trying to configure macros before connectors: This is the most common mistake. Macros depend on connectors to execute; without the connectors, macro actions have nothing to call.
- Confusing "agent script" with "macro": An agent script is the guided UI that agents see. Macros are the automation it triggers. You configure macros first, then attach them to agent script steps - the question stops at macro configuration as the final technical prerequisite.
Topics
Community Discussion
No community discussion yet for this question.
