A consultant reviews the AI-driven relationship health score for a long-standing strategic account and finds it rated At Risk despite the account manager insisting the relationship is strong, with weekly phone calls and an in-person visit last month. Investigating further, the consultant finds that the account manager logs these interactions in a personal notebook and enters them into Dynamics 365 only sporadically, weeks after they occur. What is the best explanation for the low score?
Select an answer to reveal the explanation.
Short Explanation
The model can only work with what actually makes it into the system, and here the real relationship activity was happening entirely off to the side in a personal notebook, so as far as Dynamics could tell, almost nothing was happening on this account at all. That gap between what is true in the field and what is recorded in the CRM is exactly the kind of thing that drags a health score down even when the underlying relationship is genuinely solid. It is worth resisting the urge to blame the model for being narrow-minded about channels, or to assume it only refreshes rarely, or to think a quiet pipeline alone explains an At Risk label; none of those match how the scoring actually weighs things. What actually needs to change is behavior, not configuration: get the account manager logging interactions promptly, close to when they happen, and the score will start reflecting the relationship that has been there all along.
Full Explanation
The correct answer is C. Relationship health scoring draws heavily on the recency and frequency of engagement activities as recorded in Dynamics 365; it has no visibility into interactions that happen but are never entered into the system, or that are entered only after a significant delay. Because the account manager's weekly calls and recent visit lived in a personal notebook rather than the CRM, the model had no timely data to reflect a healthy, active relationship, and the score understandably trended toward At Risk. This is a data-entry problem, not a model failure. Option A is incorrect because relationship health incorporates a broader set of activity types, not solely email and Teams chat; phone calls and in-person visits, once logged, are legitimate signals. Option B is incorrect because the absence of a new opportunity is not the dominant or exclusive driver of the score; engagement recency and frequency carry substantial weight independent of open pipeline. Option D is incorrect because relationship health scores update far more frequently than annually, so a full year of staleness is not a plausible explanation for a score that should reflect the account manager's recent activity once logged.