How to predict churn from HubSpot tickets
Use HubSpot Service Hub tickets, pipelines, properties and feedback surveys (CSAT, NPS, CES) to build early churn warnings with reports and workflows.
By Florian
If your support runs on HubSpot, your tickets already sit in the same CRM as your contacts and companies. That is an advantage most help desks do not have: you can put a ticket, a survey answer and the account it belongs to in one report, without exporting anything.
This guide shows how to turn that into an early warning for churn: which ticket properties and survey answers to watch, how to set them up in Service Hub, and how to build reports and workflows that flag at-risk accounts before renewal. It relies on HubSpot’s own knowledge base: ticket pipelines, default ticket properties, customer support surveys, customer satisfaction surveys, loyalty (NPS) surveys, analyzing survey responses, help desk reports and workflow enrollment triggers (all accessed November 2026).
Leading vs lagging signals
A cancellation is a lagging signal: by the time you see it, the decision is made. What you want from support data are leading signals, things that tend to happen weeks before. In HubSpot terms, these fall into three groups:
- What customers contact you about (ticket category, pipeline, your own properties).
- How the contact went (reopened tickets, time waiting on your team, effort).
- What customers tell you when asked (CSAT, CES and NPS survey answers).
None of these predicts churn on its own. The point is to collect them consistently so you can check, against your own cancellations, which ones actually came first.
Set up the ticket side
Pipelines and statuses
HubSpot’s pipeline guide describes the default Support Pipeline with four statuses: New, Waiting on contact, Waiting on us and Closed. For churn work, two things help:
- A separate pipeline for billing and account requests (cancellation, downgrade, refund, invoice questions). It keeps those tickets out of general support reports and lets you attach a specific survey to them, since each ticket pipeline can be linked to one support survey.
- Watching reopened tickets. HubSpot’s help desk docs say a reply to a closed ticket reopens it and moves it to the first open status in the pipeline. A ticket that keeps coming back is a customer whose problem was not solved.
Properties
HubSpot’s default ticket properties include Category, described as the main reason the customer reached out. On Service Hub Enterprise it can be set by AI from the first message, using default and custom options; this setting is off by default.
On other plans, or in addition, create your own ticket properties. A practical minimum:
| Property | Type | Why |
|---|---|---|
| Churn risk reason | Dropdown | Cancellation request, Price, Missing feature, Bug, Competitor, Onboarding, None |
| Mentions leaving | Checkbox | Agent ticks it when the customer mentions cancelling or switching |
| Affected feature | Dropdown | Lets you see which product areas generate risk |
Keep the dropdown short. If agents have to think about which value to pick, they will pick “Other”.
Set up the survey side
HubSpot’s feedback surveys support three standard measures. Ticket and feedback submission properties need Service Hub Professional or Enterprise.
| Survey | What it measures | Scale per HubSpot’s docs | Best for |
|---|---|---|---|
| Customer support survey (CES) | Effort to get an issue resolved | 1–7: 1–3 Difficult, 4–5 Neutral, 6–7 Easy | Effort after a ticket |
| Customer satisfaction (CSAT) | Satisfaction with an interaction | Stored as 0–2: Unhappy, Neutral, Happy | A specific interaction |
| Customer loyalty (NPS) | Likelihood to recommend | 0–10: Detractor 0–6, Passive 7–8, Promoter 9–10 | The overall relationship |
Details from HubSpot’s customer support survey guide that shape how you use them:
- A ticket-based survey is sent when a ticket in the selected pipeline is closed, immediately or after a delay you choose.
- It is sent once per ticket. If the ticket reopens and closes again, no second survey goes out.
- Responses are associated with the contact, the company and the ticket.
HubSpot calculates NPS as the percentage of promoters minus the percentage of detractors (analyzing survey responses).
For churn, the comment field matters more than the score. “Third time I have reported this” next to a Difficult rating is the kind of line you want someone to read the same day.
Reports that surface risk
HubSpot’s help desk report builder lets you choose tickets, conversations, contacts, companies or feedback submissions as the primary data source, then add secondary sources. Reports worth building:
- Companies with tickets marked “Mentions leaving” in the last 90 days, with their renewal date or plan from your CRM properties.
- Feedback submissions with Difficult effort or Unhappy satisfaction, grouped by company, so one bad week for one account stands out.
- Ticket count per company per month in the billing pipeline, to spot accounts whose billing questions are rising.
- Churn risk reason over time, to see whether “Price” or “Missing feature” is growing.
Then check them against reality. Once a month, take the companies that cancelled and look at what their tickets and surveys showed in the 60 to 90 days before. If a signal rarely appears before cancellations, drop it. Our guide on finding what predicts churn explains how to do this without confusing correlation and cause.
HubSpot also offers a customer success workspace with a configurable health score. If you use it, the properties above are candidates for it, once you have checked they actually come before churn.
Workflows that act on signals
HubSpot’s enrollment triggers guide says feedback submissions can be enrolled based on their properties, such as sentiment or survey name, and on associated contact and ticket information. The workflow actions include creating tasks. Two workflows and one routine cover most of the value:
- Negative feedback follow-up. Enroll feedback submissions with negative sentiment; create a task for the account owner to read the comment and reply within a working day.
- Leaving mentioned. Enroll tickets where “Mentions leaving” is checked; notify the account owner and set a follow-up task. The follow-up is a conversation, not a sales pitch.
- Repeat contact. Review report 3 weekly and create a task for any company above the threshold you chose. Automate it later, once you know the threshold is meaningful.
One line not to cross: when a ticket is a cancellation request, the workflow should never delay the cancellation. Cancel when asked, confirm in writing, and if you want to understand why, ask one optional question. See our notes on click-to-cancel rules.
A checklist to start this week
- Create a billing and account pipeline, or a property that separates those tickets.
- Add “Churn risk reason” and “Mentions leaving” ticket properties.
- Turn on a customer support survey for the main pipeline.
- Build the four reports above.
- Add the negative feedback workflow.
- Book a monthly review comparing signals with actual cancellations.
Doing this with NoChurn
NoChurn’s HubSpot connector is read-only: it reads tickets and conversations and never writes to HubSpot. Conversations are matched to your customers by email; doubtful matches are suggested for you to confirm and never merged automatically. NoChurn combines them with your billing data in a churn score from 0 to 100 and a churn drivers view that ranks which attributes are most correlated with churn (correlation, not causation), and keeps the messages as dated, verbatim evidence for disputes on Stripe and Braintree. Pipelines, surveys, reports and workflows stay in HubSpot. See NoChurn + HubSpot.