What is the HubSpot help desk?
The HubSpot help desk is a Service Hub workspace where your team manages tickets from every connected channel in one place. Email, chat, forms, calling, WhatsApp, Facebook Messenger and custom channels create tickets automatically, and agents reply, route and close them there. When we checked in October 2026, it needed Service Hub Professional or Enterprise.
This guide follows HubSpot's documentation as of October 2026. It covers the ticketing system end to end: plans and seats, the HubSpot ticket pipeline, channels, routing, the help desk workspace, ticket properties and automation. Service level agreements get one short section here, because our HubSpot ticket SLA guide covers them in depth.
Which HubSpot plans and seats include the help desk?
When we checked HubSpot's documentation in October 2026, the help desk workspace needed Service Hub Professional or Enterprise. Service or Sales Access permissions let a user view, edit and respond to tickets. An assigned Service Seat is needed for advanced features such as custom views, SLAs, reply recommendations, routing rules and capacity limits.
| Feature | Requirement (Oct 2026) |
|---|---|
| Help desk workspace | Service Hub Professional or Enterprise |
| Viewing and replying to tickets | Service or Sales Access permissions |
| Custom views, SLAs, reply recommendations | Assigned Service Seat |
| Automatic routing rules | Service Seat, for the admin and for every routed user |
| Skill-based routing | Service Hub Enterprise, Super Admin to set up |
| Ticket capacity limits | Service Seat; Super Admin or Add and edit users to set |
| Connecting channels | Account Access permissions |
| Summary and Analyze pages | Assigned Service Hub Seat |
| Support portal | Service Hub Professional or Enterprise |
Seat planning matters more than it looks. Users with Service or Sales Access but no Service Seat only see three default views: My Mentions, Following and All Open. Super Admins can open every view without a seat. If you plan to route tickets to someone, they need a Service Seat, or HubSpot will not let you add them to a routing rule.
Two other limits to know before rollout: help desk is not yet available on the HubSpot mobile app, and the setup flow creates test connections for each channel you pick, except Calling, WhatsApp and Facebook Messenger, so you can preview tickets with sample data before going live.
How should you set up a HubSpot ticket pipeline?
Start from HubSpot's default Support Pipeline, which has four ticket statuses: New, Waiting on contact, Waiting on us and Closed. Statuses are the ticket version of pipeline stages, and each one is marked Open or Closed. Rename or add statuses so they match how your team really works, then set help desk ticket defaults.
- Custom pipelines: when we checked in October 2026, creating a custom pipeline needed a Starter, Professional or Enterprise subscription. Free tools get no custom pipelines beyond the default. Limits are shared across all objects and vary by pricing model, so check Data Model > Limits in your account.
- Open or Closed: help desk views depend on this flag. Unassigned, My Team's Open and All Open only show tickets in an Open status, and All Closed shows tickets in a Closed one.
- Conditional stage properties: set properties that appear, or are required, when an agent creates a ticket in a status or moves it there. For example, you could require Resolution when a ticket moves to Closed.
- Team access: restricting a pipeline by team needs a Professional or Enterprise subscription, as does cloning a pipeline with its rules and automations.
- Ticket defaults: in help desk settings under Ticket defaults, choose the pipeline, status and priority that new incoming tickets get. Channel settings can override them.
Keep the number of pipelines low. One pipeline per genuinely different process, such as support versus onboarding, is easier to report on than one per team. The same thinking applies to deal pipelines, which our HubSpot deal stages guide covers.
How do channels turn messages into tickets?
You connect each channel in Settings under Inbox & Help Desk > Channels, then choose whether incoming conversations go to an inbox or to help desk. Help desk channels create tickets automatically for every incoming message or submission. Inbox channels keep conversations without tickets by default, and newer accounts cannot create tickets from them at all.
| Channel | What it does in help desk |
|---|---|
| Team email | Creates tickets from emails sent to a shared address |
| Chat | Website visitors start conversations through a chatflow |
| Forms | Creates tickets from form submissions |
| Calling | Calls and call conversations sit alongside other tickets |
| Messages through a verified WhatsApp Business number | |
| Facebook Messenger | Messages sent to your Facebook Business Page |
| Custom channels | Marketplace integrations or the custom channels API |
- The April 2024 cutoff: HubSpot says accounts created after April 1, 2024 cannot create tickets from channels connected to the inbox, so new support setups belong in help desk.
- One-to-one emails sent from a help desk email address create a new ticket assigned to the sender, unless you send from inside an existing ticket.
- Rule-based chatbots connected to help desk do not create tickets automatically, to prevent duplicates.
- Connect every support channel. If a workflow creates a ticket from a channel that is not connected to help desk, the subject and thread will not show in help desk.
- Send-from permissions (Service Professional or Enterprise) restrict which users and teams can send from team email, SMS, WhatsApp and custom channels.
Forms are often the cleanest way into help desk because you control the fields. Our HubSpot forms guide covers form design, and the HubSpot knowledge base guide covers deflecting simple questions before they become tickets.
How does HubSpot route help desk tickets?
Incoming help desk tickets are unassigned by default. On each channel's Routing tab you can assign tickets to specific users and teams, a team only, the contact owner, an assignment workflow or the AI customer agent. Distribution can be Load Balanced, Round Robin or Random, and by default only available agents receive tickets.
- 01 Message inEmail, chat, form
- 02 Ticket createdDefault pipeline
- 03 Routing rulePer channel
- 04 ChecksAvailability, capacity
- 05 Agent repliesHelp desk
- 06 Status setClosed or waiting
- Load balancing is per ticket type. HubSpot assigns to available users with the fewest open tickets of the same type: Calling, Messaging (live chat and custom channels) or Email/Other (email, forms, workflows, API and manual tickets). Only open help desk tickets assigned in the last 30 days count.
- Team only routes to a team without a ticket owner, so tickets land in My Team's Unassigned and My Team's Open. The team needs at least one user with a Service Seat.
- Main teams: with specific teams in a rule, tickets only route to main team members unless your account is in HubSpot's multiple main teams beta.
- Contact owner needs an owner on the contact and cookie tracking, plus a fallback rule for when the owner is unavailable or at capacity.
- Capacity limits cap open tickets per user, in total or per channel type. The calling limit can only be 0 or 1. Users at capacity are skipped, and you can exclude statuses such as Waiting on contact from the count.
- Skill-based routing (Service Hub Enterprise) matches tickets to agents by language or custom skills.
- Assignment details on each ticket show which routing rule, availability and capacity check applied, which helps when someone asks why a ticket went to them.
Round robin and load balancing behave differently from the sales rotation many teams know. Our HubSpot round robin guide explains the trade-offs.
Tickets landing with the wrong person? Bring your channels and routing rules to a free 30-minute call and we will review seats, teams, capacity and fallback rules.
How do you organize the help desk workspace?
Group agents into HubSpot teams based on expertise and how they share tickets, then use views to control what each team sees. Help desk includes default views such as Unassigned, Assigned to me, My Team's Open and All Open. Seated users can add public, team-shared or private custom views, and everyone can choose table, split or board layouts.
- Default views also include My Team's Unassigned, Following, My Mentions, All Closed, Sent and Spam, plus customer agent views if you use the AI customer agent.
- Custom views filter tickets, for example all high priority tickets. Public views are visible to all teams, team-shared views to the creator's main team, and private views only to the creator.
- View order: drag views to reorder them, or drag them below More to hide them.
- Access still applies. Users only see tickets they have access to, so check ticket permissions before blaming a view.
- Right sidebar: agents see associated contacts, companies and deals, and the History tab shows status changes, workflow enrollments and merges. You can customize which sidebar sections appear.
- Working the ticket: agents can insert templates, snippets, knowledge base articles and macros, add internal notes with @mentions, and send a reply and set a ticket status in one action.
- Slack: you can sync help desk tickets to a Slack channel based on ticket property filters. Our HubSpot Slack integration guide covers the connection.
For managers, the help desk Summary page shows today's open and closed tickets, time to first reply, time to close, team availability and SLA progress. The Analyze page holds the pre-built reports. Both need an assigned Service Hub Seat.
Which ticket properties matter most in the help desk?
The core ticket properties are Ticket name, Pipeline, Ticket status, Priority, Owner and Ticket description, and HubSpot requires name, pipeline and status by default when you create a ticket manually. Source, Originating channel type, Close date and Time to close fill in automatically and give you the reporting backbone for your help desk.
- Assigned teams records the main team set by automatic assignment. It needs Service Hub Starter, Professional or Enterprise.
- Category and Language are set by AI from the ticket's messages and need Service Hub Enterprise. Category identification is off by default and is turned on under Help Desk > AI tools.
- Resolution records the action taken. Pair it with a conditional required property on your Closed status.
- Stage calculated properties such as Date entered and Cumulative time in each status need a Professional or Enterprise subscription. They show where tickets wait.
- SLA properties such as Time to first response SLA due date only appear once SLAs are set.
- CES survey properties need Service Hub Professional or Enterprise. Our customer feedback surveys guide covers the surveys behind them.
Add custom ticket properties only when someone will report on them or route by them. Every extra field on the create form slows agents down, and an unused dropdown quietly fills with blanks.
What can you automate in a HubSpot help desk?
Start with what help desk does natively: ticket defaults, channel routing rules, capacity limits and SLA goals. Then add workflows for the gaps, such as assignment logic that routing rules cannot express, notifications and property updates. When we checked in October 2026, HubSpot workflows needed a Professional or Enterprise subscription, which Service Hub Professional includes.
- Assignment workflows: a channel can route through Use assignment workflow, which runs a ticket-based workflow with an assignment action. Capacity limits also apply to tickets assigned by workflows.
- Pipeline automation: each ticket pipeline has an Automate tab for pipeline automations, plus a Pipeline Rules tab.
- SLA goals: Super Admins set them under Help desk automation > SLAs, for all tickets or by ticket properties such as Priority or Source. They apply to help desk tickets only. Our ticket SLA guide covers the setup.
- Support portal: on Service Hub Professional or Enterprise, customers can log in to see and manage their tickets. Only tickets appear, not conversations without a ticket.
Write each workflow down before you build it: trigger, enrollment criteria, actions and who owns it. Our HubSpot workflows guide and free workflow design template help keep ticket automation documented, not black-boxed.
HubSpot help desk setup checklist
Key takeaway: Assign Service Seats first, keep one ticket pipeline per real process, connect every support channel to help desk, and set routing and capacity per channel before you add workflows. Then test what each role sees. More setup guides are in our HubSpot resources, and our HubSpot implementation service covers a full Service Hub rollout.
Frequently asked questions
Which HubSpot plan includes the help desk?
When we checked HubSpot's documentation in October 2026, the help desk workspace needed Service Hub Professional or Enterprise. Users need Service or Sales Access permissions to work tickets, and an assigned Service Seat unlocks advanced features such as custom views, SLAs and reply recommendations. Skill-based routing needs Service Hub Enterprise.
What is the difference between the HubSpot inbox and the help desk?
Both use channels such as team email, chat and forms. Messages sent to a help desk channel create tickets automatically. Messages sent to an inbox channel stay as conversations by default. HubSpot says accounts created after April 1, 2024 cannot create tickets from channels connected to the inbox.
What are the default ticket statuses in HubSpot?
HubSpot's default Support Pipeline has four ticket statuses: New, Waiting on contact, Waiting on us and Closed. Statuses are the ticket version of pipeline stages. Each one is set as Open or Closed, and you can add conditional properties that agents must fill in when a ticket moves to that status.
How does HubSpot assign help desk tickets automatically?
Each help desk channel has a Routing tab. You can route to specific users and teams, a team only, a contact owner, an assignment workflow or the customer agent, and distribute by Load Balanced, Round Robin or Random. By default, only available agents receive tickets, and routing rules need a Service Seat.
Can I use the HubSpot help desk on the mobile app?
Not when we checked in October 2026. HubSpot's setup article says help desk is not yet available on the HubSpot mobile app. Agents work tickets in the browser, and HubSpot also documents syncing help desk tickets to Slack, Microsoft Teams and Google Chat.
Sources
HubSpot documentation behind the feature and tier notes above, checked October 2026. HubSpot changes features and tiers often, so check your own portal too.
- Set up help desk (HubSpot)
- Choose a channel to connect to help desk (HubSpot)
- Connect and manage inbox and help desk channels (HubSpot)
- Route tickets in help desk (HubSpot)
- Route tickets in help desk based on agent skills (HubSpot)
- Set ticket capacity limits for users in help desk (HubSpot)
- Organize teams and views in help desk (HubSpot)
- Create and respond to tickets in help desk (HubSpot)
- Manage tickets in help desk (HubSpot)
- Set SLA goals in help desk (HubSpot)
- Analyze help desk activities (HubSpot)
- Sync and manage help desk tickets in Slack (HubSpot)
- Set up and manage object pipelines (HubSpot)
- HubSpot's default ticket properties (HubSpot)
- Set up a support portal (HubSpot)
- Create workflows (HubSpot)

