A sales manager at a client manually sets the Rating field to Hot on a lead she has strong personal conviction about. Days later, predictive lead scoring runs and assigns that same lead a Cool grade based on its activity history. She is worried the system has overwritten her judgment. What should the consultant tell her?
Select an answer to reveal the explanation.
Short Explanation
Her instinct that something got overwritten makes sense, but nothing actually collided here. The rating she typed in by hand and the grade the model calculated live in two completely separate fields, they just happen to sit near each other on the same lead. Setting one does not touch the other, so her Hot rating is sitting right where she left it even after the model comes back with a Cool grade of its own. What would be wrong is assuming the computed grade wins and quietly stomps over her input, or that the rating field disappears once scoring is turned on, or that some behind-the-scenes process kicks the lead upstairs for review because the two values disagree. None of that happens automatically. The two numbers are just two different opinions sitting side by side, and it is up to the seller to decide how much weight to give each one.
Full Explanation
The correct answer is C. The Rating field is a manually maintained option-set field that exists independently of the Score and Grade fields that predictive lead scoring computes, so her Hot rating is untouched by the scoring run and both values simply coexist on the record for sellers to weigh together. Option A is incorrect because predictive scoring does not write to or overwrite the Rating field at all; the two fields are tracked and updated through entirely separate mechanisms. Option B is incorrect because enabling predictive lead scoring does not remove the Rating field from the form or restrict it from manual entry; it remains available for sellers to use as they always have. Option D is incorrect because there is no built-in workflow that detects a mismatch between a manual rating and a predictive grade and automatically escalates it; any such review process would have to be built separately and is not part of the feature's default behavior.