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?

The correct approach is the Power Automate flow that calls the enrichment API and writes the result to a Dataverse field. That 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. The option asking reps to look up the risk score manually and type it into the lead's description field is incorrect because relying on people introduces inconsistency, delay, and the risk that busy or forgetful reps simply skip the step, undermining the goal of uniform influence on every lead. The option adding the risk score as a static value in the agent's topic instructions is incorrect because a fixed value 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. The option configuring a business rule that recalculates the qualification score entirely is incorrect because rewriting the qualification outcome through a separate 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.