Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 37 ยท Service Hub

SLAs, Priorities and Escalation in Service Hub

Understand service level agreements in HubSpot: first response and resolution targets, priority rules, business hours, escalation workflows, and a runnable SLA breach checker.

A service level agreement (SLA) is a promise about speed: "we will reply to urgent problems within one hour and resolve them within eight." Service Hub helps you keep that promise by showing which tickets are about to miss a target, by pausing clocks at the right moments, and by letting workflows escalate problems before the customer has to ask twice.

HubSpot cannot run here, so the code is a Python stand-in that models the arithmetic. SLA features are tied to certain Service Hub plans and to the help desk workspace; check what your account offers and keep your targets in the help desk settings.

Two clocks

Most teams track two measures:

  • Time to first response: from ticket creation to the first human reply.
  • Time to close (resolution time): from creation to the Closed state.

HubSpot stores both. Time to first response and Time to close appear as ticket properties you can use in reports and workflow conditions. SLA tools let you define targets per priority and show an indicator on the ticket when the target is near or breached.

Business hours

A target of "one hour" should usually count only your support hours. If your team works Monday to Friday, 9:00 to 17:00, a ticket created Friday at 16:30 with a one-hour target is due Monday at 9:30. Configure business hours and holidays in settings so reports and SLAs use them.

Designing an SLA

Priority Urgent, high, medium, low
Targets First response and resolution
Business hours Clock counts open time only
Escalation Alert before the breach

Measure, warn, escalate

1 / 2

A business-hours SLA calculator

The stand-in below calculates a due time by walking forward through working hours. It is the same logic you reason about when you set targets.

Python Due time within business hours

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The one-hour target lands on Monday 09:30, as described above.

Priority-based targets

Different priorities get different promises. Define them once as data so they can be reviewed with the customer and the team.

Python Check tickets against priority targets

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

(The simple version counts calendar hours; combine it with the previous calculator for business hours.)

Escalation workflows

A workflow can watch the properties that matter and act:

  1. Enrollment trigger: ticket status is any of New, Waiting on us AND priority is high or urgent.
  2. Delay until the warning point, for example 45 minutes.
  3. If/then branch: is the ticket still unowned or without a first response?
  4. Actions: send an internal notification, create a task for the team lead, or set a property such as "Escalated = Yes".

See workflow triggers and actions and delays, branches and enrollment for the building blocks.

Pausing and fairness

Waiting on the customer is not your delay. Agents therefore use a Waiting on contact status, and reports on "time waiting on us" are fairer than raw creation-to-close. A common design is to report both, so you do not hide slow customers or slow agents.

Pitfalls

  • Targets nobody can meet: start from last quarter's real medians, then tighten gradually.
  • Setting everything to urgent: priority loses meaning. Document what each level means.
  • Counting automated acknowledgment emails as the "first response". Make sure the metric reflects a human reply.
  • Escalation that notifies the same overloaded person; rotate or use a team.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. A one-hour SLA ticket is created Friday 16:30; support hours are 9-17 Monday to Friday. When is it due?

    Only 30 minutes remain on Friday; the other 30 minutes are counted from Monday 09:00.
  2. 2. Why use a Waiting on contact status?

    It lets reports and SLA thinking exclude time spent waiting for the customer.
  3. 3. What is a good first step in an escalation workflow?

    Enroll on the risky condition, delay, re-check, then alert or reassign.

Summary

  • SLAs promise first-response and resolution times per priority.
  • Business hours and holidays must be part of the calculation.
  • Workflows can warn and escalate before a target is missed.
  • Keep priority definitions strict and targets realistic.

Next: Knowledge Base and Help Desk