You need to configure the chatbot. Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

To properly integrate and configure a chatbot within Dynamics 365 Customer Service, you must establish the routing logic and the data transfer mechanism. First, you need a dedicated queue for human agents to handle conversations escalated from the bot. The workstream routes incoming conversations to the chatbot initially, and upon escalation, reroutes them to the human agent queue. Second, configuring context variables is essential. These variables capture key information from the customer during the bot conversation (e.g., name, product, issue type) and pass it to the human agent, ensuring a seamless and informed transition without requiring the customer to repeat information.

A. Enable a Microsoft Copilot Studio chatbot to end conversations. This is a standard capability configured within a bot's topic flow, not a primary integration or setup action for connecting it to the customer service platform.
B. Add the chatbot to an existing human agent queue. This is incorrect. Chatbots are the first point of contact in a workstream; they escalate conversations to a human agent queue, but are not members of it.
C. Enable AI suggestions with the chatbot. AI suggestions are a feature to assist human agents by providing real-time recommendations like knowledge articles or case resolutions, not a configuration step for the chatbot itself.

1. Microsoft Learn | Dynamics 365 Customer Service Documentation. "Configure context variables for a bot." This document explicitly states, "When a customer's conversation is escalated from a bot to a human agent, the complete context of the bot conversation can be shared with the human agent... To configure the transfer of conversation context, you must configure context variables." This directly supports option E.

2. Microsoft Learn | Dynamics 365 Customer Service Documentation. "Integrate a Copilot Studio bot." Under the "Create a bot user" and "Add the bot to a queue" sections, the documentation outlines the necessity of setting up the bot within a workstream that routes to a specific queue for bot interactions, and then configuring escalation rules to transfer to a separate human agent queue. This supports the structural setup described in option D.

3. Microsoft Learn | Microsoft Copilot Studio Documentation. "Configure hand-off to Dynamics 365 Customer Service." This guide details using the "Transfer to agent" node, which sends the conversation and its context (variables) to Omnichannel for Customer Service, which then uses its routing rules to assign the conversation to the appropriate human agent queue. This reinforces the need for both context variables (E) and a destination queue for humans (D).