A consultant configuring Copilot for Sales in Outlook for a retail chain wants email summaries and draft replies to reference each account's 'Loyalty Tier', a custom text field the client added to the Account table in Dataverse. Currently Copilot for Sales does not mention loyalty tier in any generated content. What should the consultant do?
Select an answer to reveal the explanation.
Short Explanation
If Copilot for Sales is not mentioning a custom field, the fix almost always lives in the settings that decide what data gets handed to the assistant as context — not in the field itself. A custom field like a loyalty tier just needs to be added to that context mapping, and from then on it flows naturally into whatever the assistant writes. Renaming the field to look like a built-in one does not do anything useful, since the real requirement is exposing custom data through configuration, not disguising it as something it is not. Telling reps to type it in by hand throws away the whole point of having an AI assistant draft things for you. And bolting on a separate notification that fires off to the side just creates a second thing to check instead of putting the information where reps are already working.
Full Explanation
The correct answer is B. Copilot for Sales in Outlook only includes fields in its generated content when those fields are explicitly mapped in the record configuration that controls what CRM data is sent to the assistant as context; a custom field like 'Loyalty Tier' will be silently ignored until it is added to that mapping. Once mapped, the assistant can reference it naturally in summaries and drafts without any per-email effort from reps. Option A is incorrect because Copilot for Sales does not require custom fields to be renamed to match a fixed list — record configuration is designed specifically to expose custom fields, and renaming would not change how data types are read or solve the underlying mapping gap. Option C is incorrect because it states a false premise: custom fields can be exposed to Copilot for Sales through configuration, so telling reps to type the tier manually abandons an available capability. Option D is incorrect because building a separate notification flow works around Copilot for Sales rather than extending it, adding a disconnected side-channel instead of surfacing the tier inline where reps are already reading AI-generated content.