Guide
HubSpot Service Hub Setup:Seats, Help Desk, Ticket Pipeline, Channels, SLAs and Portal
HubSpot Service Hub setup in order: Service seats, the help desk flow, the ticket pipeline, team email, routing, SLA goals, knowledge base and support portal.
HubSpot Service Hub setup runs in a fixed order on Professional or Enterprise: assign Service seats, run the help desk setup flow under Service > Help Desk, shape the ticket pipeline, connect a team email channel, set routing and SLA goals, then build the knowledge base and support portal that customers see. Free tools and Starter have no help desk.
Each step depends on a setting made in an earlier one. A team email channel asks which ticket pipeline, status and priority new tickets receive, so the pipeline has to exist first; routing rules can include only users who already hold Service seats; and an SLA rule chosen when a ticket arrives is not re-evaluated when the ticket's properties change later. This guide sets out the requirements by tier and the shorter setup below Professional, then the steps in order with HubSpot's menu paths, a verification test and a sample SLA calculation. It closes with the requests that end in a site visit, which belong to HubSpot field service software rather than to the help desk. HubSpot facts come from HubSpot's knowledge base and pricing pages, checked on November 12, 2026.
A channel is a route by which customers reach the team, such as a support email address or a website chat. A ticket pipeline is the sequence of statuses a ticket moves through. An SLA goal is a target time for a reply or a resolution, measured on each ticket.
Service Hub Setup Requirements by Tier
The tier decides which steps exist at all. Every tool in the main procedure below is listed for Service Hub Professional and Enterprise in its knowledge base article.
| Setup item | Tier | Seat or permission |
|---|---|---|
| Help desk workspace | Professional, Enterprise | Service seat for custom views, SLAs and reply recommendations |
| Ticket pipelines | All plans; custom pipelines from Starter | Edit property settings permission |
| Team email and other channels | Professional, Enterprise for help desk channels | Account Access permission |
| Automatic ticket routing | Professional, Enterprise; skill-based routing on Enterprise | Service seat for each user routed to |
| SLA goals | Professional, Enterprise; property combinations on Enterprise | Super Admin |
| Knowledge base | Professional, Enterprise | Service Hub seat, with Super Admin or knowledge base settings permission |
| Support portal | Professional, Enterprise | Customer portal settings permission and a connected domain |
| Customer support surveys | Professional, Enterprise | Service Hub seat |
Professional is listed at $90 or $100 a seat a month across the annual and monthly options, and the Service Hub pricing page adds a required one-time Professional Onboarding fee of $1,500. Enterprise starts at $150 a seat a month with a $3,500 onboarding fee.
Service Hub on Free Tools and Starter
Below Professional there is no help desk to set up, so the procedure in the next section does not apply. Tickets live on the tickets index page, where the board view shows them by pipeline status, and Starter allows custom pipelines: 15 in total, shared across objects. Free tools allow none beyond the defaults.
Two documented rules shape how tickets are created at these tiers. Accounts created after April 1, 2024 cannot create tickets from channels connected to the conversations inbox, according to the overview of the conversations inbox (updated May 19, 2026). The workflow Create record action creates tickets on Service Hub Professional and Enterprise only (workflow actions, updated October 26, 2026). On a newer account at free tools or Starter, a ticket is therefore created by hand from the index page or a record. The Service Hub product page does list simple ticket automation on Starter, which a Starter account tests against its own process before relying on it.
Help Desk Setup, Step by Step
The steps follow the order in which later settings depend on earlier ones. Each cites the HubSpot article that documents it.
- Assign Service seats. A Service seat unlocks the help desk's advanced features, makes a user eligible for routed tickets and is required to create a knowledge base. View-Only seats are free and unlimited, and cannot edit records (manage seats, updated November 11, 2026).
- Run the setup flow. Navigate to Service > Help Desk and click Set up help desk. The flow asks about the support team, preferred channels, existing tools and default layout. Its final button opens a workspace with sample tickets and a test connection for each chosen channel, and no messages reach customers through the test channels (set up help desk, updated November 12, 2026).
- Shape the ticket pipeline. Under Settings > Data Management > Objects, select Tickets and open the Pipelines tab. The default Support Pipeline has four statuses, from New to Closed. Create pipeline > Create from scratch adds another pipeline for a separate process, such as warranty claims (object pipelines, updated October 22, 2026).
- Connect the team email channel. Under Settings > Inbox & Help Desk > Channels, click Team Email, then Connect email address, and send incoming conversations to help desk. Choose Gmail, Office 365 or Other, which forwards mail from another provider. Set the from name and team signature, then pick the ticket pipeline, stage and priority for new tickets and the assignment rule (connect a team email channel, updated November 3, 2026).
- Connect the remaining channels. Chat, forms, WhatsApp, Facebook Messenger, calling and custom channels connect from the same Channels page. HubSpot recommends connecting every support channel, because a ticket created by a workflow from an unconnected channel shows no subject or thread in the help desk (choose a channel, updated October 29, 2026).
- Set routing. Incoming tickets arrive unassigned unless a rule routes them to specific users and teams, to a team only, to the contact owner with a fallback, or to the customer agent. Automatic routing requires a Service seat, both to set up and for each user it routes to (route tickets in help desk, updated October 27, 2026).
- Set SLA goals. Under Settings > Inbox & Help Desk > Help Desk, in the Help desk automation section, click SLAs. Choose Apply to all tickets or a single ticket property, and set Time to first reply, Time to next reply and Time to close. Set when a ticket is marked Due soon, choose During specific time for business hours, add pause conditions, then save and toggle SLAs on (SLA goals, updated June 30, 2026).
- Create the knowledge base. Navigate to Service > Knowledge Base and click the button that sets up a new knowledge base. Enter the title, language, domain and slug, then choose one of five home page templates: Content Rich, Tiles, Minimal, Cards or Classic. Professional allows one knowledge base with up to 2,000 articles (create a knowledge base, updated March 11, 2026).
- Turn on the support portal. Navigate to Service > Customer Portal and click Get Started. Enter the portal name, choose a connected domain and slug, and add or skip a support form. Then choose the help desk as the destination for portal tickets, set which tickets each contact sees, and set access by access group or self-registration (set up a support portal, updated October 23, 2026).
- Add a customer support survey. Under Service > Feedback Surveys, click Create survey, select Customer support and email delivery. Sending it needs Marketing access with publish rights for email (customer support surveys, updated June 20, 2026).
- Verify. From an address that is not a HubSpot user, send a message to the support address. Confirm that a ticket appears in the help desk with the chosen pipeline, status and priority, the routed owner and an SLA due time. Reply, set the status to Closed, then log in to the portal as the test contact and confirm the ticket is listed there.
The same address cannot serve two tools. A team email connected to the conversations inbox cannot also be connected to the help desk, an individual work email cannot be a help desk channel, and IMAP connections are not supported.
First-Reply Due Times Under a Four-Hour SLA
The figures below are sample data, not a client, chosen so the due time can be recomputed. A plumbing company sets a first-reply goal of 4 hours, applied during specific time: Monday to Friday, 8:00 to 17:00 Central, with tickets marked Due soon 1 hour before the deadline.
A warranty email arrives on Monday at 15:30. The ticket uses 1.5 hours of the goal before 17:00 on Monday and the remaining 2.5 hours from 8:00 on Tuesday, so the first reply is due on Tuesday at 10:30, and the ticket turns Due soon at 9:30. With the goal applied at all hours instead, the same ticket would be due on Monday at 19:30, after the office has closed.
A pause condition changes the clock on the other goals. With Waiting on contact set as a pause condition, a ticket waiting for the homeowner's photos of a leak stops its timer until the status changes, and the timer resumes once the ticket leaves that status.
Tickets That End in a Site Visit
A help desk built this way answers and closes customer requests, and some requests end at the customer's address: a leak after a repair, a unit that will not start, a missed spot on a clean. The ticket records the request and the reply. Its pipeline, owners and SLA goals measure the support team, and none of the help desk articles checked describes a technician, a visit time or a work order.
The return visit is a job, with its own record. What is HubSpot Service Hub sets a ticket and a field job side by side, dimension by dimension, and the HubSpot Service Hub dashboard page covers what Service Hub reports show for a field business.
FieldRanger for the Visit a Ticket Requests
FieldRanger takes the visit, and the ticket stays in the help desk. A won HubSpot deal becomes a job with its context carried over, and the deal shows the job's status as the technician starts and completes it. Job completions, notes and updates are logged to the HubSpot timeline, and photos taken on the job sync to the customer's HubSpot record, so the agent who owns the ticket can read what happened on site without asking the crew.
A job status change can also trigger a HubSpot workflow, such as a task for the ticket owner to close the ticket once the return visit is complete. Contacts and companies stay in two-way sync, so the contact on the ticket is the contact on the job. Plans are per technician on pricing, and Start free trial runs 14 days with no card.
Frequently asked questions
How to set up HubSpot Service Hub?
On Professional or Enterprise, assign Service seats, run the setup flow under Service > Help Desk, shape the ticket pipeline under Settings > Data Management > Objects > Tickets, connect a team email channel, set routing and SLA goals, then create the knowledge base and support portal. Finish with a test ticket from an outside address.
Which HubSpot Service Hub tier includes the help desk?
Professional and Enterprise. HubSpot's help desk articles, checked November 12, 2026, list those two tiers, and the Service Hub product page places the help desk workspace and knowledge base on Professional.
Can HubSpot Service Hub be set up on the free plan?
Partly. Free tools include ticketing, the default ticket pipeline and team email, with no help desk, knowledge base, support portal or SLA goals. Accounts created after April 1, 2024 cannot create tickets from conversations inbox channels.
How to connect a support email address to the HubSpot help desk?
Under Settings > Inbox & Help Desk > Channels, click Team Email, then Connect email address, choose help desk as the destination and Gmail, Office 365 or Other as the provider. Set the from name, signature, ticket pipeline, status, priority and assignment rule.
How to set SLAs in the HubSpot help desk?
As a Super Admin, open Settings > Inbox & Help Desk > Help Desk, click SLAs under Help desk automation, choose the scope, set time to first reply, next reply and close, add business hours and pause conditions, save and turn SLAs on.
How to set up a customer portal in HubSpot?
Navigate to Service > Customer Portal and click Get Started. Name the portal, choose a connected domain and slug, add a support form if wanted, pick the help desk for new portal tickets, set which tickets each contact sees and choose access groups or self-registration.
The test ticket in step 11 is the proof that the setup holds, and it belongs in the routine after every new channel or SLA change: one message from an outside address, one ticket with the right pipeline, owner and due time, and one portal login that shows it.
Run field service on HubSpot with FieldRanger
Estimates with e-signature, scheduling and dispatch, a technician mobile app and invoicing, synced to the HubSpot deals and contacts the business already keeps.
Book a demo