Skip to content
HubSpot Updates

Customer States and Follow-up Actions in HubSpot Service Hub

October 27, 2026

What This Update Actually Is

HubSpot shipped a structured state system inside the Customer Success Workspace. It gives customer success managers a set of named, trackable conditions that can be applied to any customer record.

States fall into three categories: lifecycle states like In Onboarding, Customer Activated, and Upcoming Renewal; risk states like Declining Usage, High Ticket Volume, Critical Support Ticket, No Recent Touchpoint, Cancellation Indicated, and Ticket SLA Violation; and one opportunity state, Increasing Usage.

Each state can open automatically based on trigger logic, or a CSM can open it manually for edge cases. States close automatically when conditions clear, or manually when the CSM resolves them.

Follow-up actions are attached to each state. Managers define what should happen when a state opens: send an email, create a task, enroll the customer in a sequence, unenroll them from one, or fire a Slack or Microsoft Teams notification. Breeze can also draft the email if you want AI-assisted outreach built right into the response.

Why HubSpot Shipped This

Customer success teams have always had the intent to be proactive. The data, though, gets buried in ticket feeds, contact timelines, and note fields. A CSM has to dig to know that a customer's usage dropped three weeks ago, and by the time they find it, the window to intervene has usually closed.

The internal frustration is familiar: the humans doing this work aren't lazy or careless. They're overwhelmed by a portal that shows them everything but surfaces nothing. Every CSM develops their own mental checklist, and no two checklists match.

States solve that by making the customer's current situation visible on the record itself, not buried in a report or a spreadsheet someone exports on Fridays. Follow-up actions solve the inconsistency: when a Cancellation Indicated state opens, every CSM on the team does the same thing, not whatever they remember to do.

How to Use It Step by Step

  1. Open the Customer Success Workspace. States are on by default, so default states are ready to use without any manual configuration.
  2. Turn states on or off for all customers or for specific customer segments. If a state isn't relevant to a segment (say, Ticket SLA Violation for customers on a self-serve plan), turn it off for that segment to keep views clean.
  3. Review the default trigger logic for each state. Customize triggers for your business when the defaults don't match your definition of, for example, "declining usage."
  4. Define follow-up actions for each state. Assign them to the correct customer segments. Decide whether each action runs automatically or creates a task for the CSM to complete.
  5. For sequenced or delayed follow-up (for example, send an email on day 1, create a call task on day 3), use states as a workflow trigger instead of relying only on workspace follow-up actions. Workspace actions run all at once with no delay between them.
  6. Build workspace views filtered by state. State summary cards appear on the Summary tab of each customer record. Use these views for daily CSM standup or as a queue for intervention priorities.
  7. Open states manually for edge cases, such as a customer who calls to flag an issue that hasn't yet triggered automatic detection. Close them manually when the situation resolves.

What It Touches in Your HubSpot Strategy

This update connects more systems than it might look like on the surface. Here's where the ripple goes.

Workflows are now the sequencing layer for customer success motions. The workspace handles simple, instant actions. Workflows handle anything that needs timing, branching, or logic. That's a clean division your RevOps team should document explicitly.

Key Takeaway

Don't treat workspace follow-up actions and workflows as interchangeable. Workspace actions fire all at once. Workflows give you delays, branches, and enrollment conditions. Use them together, not as alternatives.

Contact and company records now carry state data as a visible signal. That means your existing CRM segments, lists, and reporting can reference state when you build filters. It also means a sales or account expansion rep looking at a record can see that a customer is in Increasing Usage state without needing to ask the CSM.

Sequences get a new trigger point. Enrolling or unenrolling a customer from a sequence as a follow-up action connects your customer success motion to the same sequences your sales team uses. That consistency matters when an expansion opportunity opens and the handoff to account management needs to feel seamless.

Breeze enters the picture through AI-drafted emails on follow-up actions. If your team wants AI-assisted outreach as part of a state response, it's now built into the motion rather than a separate step.

If you're also building out AI-assisted service workflows, it's worth reading about how Breeze recommends Customer Agent deployment based on real conversation volume. The two updates work toward the same goal: getting the right response to the right customer faster.

Reporting is the underrated win here. Once states are running, you can track how long customers spend in each state, how often Cancellation Indicated closes to Customer Activated, and whether your follow-up actions actually change outcomes. That's retention data that most Service Hub portals have never had before.

Key Takeaway

State duration data will become one of your strongest retention signals. Start capturing it now, even before you have a formal reporting dashboard built. The historical record builds value over time.

