A sales manager wants her team notified automatically the moment a lead's predictive score crosses into the Hot range, so sellers can act within minutes rather than waiting to notice it during their next queue review. A consultant proposes a solution. What should it be?
Select an answer to reveal the explanation.
Short Explanation
If you want to know the instant something changes, don't sit there refreshing a screen; set up something that watches for the change and taps you on the shoulder. A flow triggered on the lead's predictive score or grade field sends a notification the moment the value reaches the Hot threshold. Manual refreshing, duplicate detection, and grading every lead Hot are the wrong tools for this.
Full Explanation
The correct approach is to build a Power Automate flow triggered on a change to the lead's predictive score or grade field that sends a notification when the value reaches the Hot threshold. This gives the sales manager near-real-time alerting because the flow reacts when the score or grade changes, so sellers can act within minutes without waiting for the next queue review. The manual refresh approach is incorrect because it describes polling rather than automation, and it incorrectly claims Dynamics 365 Sales cannot trigger on score changes; field-change triggers are a standard Power Automate capability. The duplicate detection rule approach is incorrect because duplicate detection rules identify potential duplicate records and have no connection to score-based alerting; they are the wrong tool entirely for this requirement. The approach of changing the model's confidence threshold so every lead is graded Hot is incorrect because it would destroy the meaning of the grade and flood sellers with notifications for leads that are not actually promising, which is the opposite of the manager's goal.