How do I run a save play for an at-risk customer?

Run a save play by diagnosing the root cause from the health signals, assigning a clear owner and a concrete action with a deadline, and tracking the outcome, so retention is a repeatable motion rather than a heroic scramble every time. A good save play turns a health alert into a resolved account.

The signals behind the play come mostly from your own internal history, revenue, support, and product usage tracked over time, the record most tools skip while reading only external public data. SignalRx scores accounts and their contacts, lets inference decide which source to trust, and writes the result into Salesforce as the Revenue Plays and lists the CSM works, so a decline shows up weeks before the customer says anything.

This guide covers the save motion itself. For how accounts are ranked before you run it, see How do I prioritize at-risk accounts? For the full detection-to-action motion around it, see How do I catch at-risk customers?

How does a save play start?

With the reason, not a generic check-in. The Health Score's attached signals (usage dropped, tickets spiked, a champion left) tell the CSM what to address, so the first conversation is specific and credible instead of a vague how-are-things call that tips the customer off that you were not watching. Most of those signals are internal, but the champion-left one is sourced externally, caught from a LinkedIn job or title change (and the web where an acquisition is behind it), then combined with the internal decline so the play fires on the full picture.

What are the steps?

Diagnose the cause, assign the right owner, take a concrete action with a due date, and record the outcome. Standardizing these steps is what makes saves coachable and measurable rather than dependent on one heroic CSM.

Illustrative example

Illustrative, based on how SignalRx customers work. An account turns At Risk with a usage drop and a disputed overage attached. The CSM diagnoses a billing misunderstanding, loops in the account executive to fix the contract, and sets a two-week deadline. Two weeks later the overage is resolved, usage recovers, and the outcome is logged as saved with the cause recorded, so the same friction can be prevented on similar accounts.

How do I learn from save plays?

Track which causes are savable and which actions work, so the play improves and prevention gets better over time. What saves an FQHC differs from what saves a specialty pharmacy, a specialty group, a senior living operator, a behavioral health provider, a dental or aesthetics group, or an MSO or PE-backed platform, so tracking the cause by setting is what sharpens the play. Where a record is missing the ownership or site detail that shaped the risk, SignalRx fills it from public sources so the diagnosis holds. Feeding the results into what leadership measures closes the loop between the front line and the renewal-risk report.

Key takeaways

• Start from the specific cause, not a generic outreach.
• Assign owner, action, and deadline, then record the outcome.
• Track what works so the play and prevention both improve.

See it in action: Increase Customer Revenue with SignalRx.

Related: How do I prioritize at-risk accounts? and How do I catch at-risk customers?