A consultant has enabled Copilot for Sales for a client and confirmed sellers can use the default prompts to draft emails and summarize records. The sales director now wants a custom Copilot prompt that pulls in the client's proprietary competitive battlecards stored in a SharePoint library whenever a seller asks about a competitor. What should the consultant do to deliver this?
Select an answer to reveal the explanation.
Short Explanation
Out of the box, Copilot for Sales comes with a set of default prompts, and those are great until someone wants something the product was never built to know about, like the company's own competitive battlecards sitting in a document library. That's not a licensing question, and it's not something solved by relating a SharePoint folder to the opportunity form, because neither of those actually teaches Copilot where to look or how to use that content. What actually extends its behavior is a separate authoring tool built for exactly this: creating a custom topic or plugin that connects to that library and wiring it into the Copilot for Sales experience so sellers can ask about a competitor and get an answer grounded in the client's own material. Asking sellers to just paste content into notes might get it into Dynamics somewhere, but that's a manual workaround, not a supported way to ground an AI assistant's answers, and it relies on a completely different feature meant for analyzing calls, not documents.
Full Explanation
The correct answer is A. Copilot for Sales ships with a default set of prompts for common tasks such as drafting emails and summarizing records, but reaching into an external source like a SharePoint battlecard library requires extending the assistant with custom logic. Copilot Studio is the tool built for that: it lets a consultant create a custom topic or plugin that connects to the SharePoint library and add it into the Copilot for Sales experience so sellers can ask competitor-related questions and get answers grounded in that content. Option B is incorrect because re-enabling Copilot for Sales with a different license changes seat entitlements, not what data sources or prompts Copilot can draw on. Option C is incorrect because adding a related entity to the opportunity form changes what a user sees on that form; it does not grant Copilot any grounding access to a SharePoint library. Option D is incorrect because asking sellers to paste content into notes is a manual workaround that depends on Conversation Intelligence, a feature built to extract signals from call transcripts, not a mechanism for grounding Copilot's prompts in an external document library.