The HubSpot Help Desk

The HubSpot help desk workspace is one screen for people who work a queue all day: views on the left, tickets in the middle, the customer record on the right.

Start free trial All guides

What the HubSpot help desk workspace actually is

The help desk is HubSpot's answer to a complaint support teams made for years: the conversations inbox is a lovely shared mailbox and a poor queue.

It puts the ticket at the centre instead of the thread. You get a list of tickets filtered by whatever properties you care about, the conversation threaded inside the ticket rather than sitting next to it, and the associated contact, company and deal in the same view.

It comes with the paid Service Hub seats rather than the free tools, so confirm which tier you're quoted before you design a process around it.

Left rail. Your saved views, which is where the queue design lives.

Middle column. The ticket list, sortable, with bulk selection.

Right pane. The record: properties, associations, activity, and the commercial context that makes HubSpot HubSpot.

Views are the whole game

A view is a saved filter on ticket properties, kept private or shared with a team. That sounds mundane. In practice your views are your operating model, because agents work the list in front of them and nothing else.

Five views cover most teams:

My open tickets, sorted oldest first.

Unassigned, which should be close to empty and is the first alarm when it isn't.

Waiting on customer, so nothing sits there for a month pretending to be work.

Reopened, because a reopened ticket is a failure you want to see today rather than in a monthly report.

Breaching or near target, on the tiers where SLA data exists.

The failure mode is view sprawl. Once every agent maintains a private set of filters, two people looking at the same queue see different work, and your standup turns into an argument about whose list is right. Keep the shared set small, name them clearly, and let private views be someone's personal scratch space.

One rule that saves a lot of pain: if a view needs information you don't have, add a ticket property. Do not add a pipeline stage. Stages describe where a ticket is in a workflow, not what it's about.

How tickets get assigned

Assignment happens in three different places, which is the single most confusing thing about the workspace for new admins.

Channel routing. When you connect an email address or chat channel, you can send everything from it to a person or a team, and on paid seats rotate it between them.

Workflows. A ticket-based workflow can set the owner from any property, which is how topic and product routing gets built.

Hands. Someone opens the unassigned view and picks the ticket up.

Most teams need all three. Channel routing gets a name on the ticket immediately, workflows correct that name based on what the ticket is about, and humans handle the fifteen percent that neither rule anticipated.

Help desk versus the conversations inbox

They're not two names for one thing, and the difference is the unit of work.

The conversations inbox is thread-first. A message arrives, someone replies, the thread is either open or closed. It is available on the free tools, it's fine for two people handling thirty emails a day, and it starts to hurt the moment you need to know what the queue looks like rather than what your inbox looks like.

The help desk is ticket-first. Every conversation on a connected channel becomes a ticket with an owner, a status, a pipeline stage and properties you can filter and report on. The thread is still there. It just is not the organising idea any more.

If you can answer "how much work is outstanding right now" from your inbox, you don't need the help desk yet. When you cannot, no amount of folder discipline will fix it.

Where it stops

Honest limits, because you'll meet all of these in month two.

No cross-ticket awareness. Two tickets from the same customer about the same problem sit next to each other in the list and nothing points it out. The workspace evaluates one record at a time, like every other part of HubSpot.

Merging is two at a time. From the actions menu, permanent, no undo. A morning of duplicates is a morning of clicking.

Routing ignores workload. Rotation shares tickets out evenly by count, not by how much work each person is already carrying.

Bulk actions are narrower than a specialist desk. You can bulk edit properties, but the more interesting bulk operations aren't there.

FAQ

Frequently asked questions

HubSpot help desk vs inbox: which should agents work in?

The HubSpot Service Hub help desk workspace, if they work a queue all day. The conversations inbox suits shared-mailbox teams. The HubSpot help desk vs inbox choice is about volume, and both read the same underlying tickets.

Is the HubSpot help desk the same as the conversations inbox?

No. The inbox organises threads and is available on the free tools. The help desk organises tickets, with views, properties and pipelines, and sits on the paid Service Hub seats.

Can agents have their own private views?

Yes. Views can be private to one user or shared with a team, which is useful and also the main cause of queue drift if nobody governs the shared set.

Does the help desk show SLA timers?

On the tiers that include SLA tracking, targets appear against tickets in the list. Below that you are reading create dates and doing the maths yourself.

Do we still need ticket pipelines if we use the help desk?

Yes. The workspace displays tickets, pipelines define the stages they move through. See HubSpot ticket pipelines.

The view nobody can build

No filter finds the ticket that's a copy of another ticket. Ticket Merger does exactly that on Zendesk and Freshdesk today, and HubSpot support is on the roadmap.

Start free trial

14-day free trial. No credit card required.

Published August 18, 2026