A regional VP asks a rep for a quick briefing before an executive review call, and the rep uses Copilot to generate a summary of the opportunity from recent emails, notes, and meeting records. The summary covers the timeline, stakeholders, and deal status, but does not mention the increased budget the customer verbally approved during a phone call last week. The rep is confident the budget increase is real. What should the rep conclude about the missing detail?

The correct conclusion is that Copilot summaries only draw on content actually captured in the system, so the phone call detail needs to be logged before it can appear. Copilot-generated summaries are built from emails, notes, meetings, and other records that actually exist in Dynamics 365 Sales; a verbal agreement from a phone call only becomes available to the summary once someone captures it, such as through a follow-up note or logged call record. Since the budget increase was never written down anywhere in the system, there was nothing for the summary to draw on, and the fix is to log the detail rather than assume the feature failed. The idea that Copilot intentionally excludes financial figures from opportunity summaries for compliance reasons is incorrect because there is no blanket policy excluding financial figures; deal values, revenue estimates, and other monetary details routinely appear in summaries when they exist as logged data. The idea that the summary feature has a fixed word limit that cut off the budget detail is incorrect because omissions in these summaries are driven by what content is available, not by an arbitrary length restriction cutting off specific facts. The idea that the opportunity record must be re-scored before new information appears in generated summaries is incorrect because summary generation draws on activity and note content independently of the predictive scoring pipeline; re-scoring the opportunity has no bearing on what appears in a generated briefing.