A sales manager wants a Sales Accelerator work queue to automatically sort leads so that the leads most likely to convert appear at the top for reps working the queue. The manager configures the segment's sort order to use a Predictive Score column, but every lead in the queue shows the same default priority and the sort has no visible effect. Predictive lead scoring has never been enabled in this environment. What must the consultant do before the sort order will work as intended?
Select an answer to reveal the explanation.
Short Explanation
Sorting a queue by a score only works if that score actually exists, otherwise every record ties for the same default value and the sort has nothing to bite into. That's exactly what's happening here: the manager pointed the segment at the right column, but the engine that fills that column with real numbers has never been turned on, so it's sorting a list of identical blanks. The instinct might be to blame the entity type, some special administrative permission, or to reach for a workaround like building an automation to copy a score into a different field. All of those skip past the actual gap. The queue and its sort configuration are already correct; what's missing is the upstream feature that generates the values being sorted on. Once that scoring capability is switched on and given time to evaluate the leads, the same segment configuration the manager already built will start working exactly as intended, with the highest-potential leads naturally floating to the top.
Full Explanation
The correct answer is A. A segment's sort order can only rank leads by a Predictive Score column if predictive lead scoring is actually enabled and running in Sales Insights; without it, every lead has no calculated score, so the sort field has nothing meaningful to order by and the queue falls back to its default order. Option B is incorrect because predictive score-based sorting is not restricted to the Opportunity entity; predictive lead scoring exists specifically to score leads, and Sales Accelerator segments can sort on that column when it is populated. Option C is incorrect because there is no dedicated administrative role gate that activates score-based sorting on a segment; sort behavior depends on whether the underlying data exists, not on the configuring user's security role. Option D is incorrect because Sales Accelerator segments can sort directly on Insights-calculated columns once they are populated; building an automation to duplicate the score into a custom field is unnecessary extra engineering for a problem that enabling the scoring model already solves. The consultant should enable predictive lead scoring first so the Predictive Score column contains real values for the segment to sort against.