A consultant bulk-imports several thousand historical leads into a client's Dynamics 365 Sales environment where predictive lead scoring is already enabled and running well. Immediately after the import finishes, sellers notice the newly imported leads show no Score or Grade value, while existing leads display theirs normally. What should the consultant tell them?
Select an answer to reveal the explanation.
Short Explanation
Nothing is actually broken here, the scores just have not caught up yet. Predictive scoring does not recalculate the instant a lead appears, it runs on its own periodic cycle, and dumping a few thousand leads in all at once just means those records are waiting for the next pass rather than getting evaluated the second they land. That is normal, expected behavior, not a sign of a botched import or a setting that got flipped off. Give it until the next scoring run and those blank fields should fill in just like every other lead's did. What would be wrong is assuming import origin somehow disqualifies a lead from scoring forever, assuming a missing score right after import proves a mapping error happened, or assuming someone needs to go flip a switch back on. None of that is true, patience and the next scheduled cycle are all that is needed.
Full Explanation
The correct answer is C. Predictive lead scoring evaluates records on a periodic scoring cycle rather than recalculating the instant each record is created, so a large batch of leads dropped in all at once will simply sit without a Score or Grade until the next scheduled run processes them, at which point they will be scored the same as any other lead. Option A is incorrect because how a record entered the system, whether typed in by a seller or brought in through an import, has no bearing on whether the model considers it eligible for scoring. Option B is incorrect because it rests on a false premise; scoring is not instantaneous for any lead, imported or manually created, so the absence of an immediate score does not by itself indicate a mapping failure. Option D is incorrect because there is no requirement to manually toggle predictive scoring back on after an import; the feature keeps running and will pick up the new records on its normal cycle without any reconfiguration.