A consultant configuring Copilot for Sales for a SaaS company wants the meeting-prep brief that Copilot generates before a renewal call to include the customer's current count of open support tickets, which is stored in a third-party support platform rather than in Dataverse. Which approach should the consultant use?
Select an answer to reveal the explanation.
Short Explanation
The detail that decides this one is where the data actually lives, and it is not inside Dynamics at all, it is sitting in a completely separate support system. Telling reps to go look it up themselves just reintroduces the manual step that the whole point of meeting prep automation was supposed to remove. A business rule sounds like a fix, but rules only operate on fields that already exist inside the system, they cannot reach out to an outside platform and fetch something new. And assuming a built-in summary already covers every possible connected system is wishful thinking, since it works with what is already wired up, not with an arbitrary third-party tool nobody has told it about. The piece that actually bridges the gap is building a connector to that outside platform and giving the brief a card to display what it brings back.
Full Explanation
The correct answer is A. Because the ticket count lives in an external support platform rather than Dataverse, surfacing it in the meeting brief requires a custom card wired to a custom connector that can reach out to that platform and pull the current count into the brief Copilot generates. Option B is incorrect because manually checking a separate system defeats the purpose of extending Copilot to automate meeting prep, and it is the outcome the consultant is trying to eliminate, not a configuration. Option C is incorrect because a Dataverse business rule can only recalculate or validate data that already exists inside Dataverse; it has no mechanism to reach into a third-party platform and pull in a value that was never stored there. Option D is incorrect because there is no default Copilot for Sales capability that automatically aggregates data from any arbitrary connected system; the relationship summary works from data already present in Dynamics 365 and connected Microsoft 365 sources, not from an unconfigured third-party support platform. Reaching external, non-Dataverse data for use inside the brief specifically calls for a custom card and connector.