A sales manager wants her team's assigned leads view to automatically surface the leads most likely to convert at the top of the list each morning, without sellers manually reordering anything themselves. Which configuration should the consultant use to achieve this?
Select an answer to reveal the explanation.
Short Explanation
The manager just wants the most promising leads sitting right at the top when a seller opens their list each morning, with no extra clicking or sorting required. The simplest path is to let the view itself do the ranking using the score the model already calculates, sorted so the biggest numbers land first. Sorting by how recently something was created just tells you what is newest, not what is most promising, so that misses the point entirely. Standing up a whole separate nightly email process to deliver a ranked list is solving a problem that the view can already solve on its own, and duplicate detection is a completely different concern about catching redundant records, not about ranking anything by likelihood to convert.
Full Explanation
The correct answer is C. Since the predictive lead scoring model already produces a numeric score reflecting conversion likelihood, the most direct way to surface the most promising leads automatically is to add that score as a column on the view and sort by it in descending order, so the view itself always reflects current priority without any manual reordering by sellers. Option A is incorrect because sorting by created-on date only reflects how recently a lead entered the system, which has no bearing on how likely it is to convert and would frequently push high-potential older leads down the list. Option B is incorrect because building a nightly email flow introduces unnecessary complexity and a separate artifact outside the working view, when the view itself can already be configured to sort by score directly within the application the sellers already use. Option D is incorrect because duplicate detection rules address data quality by flagging or preventing redundant records; they have no relationship to ranking leads by conversion likelihood and would not change how the view is ordered.