Latest / Sidekick's What Just Shipped / HubSpot routing to assignment workflows: close the unassigned gap | Shipped May 2026
Transcript
- Rob (AI host): You leave new tickets unassigned on purpose, so a workflow can route them. Rob (AI host): Then a rep grabs one first, and your routing logic never runs. Dana (AI host): HubSpot's fix sends new tickets and conversations straight into an assignment workflow. Dana (AI host): Here's how it works in Help Desk and Inbox. Rob (AI host): This is Sidekick's What Just Shipped. Let's route it. Narrator (AI voice): This is Sidekick's What Just Shipped, presented by Sidekick Strategies. Narrator (AI voice): Your hosts, Rob and Dana, are AI. Narrator (AI voice): The voices are synthetic, the research is real, and humans check every claim before it reaches you. Dana (AI host): Hi, I'm Dana. Dana (AI host): Rob and I are AI hosts, and neither of us has ever been assigned a ticket. Dana (AI host): Lucky us. Rob (AI host): I'm Rob. Today I'm playing a service ops admin with that exact unassigned workaround. Rob (AI host): So show me why I should change it. Dana (AI host): Okay. It shipped in stages. Our first write-up, from May 14, 2026, covered Help Desk. Dana (AI host): A new routing option called Use assignment workflow. Rob (AI host): Which does what? Dana (AI host): New tickets from that channel get enrolled into a workflow you choose, and that workflow makes the assignment decision. Rob (AI host): And why couldn't I just keep my workaround? Dana (AI host): First, some context. Dana (AI host): HubSpot's help desk page says incoming tickets are left unassigned by default, unless you set up routing. Rob (AI host): Right, which is why the workaround exists. Dana (AI host): Our research describes the problem plainly. Dana (AI host): Agents can claim a ticket before the workflow fires, so the routing logic you built never runs. Rob (AI host): That's my Tuesday. Dana (AI host): HubSpot's help desk routing page, updated October 27, 2026, now lists it. Dana (AI host): Use assignment workflow, then pick a ticket-based workflow with an assignment action from the Workflow dropdown. Rob (AI host): Where do I set it? Dana (AI host): For a team email channel, go to Settings, then Inbox and Help Desk, then Channels. Dana (AI host): Open the channel and use the Routing tab. Form channels work the same way. Rob (AI host): And chat? Dana (AI host): Chat assignment lives in the chatflow's Chat tab. Dana (AI host): HubSpot's live chat page shows Use assignment workflow there too. Rob (AI host): What if nobody's around to take a chat? Dana (AI host): That same page has a checkbox to assign the customer agent if no users are available. Rob (AI host): Then Inbox. What if we're not on Help Desk? Dana (AI host): Our July and September write-ups cover that. Dana (AI host): Inbox routing rules got the same option, so conversations enroll in a workflow at creation, without migrating to Help Desk. Rob (AI host): Same kind of workflow? Dana (AI host): No, and this trips people up. Help Desk needs a ticket-based workflow. Dana (AI host): Inbox needs a conversation-based workflow. HubSpot's live chat page says both, depending on where you're routing. Rob (AI host): And what counts as an assignment action? Dana (AI host): For Inbox, our research says Assign to Customer Agent or Rotate Conversation Owner. Dana (AI host): For Help Desk, Assign to Customer Agent or Rotate record to owner. Dana (AI host): Workflows without one won't show up in the dropdown. Rob (AI host): Who gets this? Dana (AI host): Service Hub Professional and Enterprise. Our write-ups and HubSpot's help desk page agree on that. George B. Thomas (AI voice clone): Hey, it's George B. Thomas from Sidekick Strategies. George B. Thomas (AI voice clone): Full honesty, this is my AI voice clone, made with my permission. George B. Thomas (AI voice clone): Routing decides who owns a ticket. SLAs tell you whether anyone answered it in time. George B. Thomas (AI voice clone): In our Service Hub training, we configure your SLAs during the sessions, so your team sees real-time performance metrics right away. George B. Thomas (AI voice clone): Sessions are recorded for onboarding new support hires. George B. Thomas (AI voice clone): Look for Service Hub training under services at Sidekick Strategies dot com. Rob (AI host): Okay, Dana. What can the workflow actually do that my old rules couldn't? Dana (AI host): Our research lists VIP versus standard routing, language or region routing, and conditional handoffs between the customer agent and humans. Rob (AI host): Anything before the assignment step? Dana (AI host): That's the clever part. Dana (AI host): Our May write-up suggests using the earlier steps to stamp ticket properties or set priority, then assign. Rob (AI host): Now the fine print on Rotate record to owner. Dana (AI host): HubSpot's workflow page says users need an active, paid Sales or Service Hub Professional or Enterprise seat. Dana (AI host): And only main team members are eligible, unless you're in a beta for multiple main teams. Rob (AI host): And if nobody's eligible? Dana (AI host): Then no owner is assigned. Dana (AI host): So your workflow needs a fallback branch, or you're back to unassigned. Rob (AI host): How does it split work across a team? Dana (AI host): By default, records are assigned equally within the selected team or between the users you specify. Rob (AI host): Huh. Any other gotcha? Dana (AI host): If the HubSpot owner property syncs to Salesforce, HubSpot says the action may not work as expected. Rob (AI host): And when a ticket lands somewhere weird, how do I find out why? Dana (AI host): Open the ticket, expand Ticket activity, and click Assignment details. Dana (AI host): It shows the routing rule, user availability, capacity check, and assignment. Rob (AI host): So does this mean Inbox teams never need Help Desk? Dana (AI host): Our September write-up says no. Dana (AI host): Help Desk still has SLA management, ticket pipelines, and reporting that Inbox doesn't match. Dana (AI host): This just removes routing as the reason to move. Rob (AI host): Okay. What couldn't you confirm? Dana (AI host): Three things. First, live chat. Dana (AI host): Our Inbox write-ups say a chat widget using this option shows as available at all times, because HubSpot can't predict who the workflow will pick. Dana (AI host): HubSpot's live chat page doesn't mention that. Rob (AI host): That one matters at night. Second? Dana (AI host): Status. Dana (AI host): Our write-ups called it a public beta, expected July 20 for Help Desk and August 26 for Inbox. Dana (AI host): HubSpot's pages now list the option without a beta label, but don't say when it went fully live. Rob (AI host): Third? Dana (AI host): Skills. Our May write-up lists Rotate owner by skill as coming soon. Dana (AI host): HubSpot's help desk page covers skill-based routing rules, but we couldn't confirm a skill action inside workflows. Rob (AI host): Fine. Here's my Monday as the admin with the workaround. Rob (AI host): Build the workflow first, with a branch for when no one is eligible. Rob (AI host): Then point one low-volume channel at it. Rob (AI host): Check Assignment details on the first ten tickets before moving anything else. Dana (AI host): And if you run live chat after hours, test the widget at night. Dana (AI host): That's routing to assignment workflows in Help Desk and Inbox, and the fine print on Rotate record to owner. Rob (AI host): Every source is on the HubSpot Updates page at Sidekick Strategies dot com. Dana (AI host): Thanks for routing a few minutes our way on Sidekick's What Just Shipped. Rob (AI host): Unassigned is not a strategy. Narrator (AI voice): Sidekick's What Just Shipped is presented by Sidekick Strategies, with AI hosts Rob and Dana and AI-generated music. Narrator (AI voice): We're independent, and not affiliated with HubSpot. Find our research at Sidekick Strategies dot com.