Relationship Risk agent
Champion Loss Detector
Flags a champion gone silent, changed roles or left - while there is still time to rebuild the relationship.
What does Champion Loss Detector do?
Champion Loss Detector is an AI agent that watches your champion's engagement on every account and flags the moment they go quiet - 21 or more days without contact, a role change, or a departure - so a CSM can act while there's still time to find a new stakeholder, not after the renewal call goes to voicemail. It runs fully autonomously by default: no CSM has to remember to check.
What signals does it watch?
The agent reads contact and signal activity for the champion on record for each account, comparing it against that account's own baseline rather than a fixed rule that treats a quiet enterprise buyer the same as a chatty startup founder.
- No email, call or meeting activity from the champion contact for 21+ consecutive days
- A role or title change detected on the contact record
- An out-of-office reply that reads as a departure, or a bounced email address
- A sustained drop in the champion's own engagement compared to their account's history
What actions does it take?
Once a champion-loss signal fires, the agent does two things immediately, then gets out of the way for a human to take it from there.
- Raises a signal on the Signals dashboard, scoped to the account and visible to the owning CSM
- Creates a re-engagement task on the Tasks dashboard, so it shows up in Today's Focus rather than getting buried
- Feeds into the relationship pillar of the account's six-pillar health score
- Runs at the fully-autonomous tier by default - set it to notify-only or suggest-and-approve per segment if you'd rather review first
Which workflows use Champion Loss Detector?
Champion Loss Detector is the trigger for the seeded Champion Loss workflow, which routes the re-engagement sequence through Playbook Executor once the signal fires.
What does this look like in practice?
A $180K account goes quiet: the champion who championed the original deal stops replying to a CSM's check-ins. Three weeks pass with nothing - no email opens, no meeting requests answered. Champion Loss Detector flags it on day 21. The CSM checks LinkedIn, finds the champion moved to a new role internally two months ago, and identifies their replacement from the account's contact list. A re-engagement email goes out to the new stakeholder that week, well before the renewal conversation would otherwise have started cold.
Frequently asked questions about Champion Loss Detector
- What exactly counts as "champion loss"?
- Any of: 21+ days of silence from the on-record champion, a detected role change, or a departure signal like a bounced email or an out-of-office reply. The agent flags whichever fires first, so you're not waiting for all three.
- Does it need an email integration connected to work?
- It works best with Gmail or Outlook connected, since email activity is the clearest signal of engagement. Without one, it still watches CRM contact updates and call logs for role-change and activity signals.
- Can I change the 21-day threshold?
- Yes - it's a setting, not a hardcoded rule, and you can set it per segment so a fast-moving longtail account and a slower enterprise one aren't held to the same clock.
- What happens after it flags a lost champion?
- A signal and a task are created immediately. If the account is on the Champion Loss workflow, Playbook Executor picks up the re-engagement sequence automatically at whatever tier you've set for that segment.
See Champion Loss Detector on your own accounts.
Book a 30-minute demo, or connect your stack and try it free for a week.