HubSpot Ticket SLAs: Setup, Statuses and Reports

Which HubSpot plans and seats include ticket SLAs?

When we checked HubSpot's documentation in October 2026, SLA goals in help desk needed Service Hub Professional or Enterprise. Rules based on a combination of ticket properties, including custom properties, needed Service Hub Enterprise. Super Admin permissions are required to set help desk SLAs, and an assigned Service Seat is needed to see SLA warning labels.

HubSpot's help desk pages also describe SLAs as an advanced help desk feature that needs an assigned Service Seat. If some of your support team work on core seats, check what they can see before you rely on labels as the main warning. For a wider look at what changes between tiers, see HubSpot Professional vs Enterprise.

Should you set SLAs in help desk or in the inbox?

Use help desk. When we checked in October 2026, HubSpot said accounts created after April 1, 2024 cannot set SLAs in the conversations inbox and recommended help desk for SLA goals. Help desk SLAs also do more: a time to next reply goal, pause conditions, rules by team, source or pipeline, and retroactive updates to open tickets.

Inbox SLAs have two more limits worth knowing if you still use them. They only apply to conversations with an associated ticket, so tickets created by a workflow or manually from the tickets index page get no SLA. And only replies sent from a connected team inbox update the SLA; replies from an individual work email or outside HubSpot don't count. If you are moving to help desk, our HubSpot help desk guide covers the workspace itself.

How do you set up SLA goals in HubSpot help desk?

Go to Settings, then Inbox & Help Desk, then Help Desk, and click SLAs in the Help desk automation section. Choose whether goals apply to all tickets, one ticket property or a combination of properties. Set Time to first reply, Time to next reply and Time to close, set the Due soon point, then save and switch SLAs on.

• One ticket property: set goals per value of priority, team, source or pipeline. Turn the Goal Active? switch off for any value that should have no SLA.
• Combination of properties (Enterprise): build named rules from filters and filter groups, including custom properties and associated company properties. If a ticket matches more than one rule, the rule highest on the list wins, so drag rules into the right order.
• Fallback rule: with combined rules, turn on Use fallback SLA rule so tickets that match nothing still get goals.
• Rules are set once: HubSpot picks the SLA rule when the SLA is applied, based on the ticket and associated property values at that time. If those properties change later, the rule is not re-evaluated.
• Edit, clone or delete rules from the same SLAs page by hovering over a rule.

That "set once" behavior is the part teams miss. If priority or tier is filled in by a workflow a few minutes after a ticket is created, the ticket may already sit under the wrong rule. Fill the deciding properties at creation, for example on the form or channel, or test the timing in your own account first.

How do business hours and pausing affect the SLA timer?

By default a help desk SLA counts at all times. To count only working time, open the rule's Schedule section, choose During specific time, then pick a time zone and hours. To stop the clock while a ticket waits on someone else, add pause conditions by pipeline and ticket status; the timer resumes when the ticket no longer matches.

• Each rule has its own schedule, including the fallback rule, so different teams or regions can run on different hours.
• Snoozing does not pause the SLA. HubSpot says the SLA keeps running while a ticket is snoozed. Use a pause condition on a ticket status instead.
• User working hours are separate. They set when a user is Away and not eligible for automatic assignment; they are not the SLA schedule.
• Inbox SLAs use Operation hours or 24/7. HubSpot says holidays are not accounted for when it works out those hours, and tickets in Waiting on contact still count.

HubSpot's help desk SLA page doesn't say how holidays are handled in a help desk schedule, so check this in your account before a public holiday rather than after.

What SLA statuses and properties does HubSpot add to tickets?

When you use SLAs, HubSpot adds four ticket properties: Time to First Response SLA Due Date, Time to First Response SLA Status, Time to Close SLA Due Date and Time to Close SLA Ticket Status. The status properties show Active SLA, Due soon, Overdue, SLA completed on time or SLA completed late, for use in reports, lists and workflows.

• SLA hours properties: Time to first response in SLA hours and Time to close in SLA hours measure time within the SLA schedule. They are only populated for help desk tickets and include data from January 2025.
• Retroactive changes: if you apply changes to existing open tickets, SLAs already met are not updated. Goals with time remaining are recalculated.
• Merged tickets keep the primary ticket's SLA, so due dates can shift and the SLA status may not match the current ticket status.
• Next reply: help desk lets you set a Time to next reply goal, and the help desk Summary page and reports track next response. HubSpot's SLA page still lists only the four properties above, so check which next response fields your account shows before you build on them.

How do you alert your team before a ticket breaches its SLA?

Build a ticket-based workflow that enrolls tickets when an SLA status property, such as Time to first response SLA Ticket Status or Time to close SLA Ticket Status, becomes Due soon or Overdue. Then add a notification action: an internal email, an in-app notification or a Slack notification to specific users, teams, owners or channels.

• Due soon is your warning point. Set Mark as due soon on each goal so alerts fire while there is still time to act, not only after a breach.
• Separate warning from escalation. A typical pattern is one workflow that notifies the owner on Due soon and another that notifies a lead or team channel on Overdue.
• In-app labels appear next to the ticket number in the reply editor, but only for users with an assigned Service Seat.
• Custom views in the help desk left sidebar need a Service Seat and Custom views permissions to create, and Super Admin or Account Access permissions to set a view shared with Everyone as the homepage.

Keep alert workflows few and clearly named, or the team learns to ignore them. Our HubSpot workflows guide covers enrollment triggers, re-enrollment and testing.

How do you report on SLA breaches in HubSpot?

Start with the ready-made reports: go to Reporting, then Reports, and search for "sla" to find them. The help desk Summary page shows SLA progress with Overdue, Due soon and Active tickets. For custom reports, use the SLA status properties and the SLA hours properties in the custom report builder, for example with the Tickets data source.

• SLA progress on the help desk Summary page filters by Time to close, Time to first response, Time to next response or Completed.
• Completion over time: help desk reports show how many tickets met or missed first response, next response and time to close SLAs.
• 24/7 vs SLA hours: in the service analytics suite, Average time to close and Average time to first response (beta) have tabs to switch between round-the-clock time and time within each SLA rule's scheduled hours.
• Data start: the SLA hours properties include data from January 2025, so older trend lines will have gaps.

A breach report is only useful if someone acts on it. Pair the Overdue count with the owner or team and review it on a set cadence, and treat repeated misses on one rule as a sign the rule, the routing or the staffing needs to change. More setup guides are in our HubSpot resources.

HubSpot ticket SLA checklist