What is a ticket SLA in HubSpot?
A ticket SLA is a service level agreement in HubSpot that sets target times for responding to and closing support tickets. HubSpot tracks each ticket against those targets and shows when a ticket is due or overdue.
An SLA turns a promise to customers into something you can measure. Common targets are time to first response and time to close, often set differently for each ticket priority: a high priority ticket might need a first response within one business hour, a low priority one within a business day. SLA timing usually follows your business hours, so a ticket that arrives on Friday evening does not breach over the weekend. SLA features and options depend on your subscription.
SLAs matter because slow responses drive escalations and churn, and because many customers have contractual response times. Tracking tickets against targets lets the team work the most urgent tickets first and lets leaders see breaches as they happen instead of in a monthly report.
SLAs only work if the setup around them is correct. Tickets need a priority, or they fall into a default target. They need an owner, or nobody sees the clock running. Business hours need to match when the team actually works. Targets need to be realistic for your team size, or every ticket is overdue and the signal is lost.
Review SLA performance regularly by priority, channel and team. A cluster of breaches usually points to a cause in the setup, such as routing that sends tickets to nobody, rather than to individual people.
Example
A payroll software company set a four-hour first response SLA for high priority tickets. Breaches spiked every Monday. The support lead found that weekend chat tickets had no priority and no owner, so they waited in a shared queue. Adding a routing rule and a default priority fixed most of the breaches within two weeks.
Common mistakes
- Setting SLA targets without matching business hours, so tickets breach overnight or at weekends.
- Leaving tickets without a priority, so they all get the same target regardless of urgency.
- Setting targets the team cannot meet, so overdue becomes normal and nobody reacts.
- Measuring breaches without assigning owners, so nobody is responsible for the ticket that is running late.
Related checks
Frequently asked questions
What is a good first response SLA?
It depends on your customers, channels and team size. Many teams set tighter targets for high priority and live channels, and looser ones for low priority email. Start with targets you can meet most of the time, then tighten them.
Do HubSpot SLAs pause outside business hours?
SLA timing generally follows the business hours you configure, so time outside those hours does not count toward the target. Check your settings, because the exact behavior depends on how SLAs and business hours are set up in your account.
Related terms
See how your portal measures up.
Ancil connects to HubSpot read-only in about 60 seconds. Nothing changes in your portal without your approval.