A sales operations manager wants the Sales Qualification Agent to factor in a lead's industry-specific risk score, calculated by a third-party enrichment API that Dynamics 365 Sales does not natively query. The manager wants the score to influence qualification recommendations for every incoming lead without anyone hand-editing agent logic case by case. What should the team do?
Select an answer to reveal the explanation.
Short Explanation
The real question here is how to get outside information flowing into the agent automatically instead of relying on a person to carry it over by hand. Building a small automated flow that calls the enrichment service and drops the resulting score into a field on the lead is the move, because the agent is already set up to read fields like that when it reasons about qualification. Asking reps to type the number in themselves sounds simple, but people forget, get busy, or transpose digits, and now your risk score is only as reliable as the least careful rep on the team. Baking one fixed number into the agent's own instructions is worse in a different way: every single lead would get the same score no matter what industry it actually belongs to, which defeats the whole purpose of an industry-specific signal. And having a separate rule quietly recalculate the whole qualification outcome on its own means the new data never actually reaches the agent's reasoning at all. Automate the plumbing, let the agent read the result.
Full Explanation
The correct answer is A. A Power Automate flow that calls the enrichment API and writes the result to a Dataverse field creates a reliable, automated pipeline: the field updates for every lead without manual effort, and the agent can reference that field in its qualification instructions so the score influences every recommendation consistently. Option B is incorrect because relying on reps to manually look up and type a value introduces inconsistency, delay, and the risk that busy or forgetful reps simply skip the step, undermining the goal of uniform influence on every lead. Option C is incorrect because a static value baked into the agent's instructions cannot vary per lead, so it would apply the same risk score to every prospect regardless of their actual industry, which is not what the manager wants. Option D is incorrect because rewriting the qualification score entirely through a business rule bypasses the agent's reasoning altogether rather than feeding the new signal into it, so the agent's qualification logic never actually incorporates the enrichment data. Automating the data flow into a field the agent already reads is the only approach that is both accurate per lead and maintenance-free.