A consultant enabled predictive opportunity scoring for a sales team last quarter, and the model has generated scores reliably for existing pipeline records ever since. A rep creates a brand-new opportunity this morning for a fast-moving deal and opens the record expecting a score, but the score field shows 'Not enough data' instead of a number. The consultant confirms the rep's security role includes the AI scoring feature and that scoring is active for this pipeline. What is the most likely explanation?
Select an answer to reveal the explanation.
Short Explanation
New records need time to build a track record before the model will put a number on them. Think of it less like a broken feature and more like asking someone to predict a race's outcome before the runners have taken a single lap — there just isn't enough to go on yet. Since the rest of the pipeline is scoring fine and the access checks came back clean, the licensing and configuration explanations don't hold up: those problems would show up everywhere, not on one fresh record. A sync delay is tempting to blame, but the scoring engine reads straight from the same database the record lives in, so there's no separate pipe that could be lagging. The real story is simpler: the deal is too young. Give it some activity — emails, calls, stage movement — and the score will populate once the model has enough signal to trust its own estimate.
Full Explanation
The correct answer is B. Predictive opportunity scoring depends on the model observing enough signals, such as activity history, stage progression, and engagement, before it can produce a confident score; a record created minutes earlier simply has not generated that history yet, which is exactly what 'Not enough data' communicates. Option A is incorrect because a missing license would block AI features across the rep's entire environment, not just this one new record, and the consultant already confirmed the role has access. Option C is incorrect because excluding a record type from the model's scope is an organization-wide configuration choice; it would prevent scoring for every opportunity of that type, not only newly created ones, and the team's existing pipeline is scoring normally. Option D is incorrect because Dynamics 365 Sales and its AI scoring model operate natively on Dataverse without a separate synchronization step, so there is no sync lag to account for; a sync problem would also produce broader symptoms across many records rather than a single new opportunity showing a data-insufficiency message.