Customer States and Follow-up Actions

I picked this one first because it lands on a problem I remember working around. There is tons of value in an update like this for anyone managing the help desk or responsible for anything after the sale is done. What I remember is this: “lifecycle stage never captured the whole story. We had to constantly use additional properties to capture all of these values.” Most of the time that meant a workflow automation, or some kind of monitoring layer on top of HubSpot to power all of it in any meaningful way.

My questions are the ones the panel does not answer. It says customers enroll in states automatically based on trigger logic, such as onboarding or a usage drop. I asked whether that trigger logic is a workflow, configuration inside the beta, or list enrollment and exit criteria, and where the usage signal comes from in the first place. I think you can hook the signal up with custom events or marketing events, but it still comes back to the foundation: “what does it mean when they're in onboarding? And what does it mean when we're declining usage? So all of those things need to be defined first and then we can come into the configuration and get this hooked up in an actual, intentional and strategic way.” We stayed on the panel and did not open the Customer success workspace on air, so how a state is stored and how far you can customize its triggers are still open from the show.

The Breeze angle is where I would look next, and it is a question, not a feature. I asked whether you could assign a custom agent in this context, so I could have dedicated agents for each customer state, trained on my context and processes, doing the customer agent-like behavior. Or maybe you just attach Customer Agent to it, aware of the customer state, to manage the back and forth. The panel does not mention assigning an agent to a state. Chris's reaction was that this is probably another update trying to help AI do some of this stuff for you.

Chris came at it from the other side. His upfront argument was that this is likely here because there is nothing in lifecycle stages after the customer. For a small team his advice was to pick one segment: you can turn states on for all customers or for specific customer segments, and one customer success person has to think through a lot that they naturally feel day to day. My advice is what I said on air: define the states first, then configure. If you run anything after the sale on Service Hub Professional or Enterprise, join the beta and do that definition work this week. If you are not on one of those two, skip it: the panel says the Customer Success Workspace is available only on Service Hub Professional and Enterprise.