All recipes
Support Action

Churn risk watch

Flag accounts with usage decline, sentiment red flags, or unanswered tickets — before the renewal call.

Eluu — churn-risk-watch
Shown in preview
Zendesk Salesforce Slack
Runtime ~5 min per run
Tokens ~18K per run
Owner a CS colleague

Works with

Pick whichever tool your team already uses.

  • CRM
    HubSpot Salesforce Pipedrive
  • Messaging
    Slack
  • Support
    Zendesk Intercom
Salesforce
Salesforce Read usage
Zendesk
Zendesk Aging + sentiment
Salesforce
Account signals NPS + escalations
Slack
Slack Alert CSM

What it does

The accounts that churn are usually the ones nobody warned the CSM about. This recipe runs a daily three-signal scan — usage decline, support sentiment, and in-app churn language — and DMs the CSM whenever an account crosses the risk threshold, with a one-page digest of why.

How it works

  1. Read usage trends. The colleague pulls every active account’s last 30-day usage and compares against the trailing 90-day baseline.
  2. Score support tickets. Open tickets are pulled, aged, and run through sentiment analysis on the latest replies. Aging > 5 business days is flagged.
  3. Layer in account signals. NPS responses, escalation flags from the CRM, and explicit churn-language mentions are added to the score.
  4. Alert the CSM. Accounts crossing the risk threshold get a one-page digest DMed to their assigned CSM, with a deep link back to the CRM.

Setup

  • Connect a CRM (HubSpot, Salesforce, or Pipedrive) for account ownership and contract data.
  • Connect a support tool (Zendesk or Intercom).
  • Connect a messaging channel (Slack) for the alerts.
  • Set the risk threshold and the per-CSM alert quiet-hours.

Variations

  • Add a leadership digest summarizing all flagged accounts in one rollup.
  • Auto-create a save-play task in the CRM for each newly-flagged account.