A consultant is configuring relationship analytics for an enterprise accounts team that has repeatedly lost late-stage deals after their single primary contact left the customer's organization. The team wants the system to flag opportunities where meaningful engagement, such as emails and meeting attendance, exists with only one contact at the account, so reps are prompted to build relationships with additional stakeholders earlier. Which relationship analytics capability should the consultant configure?
Select an answer to reveal the explanation.
Short Explanation
The real risk here is not too little engagement, it is engagement that is all resting on one person's shoulders. A score that only tracks how often reps email that one favorite contact would actually climb higher the more the team leans on that single relationship, which is precisely the trap they fell into before. Comparing products against what similar accounts buy is a useful exercise for finding upsell room, but it says nothing about how many people are actually engaged. Counting heads on a video call captures a narrow slice of the picture and does not proactively tell anyone there is a problem. What the team needs is something that looks across every channel of engagement, notices when it is all funneled through one contact, and actively nudges the rep to go find more stakeholders before that single thread snaps.
Full Explanation
The correct answer is D. The team's problem is a lack of multi-threading, meaningful engagement is happening but it is concentrated on one person, so the needed capability is an alert built specifically to detect that concentration pattern across all engagement types and prompt reps to broaden it. Option A is incorrect because a score based purely on email frequency with the primary contact would rise as engagement with that one contact increases, rewarding exactly the narrow pattern the team wants flagged rather than warning against it. Option B is incorrect because whitespace analysis identifies cross-sell and upsell opportunities based on product gaps relative to peer accounts; it has nothing to do with how many people at an account are engaged. Option C is incorrect because a call-attendee tracker only reflects who joined recorded meetings, missing email engagement entirely, and it merely counts participants rather than generating a proactive alert that prompts reps to multi-thread. Only an alert purpose-built to detect single-contact concentration across engagement channels and nudge reps toward broader outreach addresses the risk the team experienced when their sole contact departed.