HubSpot tickets not assigned, or going to the wrong person? How to fix routing

New HubSpot tickets stay unassigned for two broad reasons. Either the channel has no routing rule, in which case help desk tickets go to the Unassigned view by default, or a rule exists but nobody in it can take the ticket. People drop out of the pool when they're marked Away, reach their capacity limit or don't have a Service seat. HubSpot then leaves the ticket unassigned. Tickets that reach the wrong person usually trace back to the same settings.

HubSpot records why each ticket went where it did, so start there. Open the ticket in the help desk, expand Ticket activity in the right sidebar, find the assignment entry and click Assignment details. It splits the decision into the routing rule, user availability, the capacity check and the final assignment, and the failing step is usually obvious.

Why help desk tickets aren't assigned, or go to the wrong person

The channel has no routing rule

Each channel connected to the help desk has its own assignment setting. For team email, forms and WhatsApp it's in the channel's settings under Inbox & Help Desk, then Help Desk and Channels. For chat it's the Assignment switch on the chatflow's Chat tab. Setting up automatic routing needs an assigned Service seat on Service Hub Professional or Enterprise, as of October 2026 (route tickets in help desk).

Routing rules belong to channels. If tickets are also created by a workflow, an import or an integration, give that process its own owner step, for example the Rotate record to owner workflow action. If emails aren't creating tickets in the first place, see emails not creating tickets.

The person isn't eligible

Automatic assignment only goes to users who have an assigned Service seat and access to tickets. Users without a seat can't be added to routing rules. In the Rotate record to owner action, users who were deactivated or lost their paid seat show with a red border and are skipped, and invited users who haven't accepted are greyed out. When you route to a team, only its main members are eligible unless your account has joined HubSpot's beta for multiple main teams. See seat required errors for seats in general.

Everyone in the pool was unavailable

Assign to available users only is ticked by default in channel routing. HubSpot works out availability from working hours, out-of-office dates or a status the user sets by hand, and switches people to Away outside their working hours. A rep whose time zone is set wrong can show as Away while they're at work. If nobody in the pool is available, the ticket stays unassigned, and with team routing it lands in My Team's Unassigned. Each user's working hours and time zone are on the Preferences tab of their user record (user availability for help desk).

Everyone in the pool was at capacity

Ticket capacity limits take a user out of automatic assignment once they reach their limit, and that includes assignment by workflow. If every target user is full, the ticket waits unassigned until someone assigns it by hand. Limits count open help desk tickets by Ticket owner. On the Exclusions tab you can leave out tickets by age or by statuses such as Waiting on contact, so old tickets don't block new ones (ticket capacity limits).

Contact owner routing had nothing to work with

Routing to the contact owner needs a contact that has an owner and is tracked with a cookie. If the owner is unavailable, at capacity or not eligible, HubSpot uses the fallback set under If there is no contact owner, assign to. When that fallback is No owner, the ticket stays unassigned.

A skill-based rule matched, but nobody had the skill

On Service Hub Enterprise, skill-based rules run in priority order. If a ticket matches a rule but no user meets that rule's team and skill criteria, it stays unassigned. The channel's default rule only applies when no rule matches at all (skill-based routing).

A workflow set the wrong owner, or none

The Rotate record to owner action only replaces an existing ticket owner when Overwrite any existing ticket owner is selected. It has its own Assign to available users only option too, and if the whole pool is away it leaves the owner empty. Another workflow can also change the owner after routing set it. Look at the Ticket owner property history on the ticket to see what changed it, as explained in finding what changed a property.

The customer agent handed off and nobody picked it up

After a customer agent handoff, the Customer Agent ticket status property reads Awaiting Human Assignment until a person is assigned, and the help desk has a view for those tickets. Only users with a Sales or Service seat can be in the handoff routing. If the handoff uses Team only, availability is ignored and the handoff happens even when nobody is working. The customer agent setup guide covers planning handoffs.

How to fix ticket assignment

1. Open three recent tickets that went wrong and read Assignment details on each.
2. Check the channel's routing rule and its distribution method. Load Balanced, Round Robin and Random behave differently.
3. Confirm everyone in the rule has a Service seat and ticket access, and is a main member of any team you route to.
4. Check working hours, time zones and out-of-office dates for the people who should have received tickets.
5. Review capacity limits and their exclusions.
6. If a workflow assigns tickets, check its overwrite and availability options, then the Ticket owner history for other workflows changing it.
7. Assign the stuck tickets by hand from the Unassigned view. Manual assignment still works for users at their capacity limit.

How to stop it happening again

Give every routing rule a fallback that a person actually watches, and keep working hours current when shifts change. If your team uses Google or Outlook calendar sync, turn on the option to sync out-of-office events so leave shows up in HubSpot. When someone leaves, take them out of routing rules and workflows on the day their seat is removed. Check the Unassigned and My Team's Unassigned views every day, because that's where tickets wait when no rule can place them.

If tickets keep landing with the wrong person and you'd like the routing rebuilt, I can set up your help desk for you.

Questions

What's the difference between Load Balanced and Round Robin?

Load Balanced gives the ticket to the available user with the fewest open tickets of the same type, counting only help desk tickets assigned in the last 30 days. Round Robin works through users in a rotating order.

Can a ticket be assigned to a team with no owner?

Yes. Team only routing sets the team and leaves Ticket owner empty. Those tickets appear in My Team's Unassigned and My Team's Open, and the team needs at least one user with a Service seat.