A consultant reviews a strategic account in Dynamics 365 Sales where the AI-driven relationship health score is rated 'Healthy.' A sales director points out that the primary economic buyer has not opened an email or accepted a meeting in four months, while three junior stakeholders remain highly engaged, and asks why the score does not reflect this risk. How should the consultant respond?
Select an answer to reveal the explanation.
Short Explanation
An account score is a group photo, not a portrait of one person. When it blends everyone connected to an account into a single healthy or at-risk label, a few enthusiastic junior contacts can easily smile bright enough to hide the one senior buyer who has quietly gone dark. That is exactly what is happening here: the rollup looks fine because most of the people in it are engaged, even though the one relationship that actually decides the deal has cooled off. The fix is not to distrust the scoring engine or throw the feature out, since nothing about it is broken. It is to zoom in from the group photo to that one person's individual engagement history, where the real signal about the buyer's disengagement is still sitting, uncounted, at the account level.
Full Explanation
The correct answer is C. An account-level relationship health score summarizes engagement signals, such as email responsiveness and meeting activity, across every contact tied to the account, so strong activity from several engaged stakeholders can offset a single disengaged contact and keep the overall label at Healthy. To see the risk the sales director is describing, the consultant should look at the individual contact's own engagement trend rather than the blended account figure, since the two are measuring different things. Option A is incorrect because the discrepancy is an expected consequence of how an aggregate score is calculated, not evidence that the model is producing faulty predictions. Option B is incorrect because contact-level engagement data already exists and can be reviewed; disabling the feature entirely discards a useful account-level signal instead of supplementing it with the missing granularity. Option D is incorrect because it assumes a data-quality error such as duplicate or misattributed records, when nothing in the scenario suggests the buyer's activity is being logged incorrectly, only that it is being diluted by other contacts' engagement in the rollup.