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 - a bounce, a "no longer with the company" reply, a CRM contact change, news of a departure, or simply silence for three times their own usual gap (minimum 21 days) - 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, and it suggests a successor from the account's own contact list.
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.
- A bounced email address for the champion contact
- A "no longer with the company" auto-reply
- A CRM contact change, or news of a departure
- Quiet for 3× the champion's own usual contact gap, with a 21-day minimum
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
- Suggests a successor from the account's own contact list where one is on record
- 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 with its step set to do automatically by default - set it to needs approval or just notify for any Profile where 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: a bounce, a "no longer with the company" reply, a CRM contact change or news of a departure, or quiet for 3× the champion's own usual gap (minimum 21 days). The agent flags whichever fires first, so you're not waiting for all of them.
- 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 news for role-change and departure signals.
- Can I change the 21-day minimum?
- Yes - it's a setting, not a hardcoded rule, and you can set it per Profile so a fast-moving Self-Serve account and a slower High-Touch 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 step mode you've set for that Profile.
See Champion Loss Detector on your own accounts.
Book a 30-minute demo, or connect your stack and try it free for a week.