A consultant enables Dynamics 365 Sales Premium's predictive opportunity scoring feature in a newly provisioned environment that has been live for three weeks. The environment already contains 60 open opportunities actively being worked, but the scoring column on the opportunity list still shows 'Insufficient data' for every record. What should the consultant do to get the model producing scores?
Select an answer to reveal the explanation.
Short Explanation
Picture a scoring engine that's supposed to grade opportunities the way a coach grades players, by comparing them to seasons that already happened. If nothing has finished yet, there's no game film to learn from. That's the trap here: the environment is full of open opportunities, all still in play, but the model needs a track record of deals that actually closed, won or lost, before it can spot the patterns that separate a winner from a loser. Sixty active deals sound like plenty of data, but to the model they're all still unknowns. The fix isn't about who can see the records, and it isn't about piling on more custom fields for the model to chew on, since extra inputs don't help if there are no outcomes to tie them to. It also has nothing to do with call transcripts; that's a different feature entirely. The real move is building up a real history of closed business, either by importing past closed opportunities or giving the pipeline time to mature, so the model finally has something to learn from.
Full Explanation
The correct answer is A. Predictive opportunity scoring is a supervised model: it learns which combination of attributes tends to precede a win versus a loss, which means it needs a meaningful volume of opportunities that have already been closed as won or lost. An environment with 60 open opportunities and no closed history gives the model nothing to train on, so every record shows as insufficient data regardless of how active the pipeline looks. The fix is to build up that closed-opportunity history, either by importing historical closed records from the client's prior system or by letting the new pipeline mature until enough deals have closed. Option B is incorrect because security roles control who can see or edit records, not what data the scoring model has available to train on; granting broader access does not create closed-opportunity history. Option C is incorrect because adding custom fields increases the number of signals available on open records but does nothing to supply the labeled outcomes the model actually needs to learn from. Option D is incorrect because Conversation Intelligence analyzes call recordings and transcripts for a separate set of signals; predictive opportunity scoring is based on opportunity record attributes and historical outcomes, not on whether calls have been transcribed.