What ticket routing means here
Routing is the step after a ticket lands: deciding who should own it, how fast it needs a response, and whether anyone besides the assigned rep needs to know about it right away.
HubSpot provides native help-desk routing and ticket-based workflow actions on qualifying Service Hub plans. The exact options and seat requirements vary. Current help-desk routing and workflow assignment are documented for Service Hub Professional and Enterprise (HubSpot: route tickets in help desk, HubSpot: assign ticket owners using workflows).
The routing mechanism still needs a signal. That signal can come from a property your team sets, HubSpot’s Enterprise ticket-category feature, a custom Breeze workflow action, or an installed app.
The signal has to exist as a property first
A workflow can only enroll and branch on something HubSpot can see, which means sentiment, category, and priority need to exist as ticket properties before any routing logic can use them.
This is why routing depends on categorization and sentiment. SentimentSync reads the ticket subject and description and writes its own four custom properties. It does not overwrite HubSpot’s built-in priority or category fields.
Once populated, the properties are available to HubSpot features that support ticket properties. Workflow branches require a qualifying Professional or Enterprise subscription (HubSpot: use branches in workflows).
Building the workflow
In Automation, create a ticket-based workflow and choose enrollment criteria based on the sentiment, category, or priority property you want to use.
From there, branching (if/then logic) can split tickets by category into different owners or teams, and a second branch can check sentiment to escalate a negative ticket regardless of which category it fell into.
Available actions depend on your HubSpot products and seats. A common pattern is to branch on the score, then notify a reviewer or use an eligible assignment action. Confirm the available action in your portal before designing the process around it.
A realistic example
A billing ticket that scores negative on sentiment is a different problem than a billing ticket that scores neutral. Both get the “billing” category, but only one needs a manager to look at it before the standard queue gets to it.
A workflow that branches on category first, then checks sentiment inside the billing branch, can route the negative one to a senior rep or a manager while the neutral one goes to the standard billing queue. Neither ticket needed a human to make that first split-second decision.
What routing on AI-generated properties will not fix
Routing logic is only as good as the property values feeding it, so a ticket with almost no description will produce a low-confidence category and sentiment score, and routing on top of a weak signal just moves the ambiguity downstream faster.
Workflows do not undo bad enrollment criteria. If a workflow’s trigger is too broad, it will enroll tickets you did not intend to route that way, so it is worth testing a new routing workflow on a small pipeline or with a delay step before turning it loose on your main queue.
This does not replace escalation paths you already trust for genuinely urgent issues, such as outage reports. Keep those fast paths and use AI-generated properties as an additional signal.
Rolling it out
Start with one routing rule, test it on a controlled set of real tickets, and compare the scores with human judgment. Add category-based or priority-based branches only after you know what the first rule gets wrong.
If you are still choosing the input signals, start with AI ticket categorization and HubSpot sentiment analysis.