Hops

Search documentation

Search pages by title, headings and content

Churn signals

Combine tickets, sentiment and usage into one churn-risk list.

Churn shows up in tickets long before it shows up in a cancellation. Hops reads tickets and account data every morning and keeps one list of at-risk accounts.

What it does

  • Looks for the signals. Cancellation questions, repeat issues, negative sentiment and silence after escalations.
  • One row per account. Signal, owner and status, so the list stays easy to scan.
  • Finds the owner. Hops reads owners and renewal dates from HubSpot or Salesforce.
  • Posts only what is new. Accounts already on the list are not repeated.

Ask Hops

Copy a prompt into any chat with Hops, or mention @Hops in a Space.

Plain text
Which accounts show churn signals this week?
Plain text
Why is Hooli on the at-risk list?
Plain text
Show at-risk accounts renewing in the next 60 days.
Plain text
List accounts that went silent after an escalation.

Example reply:

6 accounts at risk:

  • Hooli: 3 negative tickets and a cancellation question.
  • Umbrella reported the same bug 4 times.
  • Churn-risk table updated.

What you get

  • A Slack or Space post each weekday with new at-risk accounts.
  • Updated Tables in the Space with one row per account, signal, owner and status.
  • On-demand checks for any account or segment.

Connections needed

Connect these apps. Each card opens Connections in the app.

Tickets and sentiment (or Intercom).

Deals, contacts and owners (or Salesforce).

Where Hops posts the results and nudges owners.

Set it up

  1. Connect your apps

    Connect the apps above in Connections.

    See Connections.

  2. Pin context

    Create a support Space and pin your churn-signal definitions in Space context.

    See Spaces and Space context.

  3. Add the skill

    Create a skill with this prompt so the output has the same format every time.

    Plain text
    You detect churn signals. Look for cancellation questions, repeat issues, negative sentiment and silence after escalations. Keep one row per account with signal, owner and status.

    See Build a skill.

  4. Schedule it

    Run every weekday at 8:00 AM. Hops posts new at-risk accounts to the support Space and updates the churn-risk Table.

    See Automation.