A consultant is configuring Copilot-driven lead qualification for a client that sells industrial equipment through a network of regional dealers. The client wants Copilot to flag which assigned leads a seller should qualify next, but the dealer network submits leads through a mix of a web form, a partner portal, and manual entry by dealer reps, so lead detail completeness varies widely from one source to another. Sellers report that leads from the partner portal, which capture only company name and phone number, are almost never surfaced by Copilot as ready to qualify, even when those leads are genuinely promising. What should the consultant do to address this pattern?
Select an answer to reveal the explanation.
Short Explanation
When Copilot keeps skipping over leads from one particular source, the instinct is to blame the AI, but the real story is usually that those leads just do not have much to say for themselves. Copilot can only point to evidence it can see, so a lead with nothing but a company name and a phone number gives it nothing to cite as a reason to act now. Renaming the problem or hiding those leads does not change that. The move is to go upstream and get that intake channel capturing the same kind of detail the other channels do, so every lead brings enough substance for Copilot to reason about fairly. Think of it like asking someone to recommend a restaurant from a menu with no dish descriptions versus one with full descriptions; the sparse menu is not badly reviewed, it is just under-described. Fix the menu, not the reviewer.
Full Explanation
The correct answer is A. Copilot's qualification guidance reasons over the data present in a lead record; when partner-portal leads carry only company name and phone number, there is little signal for Copilot to cite as evidence of readiness, so those leads are underrepresented in recommendations even if they would convert well. The fix is a data-quality intervention at the source: enrich or require the fields Copilot needs (such as email engagement, company size, or role information) so partner-portal leads carry comparable signal to leads from other channels. Option B is incorrect because abandoning predictive scoring in favor of pure recency discards the qualification capability the client wants and does not address why partner-portal leads were being underweighted. Option C is incorrect because re-entering a lead through a different form does not add any qualifying data; the underlying sparseness persists and the rework burden falls on sellers for no analytical gain. Option D is incorrect because excluding every incomplete lead from recommendations would suppress a large share of the partner-portal channel outright, hiding leads from sellers rather than helping Copilot reason about them, and would not distinguish a lead that is merely missing a nonessential field from one that lacks any qualifying signal at all.