If your team is also setting retention and expansion goals in HubSpot, the bulk goal cloning update pairs well here. You can clone your current-quarter customer success goals and map them directly to state-based performance metrics.

Who Should Care Most

Customer success managers on Service Hub Professional or Enterprise are the direct audience. This is built for them.

  • Use states as a daily queue filter so you prioritize high-risk customers before the ones who are stable, without needing a separate spreadsheet to triage.
  • Use follow-up actions to enforce team playbooks automatically, so new CSMs run the same plays as your most experienced humans from day one.
  • Use state-triggered workflows for multi-step retention sequences when you need timing and branching that workspace actions can't handle.

RevOps leaders should also pay close attention. States are structured data objects. That means they're reportable, segmentable, and linkable to revenue outcomes. A RevOps team that maps state transitions to expansion revenue or churn events will have a material advantage in forecasting.

Companies that will see the most immediate value: SaaS businesses with usage-based signals, subscription companies approaching renewal cycles, and any organization where the customer success team has grown faster than its documented playbooks.

George's Take

We've worked inside a lot of portals where the customer success team is doing genuinely heroic work, but it's invisible and unsystematic. The CSM who's been there four years holds all the institutional knowledge in her head. The one who joined six months ago is guessing. States change that dynamic. They make the playbook structural, not personal. And the follow-up action system means your retention motion doesn't depend on whoever happens to check the queue first. That's not just an efficiency gain. It's a fairness upgrade for your customers, who deserve a consistent experience regardless of which human picks up their record on a given Tuesday.

“The best retention systems aren't the ones with the smartest CSMs. They're the ones where every CSM knows exactly what to do next, every single time, because the system tells them.”
— George B. Thomas

If you're thinking about where AI fits alongside structured systems like this one, our piece on human-centered AI and what it means for your go-to-market motion is worth a read. Humans set the trajectory. Tools like states and Breeze add the speed.

If you want help mapping Customer States to your existing segments, building the right follow-up actions for each state, or connecting this to your RevOps reporting layer, that's exactly the kind of work we do at Sidekick Strategies. Book a strategy call and let's build a retention system your whole team can rely on.

Frequently Asked Questions

What are HubSpot Customer States?

HubSpot Customer States are structured labels applied to customer records inside the Customer Success Workspace. They represent lifecycle stages like In Onboarding or Upcoming Renewal, risk signals like Declining Usage or Cancellation Indicated, and opportunity signals like Increasing Usage. States open automatically based on trigger logic or manually by a CSM.

Which HubSpot plans include Customer States and Follow-up Actions?

Customer States and Follow-up Actions are available on HubSpot Service Hub Professional and Service Hub Enterprise. They're not available on Free or Starter tiers.

What's the difference between workspace follow-up actions and workflows for customer states?

Workspace follow-up actions fire all at once the moment a state opens. They don't support delays or conditional branches. Workflows support sequenced timing, delays, and branching logic. Use workspace actions for instant responses and workflows for multi-step retention plays that need structure over time.

Can customer states open automatically, or does a CSM have to set them?

Most states open automatically based on trigger logic configured in the workspace. For example, a Declining Usage state can open when usage drops below a defined threshold. CSMs can also open any state manually to cover edge cases that automation doesn't catch.

Can I use HubSpot Customer States in reports and workflows?

Yes. States are structured data on the customer record, so you can filter workspace views by state, use states as workflow enrollment triggers, and reference state data in HubSpot reports. This makes it possible to track retention metrics like time in state and state-to-outcome conversion rates.

How does Breeze AI connect to Customer States follow-up actions?

When you configure a follow-up action to send an email, you can choose to have Breeze draft it. This means AI-assisted outreach is built directly into the state response rather than requiring a separate manual step, so CSMs get a ready-to-review draft the moment the state opens.

Live Workshop

HubSpot Super Admin Workshop

Stop reacting to requests and start running your portal like the architect it needs. You leave with a filled-in plan, not just notes.

$999 · January 8, 2027 · Live virtual

Free, In Your Inbox

Get Every HubSpot Update

No spam. Unsubscribe anytime.

Comments

Join the conversation. Share what resonated, ask questions, or add your perspective.

Leave a Comment

We'd love to hear your thoughts. Your comment will appear after review.

Never shared publicly.

0/2,000

Ready To Talk?

Need Help Making Sense of HubSpot?

Sidekick Strategies helps your humans get the most out of every HubSpot update, feature, and tool. Let's make your portal work harder for you.