A sales operations manager reviewing the Sales Order Agent's activity notices that purchase orders emailed by a long-standing wholesale customer are being converted with the wrong unit of measure roughly one in five times, even though the product SKUs match correctly. Investigation shows the customer's PO documents list quantities in 'cases' while the Dynamics 365 product records default to 'each' as the base unit. What should the consultant do to reduce this error rate?
Select an answer to reveal the explanation.
Short Explanation
The pattern here is narrow: one customer, one recurring mix-up, always the same kind of quantity language. That points straight at a translation gap rather than a broad trust problem with the agent, so ripping out automation for this account is overkill for something that has a precise fix. Pushing the fix onto the customer by asking them to rewrite how they've always written purchase orders ignores that adapting to real-world documents is exactly what this kind of automation is for. And turning up caution for every customer everywhere would slow down all the orders that were never wrong in the first place, just to patch one account's issue. The tidy solution is teaching the system that when this particular customer says 'cases,' it means a specific converted quantity, so it stops guessing wrong.
Full Explanation
The correct answer is C. The root cause is a unit-of-measure mismatch between how this customer phrases quantities and how the product catalog is structured, not a general reliability problem with the agent. Adding a mapping that teaches the agent to translate this customer's 'cases' language into the correct unit-of-measure schedule quantity directly fixes the misinterpretation at its source. Option A is incorrect because disabling automation for the customer removes the efficiency benefit entirely to work around a fixable data-mapping gap, which is a disproportionate response. Option B is incorrect because it shifts the burden onto a long-standing customer to change their own documentation practices rather than adapting the system to handle a legitimate and common real-world quantity format. Option D is incorrect because raising the confidence threshold across all customers would suppress correct conversions for other customers whose documents do not have this specific ambiguity, without addressing the actual mismatch causing this customer's errors.