A consultant configures a Sales Accelerator work queue for an inbound SDR team and enables predictive lead scoring in Sales Insights so that each lead carries an AI-generated score. Sellers report the work queue still lists leads in the order they were created rather than prioritizing the highest-scoring leads first. What should the consultant change to fix this?

The correct answer is editing the segment feeding the Sales Accelerator work queue so its sort configuration uses the predictive score field instead of the created-on date. The Sales Accelerator work queue displays records in the order defined by the segment that populates it, and by default that sort is often based on a field like created-on date. Enabling predictive lead scoring generates a score on each lead, but it does not automatically change how any existing queue is sorted; the segment's sort configuration has to be edited to reference the score field so the highest-scoring leads surface at the top. The choice about re-enabling predictive lead scoring is incorrect because the scenario states leads already carry AI-generated scores, which confirms scoring is running; the symptom is purely about presentation order in the queue, not whether scores are being generated. The choice about assigning the Sales Accelerator work queue to a security role with higher priority is incorrect because security roles govern who can access or act on records and queues, not the sequence in which records are displayed within a queue. The choice about adding the predictive score field to the lead form is incorrect because a Sales Accelerator segment's sort configuration reads the underlying field value directly from the record; the field does not need to be added to the lead form for the queue to sort by it, since form layout and queue sorting are independent of each other.