A sales manager notices several opportunities forecasted as likely to close have stalled: sellers have logged no recent activity, email response rates from the buyer side have dropped, and calls are going unanswered. The manager wants Dynamics 365 Sales to automatically surface these warning signs on the opportunity itself so sellers can intervene before the deals go cold, rather than relying on sellers to notice the pattern themselves. Which AI-driven capability should the consultant configure?
Select an answer to reveal the explanation.
Short Explanation
What the manager wants is a deal to raise its own hand when things are going quiet, instead of someone having to notice on their own that emails have stopped getting replies and calls aren't being picked up. That's a pattern-detection job, watching engagement signals over time and flagging risk right where the seller will see it. A process flow stage requirement is just a checklist a person set up in advance; it doesn't watch anything, it just demands a field get filled in. A drafting assistant is useful once a seller has already decided to reach out, but it does nothing to notice the silence in the first place. And a rollup number for the whole pipeline tells the manager how much revenue is expected in total, which is the wrong resolution when the actual need is spotting which individual deals are quietly dying. The capability that continuously reads engagement signals and posts a warning on the specific stalling deal is the one that solves this.
Full Explanation
The correct answer is D. Relationship health and deal risk insights within Sales Insights are built to continuously analyze signals such as declining response rates, gaps in seller activity, and unanswered outreach, then surface risk indicators directly on the affected opportunity so a seller sees the warning without having to notice the pattern manually. This matches the manager's requirement for automatic, per-deal detection rather than manual review. Option A is incorrect because a business process flow stage requirement is a static, manually defined rule that enforces data entry or task completion at a stage; it does not analyze engagement patterns or detect risk on its own. Option B is incorrect because the email drafting assistant helps a seller compose messages faster once they decide to act, but it does not detect stalled deals or declining engagement in the first place. Option C is incorrect because a predictive forecast rollup aggregates expected revenue across an entire pipeline or team for planning purposes; it reports a summary number rather than flagging risk signals on any individual opportunity, so a manager reviewing only the rollup would not see which specific deals are stalling.