A consultant is helping a sales director configure the lead scoring model for a wholesale distribution business. The director wants Copilot to surface a short, plain-language reason alongside each lead's numeric score so sellers without analytics training can trust the recommendation without opening a model detail screen. Which capability should the consultant point to as already meeting this need?
Select an answer to reveal the explanation.
Short Explanation
Think about what a seller actually needs in the moment: not a dashboard, not a weekly email, not a pile of raw activity logs to sift through, but a quick reason they can trust right on the lead. That is exactly what the scoring feature already gives you. Next to the grade, it lists the handful of factors that pushed the score up or down, written in plain words instead of statistics jargon. A report of historical trends tells you about the pipeline as a whole, not this one lead, and a summary email arrives too late and too infrequent to help someone deciding who to call next. The raw timeline of emails and calls is just data; someone still has to figure out what it means, which is the exact work the director is trying to remove. The trap in questions like this is reaching for a reporting or automation tool because it sounds more sophisticated, when the simplest built-in explanation feature already does the job.
Full Explanation
The correct answer is A. Predictive lead scoring in Dynamics 365 Sales is built to be explainable at the point of use: alongside the numeric grade, it generates a natural-language list of the factors that most influenced that specific lead's score, such as engagement level or firmographic fit, so a seller can see the reasoning without leaving the record or consulting a data specialist. That directly satisfies the director's requirement for plain-language trust at the point of decision. Option B is incorrect because a Power BI report showing historical conversion trends is an aggregate, backward-looking view of the whole pipeline, not a per-lead explanation a seller can act on in the moment. Option C is incorrect because a scheduled summary flow reaches the director on a weekly cadence, not the seller working the lead in real time, and it summarizes trends rather than explaining an individual score. Option D is incorrect because the activity timeline is raw historical data entry; it requires the seller to interpret which activities mattered, which is exactly the manual analysis the director wants to eliminate. The built-in explainability output is the only option that delivers an immediate, per-lead, plain-language reason.