A hospital wants the customer-service copilot to draft the case summary and wants the contact-center copilot to use that case. A separate FAQ bot has been proposed. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
Two nurses should read the same chart, not a pamphlet that has not met the patient. You let the customer-service copilot draft the case summary and have the contact-center copilot use that case. A separate FAQ bot can sound helpful and still miss the chart.
Full Explanation
The hospital already has a customer-service copilot that works the case and a contact-center copilot that meets the person on the channel. The case summary belongs to the customer-service copilot, and the contact-center copilot should read that same case so the channel answer matches the record. A separate FAQ bot is a parallel assistant that does not carry the case. Replacing both copilots with a FAQ bot that answers without opening the hospital case drops the summary and the case context together. Having the contact-center copilot draft a private summary from FAQs and leave the case unread creates a second story the case owner did not write. Keeping the FAQ bot as the only assistant and leaving both Dynamics copilots off the case abandons the copilots that already sit on the record and the channel. Exam caveat: the FAQ content can still ground a general question, but it is not a substitute for the case the two copilots are supposed to share. Operational check: draft a case summary with the customer-service copilot, open the same case from the contact center, and confirm that copilot uses the case rather than a side bot.