On this page
What HubSpot supports natively
| Area | Native tool | Note |
|---|---|---|
| Ticket handling | Help desk workspace | HubSpot’s recommended place to manage tickets and SLA goals |
| SLAs | SLA goals for time to first reply and time to close | Service Hub Professional or Enterprise; an assigned Service Seat is needed for advanced help desk features such as SLAs |
| Inbox SLAs | Conversations inbox | Not available to accounts created after April 1, 2024 |
| Customer health | Health scores in the Customer Success workspace | Service Hub Professional or Enterprise |
| Ticket pipelines | Pipeline settings | Custom pipeline limits depend on tier |
HubSpot also notes that SLAs only apply to conversations with an associated ticket, and tickets created by a workflow or manually from the tickets index don’t get one. A Service Hub audit should check whether that matches how your tickets are created.
What a HubSpot Service Hub audit should check
| Check | What good looks like |
|---|---|
| Ticket pipelines | Each has a clear purpose, such as support tier or product |
| Stages | Each stage is a real handoff or status, not a holding pen |
| Ticket sources | You know how tickets arrive (email, form, chat, manual) and each route is set up |
| Routing | Tickets are assigned to teams or reps by rule, not left unassigned |
| Priority | Priority is set and used in views and SLAs |
| SLAs | Goals exist and are measured; breaches are visible to the team |
| Knowledge base | Articles organized, recently reviewed, and linked from common ticket types |
| Feedback | Survey types in use, sensible frequency, and follow-up on low scores |
| Reporting | First-response and resolution reports filtered to the right pipelines |
If you use customer health scores, check the rules behind them too; this page explains what a health score measures.
Common mistakes
- Auditing only ticket volume and ignoring how tickets are created.
- Adding SLAs that the ticket creation route never triggers.
- Leaving a knowledge base nobody has reviewed in a year.
Where Jetstack AI fits
Jetstack AI’s Portal Audit has a Service Hub Audit template. Its Service section runs five blocks: Service Overview, Ticket Pipeline, Resolution Metrics, Customer Feedback and Knowledge Base. Service Overview shows service footprint, live workload, performance, customer experience and configuration health on one screen before the four detail blocks. The scoring is built for coverage, not adoption: if less than 20% of the Service section’s data points return a score, for example because the portal has no recent ticket activity to measure, the section drops out of the portal score and its 10% base weight is shared proportionally across the other sections. A Service setup that can be measured is scored as it is, so a thin help desk still shows up as a finding. To rebuild what the audit flags, Projects, currently in limited release, builds ticket pipelines, SLA goals and routing workflows from a brief, with the plan and the deployment approved separately; SLA goals and workflows are created switched off for you to check and switch on. See the Service Hub data points and what Projects can build.
Sources
- Set SLAs in the inbox (HubSpot Knowledge Base)
- Overview of the help desk workspace (HubSpot Knowledge Base)
- Service Hub data points (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Portal audits
See what needs work before you change it.
A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.
Explore Portal Audit