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?

The correct answer is that predictive scores are computed on a periodic refresh cycle rather than the instant a record is created, so imported leads will receive scores once the next scoring run completes. 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 like any other lead. The claim that imported leads are permanently excluded from predictive scoring because they originated from a data import instead of manual entry is incorrect because how a record entered the system, whether typed by a seller or brought in through an import, has no bearing on whether the model considers it eligible for scoring. The claim that the import must have failed to map a required field, since predictive scoring computes instantly the moment any new lead is created, 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. The claim that predictive scoring must be manually re-enabled in settings after any bulk data import before it will resume scoring 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 reconfiguration.