A seller asks Dynamics 365 Sales Copilot to draft a follow-up email to a contact after a discovery call held through Microsoft Teams. Conversation Intelligence successfully transcribed and summarized the call, and the summary is attached to the opportunity record. Even so, the Copilot-drafted email comes back generic and does not mention anything specific that was discussed on the call. What most likely explains this?
Select an answer to reveal the explanation.
Short Explanation
The detail that matters here is where the seller clicked to open Copilot from. Copilot writes using whatever context lives on the record it was launched from, and the call summary landed on the opportunity, not on the contact. Open it from the contact and Copilot only sees generic contact details, which is exactly the flat, nothing-specific draft the seller got back. Open it from the opportunity instead and suddenly the summary of what was actually discussed is right there for Copilot to pull from. It would be easy to assume some artificial restriction is at play, like a sales stage gate or a hard wall between features that never lets them talk to each other, but neither of those hold up, since Copilot works at any stage and the summary is sitting in the same shared data the rest of the app can see. And no, nobody needs to hand-paste a transcript either, since pulling in existing context automatically is the entire value of asking Copilot to draft from the right place to begin with.
Full Explanation
The correct answer is B. Copilot grounds its drafts in the context of the record it is opened from, and the call summary generated by Conversation Intelligence lives on the opportunity record where the call was logged. Opening Copilot from the contact record instead gives it only contact-level context, such as name and company details, with no visibility into the call summary attached to the opportunity, which explains why the draft came back generic despite the summary existing elsewhere in the same environment. Option A is incorrect because there is no stage restriction on when Copilot can draft an email; sellers can request a draft at any point in the sales process. Option C is incorrect because it overstates the isolation between features; Conversation Intelligence summaries are stored in Dataverse alongside the record and are available to other Sales features that read from that record, which is precisely why opening Copilot from the correct record would surface it. Option D is incorrect because Copilot does not require a manual transcript paste; it is designed to pull existing record context automatically, which is the whole point of drafting from the right starting record. The fix is record context, not a missing manual step or a hard licensing wall.