A financial-services sales team uses Copilot-generated call summaries that are automatically appended to the opportunity timeline after each customer call. Compliance requires that any customer-facing communication captured in the CRM be reviewed by a licensed representative before it is considered part of the official record. What should the consultant recommend?
Select an answer to reveal the explanation.
Short Explanation
The compliance rule here is really specific: a licensed person has to look at customer-facing content before it counts as official. That means whatever gets set up needs an actual checkpoint sitting between the AI generating the summary and it landing permanently on the record. Saving the summary as a draft that a seller has to approve does exactly that, it inserts a real review step without throwing away the time savings of having AI draft the summary in the first place. Turning the feature off entirely solves the compliance problem by brute force, but it also throws out all the efficiency the team was getting, which is more than the requirement calls for. Locking the field so only managers can see it after the fact does not add review before posting, it just changes who can look at something that is already final, which misses the point of the requirement. And filtering out summaries based on a sentiment score has nothing to do with whether a qualified person actually checked the content, that is measuring the wrong thing entirely. A draft-and-approve step is what actually satisfies the rule.
Full Explanation
The correct answer is D. Configuring generated summaries to save as drafts pending seller review and approval satisfies the compliance requirement by inserting a human checkpoint before an AI-generated summary becomes part of the official record, while still preserving the time savings Copilot provides. Option A is incorrect because disabling summarization entirely discards the efficiency benefit of the feature and forces a return to fully manual note-taking, which is a heavier-handed response than the compliance requirement actually demands. Option B is incorrect because restricting who can view the summary after it has already posted does not constitute a review before it becomes part of the record; visibility is not the same as approval, and the compliance requirement is about pre-posting review. Option C is incorrect because deleting summaries based on a sentiment confidence score is an unrelated and arbitrary criterion that has nothing to do with whether a licensed representative reviewed the content for accuracy, and it could delete accurate summaries or retain inaccurate ones. A draft-and-approve workflow is the direct way to insert the required human review step.