What This Update Actually Is
HubSpot added a new action to Inbox routing rules called "Use assignment workflow." Instead of routing a new conversation to a specific agent or team, this option enrolls the conversation directly into a workflow you choose.
The workflow takes over from there. It controls assignment, sequencing, handoffs, and any other downstream logic you've built. The routing rule is just the trigger point.
One important caveat: live chat channels using this option will show the widget as available at all times. Because the workflow decides which agent ultimately handles the chat, HubSpot can't know in advance whether a specific agent is online. That's a trade-off worth knowing before you go live.
Why HubSpot Shipped This
Standard inbox routing has always covered the basics: assign to an agent, a team, or the contact owner. That's fine for small teams. It breaks down fast when you need anything more sophisticated.
Language-based routing, skills-based assignment, Customer Agent handoffs, and time-of-day logic all require conditional logic that a static routing rule can't deliver. Teams running those scenarios had two options before today.
- Migrate to Help Desk, which adds complexity and a learning curve your team may not be ready for.
- Leave conversations unassigned and let a workflow catch them, which creates a race condition where agents can claim tickets before the workflow even fires.
That second option is a real problem. We've seen it in portals where well-intentioned routing setups actually made assignment less consistent, not more. Agents grab whatever's visible, the workflow fires a few seconds later, and suddenly a conversation has two owners or none.
This update closes that gap. The conversation goes straight into the workflow at creation. No race condition, no unassigned window.
How to Use It Step by Step
Here's how to set this up in your portal once the beta is available to you.
- Build your assignment workflow first. It must be a conversation-based workflow. It must include either an "Assign to Customer Agent" action or a "Rotate Conversation Owner" action. Publish it before touching the routing rule.
- Navigate to your Inbox settings. Go to Settings, then Inbox, then select the inbox you want to update.
- Open the routing rule for the relevant channel. Click into the routing configuration for the channel you're updating.
- Select "Use assignment workflow" from the action options. A searchable dropdown will appear. Only published workflows with a valid assignment action will appear here.
- Pick your workflow from the dropdown and save the rule. All new conversations in that channel will now enroll directly into the workflow on creation.
- If you're using a live chat channel, confirm the chat widget availability behavior matches your expectations. The widget will show as available at all times, regardless of individual agent status.
What It Touches in Your HubSpot Strategy
This update does more than add a dropdown. It shifts where routing logic lives in your Service Hub architecture.
Before this update, your routing logic was split: some of it lived in inbox rules, and the more advanced stuff lived in workflows that fired after the fact. Now you can consolidate. The workflow becomes the single source of truth for assignment.
Key Takeaway
If you've been using conversation-based workflows to patch gaps in your inbox routing, you can now connect them directly to the routing rule. That eliminates the unassigned window that creates race conditions and inconsistent agent experience.
Here's what this ripples into across your portal.
- Conversation-based workflows: these become your routing engine, not just a fallback. Build the conditional logic here: language detection, time of day, contact tier, topic.
- Customer Agent integration: handoffs from AI agents to human reps can now be orchestrated through the workflow directly from the point of conversation creation.
- Reporting: because assignment now happens inside a workflow, you gain a clear audit trail. You can see exactly which branch of logic handled each conversation.
- Help Desk migration decisions: if the only reason you were considering Help Desk was advanced routing, this update may remove that pressure. Evaluate what else Help Desk offers before committing.
This update pairs naturally with user availability statuses in HubSpot workflows, which let you trigger routing logic based on whether an agent is out of office or within working hours. Together, these two updates give you a genuinely sophisticated routing stack inside Inbox.
Key Takeaway
The live chat caveat is real: the widget shows as available at all times when this routing option is active. If your team goes offline at night and you're using live chat, make sure the workflow itself handles the no-agent-available scenario, or visitors will see an available widget with no one to answer.
If you're thinking about how this fits into a broader agentic service model, the HubSpot agentic platform pillar gives you the strategic picture of where AI-assisted routing and Customer Agents are heading.
Who Should Care Most
Not every team needs this right away. But if you recognize yourself in any of these profiles, move it up your priority list.
- Multilingual support teams routing conversations to agents by language. Static rules can't do this. Workflows can.
- Teams using or piloting HubSpot Customer Agents. Workflow-controlled handoffs from AI to human now connect directly to the routing entry point.
- Service operations leaders who've been patching routing gaps with workarounds and want a cleaner architecture.
- Companies with tiered support models. Route enterprise contacts to senior reps and standard contacts to general queues using workflow branches, all from a single inbox rule.
- RevOps and CX managers who want a full audit trail of how conversations got assigned, not just who ended up with them.
This feature requires Service Hub Professional or Enterprise. If your team is on Starter, this won't appear in your routing options.
George's Take
I've sat with a lot of service teams who built genuinely clever routing logic in workflows, then watched it underperform because there was always that gap between conversation creation and workflow enrollment. Agents are fast. They'd grab tickets before the workflow could do its job, and then you'd have a mess to untangle. This update removes that gap at the source. The workflow fires at the moment the conversation is created, not a few seconds later. That's the kind of fix that sounds small until you've seen what the race condition costs you in misdirected conversations, frustrated humans, and manual reassignments.
“The workflow fires at creation, not after. That one change turns a workaround into an actual system.”
Also worth noting: this pairs really well with the Workforce Management tools HubSpot shipped for Help Desk. If you're managing capacity and availability across a service team, having routing and staffing visibility in the same platform is a meaningful step forward for the humans running those operations.
If your inbox routing has been a patchwork of workarounds, this is the right moment to rethink it from scratch. The Sidekick team helps Service Hub Pro and Enterprise accounts design routing architectures that scale. Book a strategy call and let's look at what your portal actually needs.
Frequently Asked Questions
What is the "Use assignment workflow" option in HubSpot Inbox?
It's a new routing action in HubSpot Inbox that enrolls newly created conversations directly into a published conversation-based workflow instead of assigning them to a static agent or team. The workflow then controls all assignment, handoff, and downstream logic. It's available in Service Hub Professional and Enterprise.
How is this different from regular HubSpot inbox routing?
Standard inbox routing assigns conversations to a specific agent, team, or contact owner. This new option hands control to a workflow, enabling conditional logic like language-based routing, time-of-day rules, skills-based assignment, and Customer Agent handoffs. Those scenarios aren't possible with static routing rules.
Does the workflow need to be published before I can use it in routing?
Yes. The workflow must be published and must include either an "Assign to Customer Agent" or "Rotate Conversation Owner" action before it appears in the routing dropdown. Drafts won't show up. Build and publish the workflow first, then update the routing rule.
Why does the live chat widget show as available at all times with this option?
When "Use assignment workflow" is active on a live chat channel, HubSpot can't predict which agent the workflow will assign the conversation to, so it can't check individual agent availability upfront. The widget stays available at all times. Your workflow needs to handle the no-agent-available scenario explicitly.
Do I need to migrate to Help Desk to use advanced routing logic in HubSpot?
Not anymore. This update brings workflow-driven routing into the standard Inbox experience. If advanced assignment logic was the main reason you were considering Help Desk, this may remove that need. Evaluate what else Help Desk offers before deciding, since it includes additional features beyond routing.
Who is this HubSpot inbox routing update available to?
It's available to Service Hub Professional and Enterprise accounts. As of late July 2026, everyone in those accounts is enrolled in the public beta, with a general release expected August 26, 2026.
