A consultant is designing relationship analytics for a strategic accounts team. The team wants the system to surface accounts where the primary buying contact has changed roles within the last 90 days, since a new contact often means the relationship needs to be rebuilt. Relationship analytics in Dynamics 365 Sales draws on interaction history and organizational signals already tracked in the system. What must be true for this specific signal to appear in relationship health insights?
Select an answer to reveal the explanation.
Short Explanation
Here's the core idea: any analytics feature can only spot patterns in data it actually receives, so if nobody's role change ever gets recorded anywhere the system reads, there is nothing to notice, no matter how meaningful that change would be to the sales team. Having an active deal in progress doesn't matter here, since this is about contact turnover, not pipeline stage. Tagging an account as important might help someone decide where to look first, but tagging alone doesn't manufacture the underlying fact of a role change. And running a report meant to uncover unsold product opportunity within an account is a completely different question from tracking whether the buying contact has moved on. The one thing that actually has to happen is that the role change gets captured as real, ingestible data somewhere the system can read it.
Full Explanation
The correct answer is D. Relationship analytics can only reason about signals it can observe, so a contact's role change becomes part of relationship health insights only once that change is captured as ingestible data, whether through a connected professional-network data source, an integration, or a manual update to the contact record. Without that underlying data, there is nothing for the analytics to detect regardless of how important the change is conceptually. Option A is incorrect because an open opportunity is not a prerequisite for relationship health tracking; the contact-role signal is independent of pipeline stage. Option B is incorrect because a custom 'strategic' flag might help prioritize which accounts a team reviews first, but it does not create or surface the underlying role-change data itself. Option C is incorrect because whitespace analysis addresses untapped product and cross-sell opportunity within an account, a different capability from relationship health signals about contact turnover, so requesting it does not produce this insight.