This post walks through the four SLA and routing decisions you make in the first hour of configuring HubSpot Help Desk: first reply vs time to close, universal vs priority-based rules, default vs automatic routing, and round-robin vs skill-based assignment. Get these right and the rest of the setup is mechanical; get routing wrong and your SLA timer burns down before a human ever touches the ticket.
Last month I sat down with a support lead who had Service Hub Professional running for 8 months and zero SLAs configured. Average first reply: 19 hours. Tickets bouncing around because routing was on default, which in HubSpot Help Desk means "nobody owns it". We fixed both in one afternoon. This is the playbook.
What tier do I need for SLAs and routing in HubSpot Help Desk?
You need Service Hub Professional or Enterprise for SLA goals in HubSpot Help Desk, and the same tier for ticket routing. Starter includes neither. This is the first thing I check before any configuration call, because half the "our SLAs are broken" questions I get turn out to be "we never had the feature to begin with".
One nuance worth knowing: accounts created after April 1st, 2024 cannot set SLAs in the conversations inbox anymore. HubSpot points those accounts to Help Desk for ticket management and SLA goals. If you are on a newer portal and still hunting for the SLA option in the old inbox, that is why it is missing.
Decision 1: first reply time, time to close, or both?
Set both, but do not use the same number for the same priority. HubSpot lets you define SLA goals on time to first reply and time to close, and these two clocks answer different questions.
First reply is the customer-facing promise, so it gets the aggressive target. Time to close depends on engineering, third parties, and the customer answering your follow-up questions, so it gets a realistic one. A shape that works for most teams I set up:
- First reply: 1 hour for Urgent, 4 hours for High, 1 business day for Medium and Low
- Time to close: 4 hours for Urgent, 1 business day for High, 3 to 5 business days for Medium and Low
Pick numbers your team can hit during the hours you actually staff. An SLA you breach 40% of the time is not an SLA, it is a guilt-trip generator that your agents learn to ignore inside a week.
Decision 2: one SLA for everyone, or priority-based rules?
Start priority-based, not universal. HubSpot supports both: you can apply a universal SLA rule to all tickets, use a single ticket property such as Priority is Urgent to trigger a stricter goal like a 30-minute response requirement, or combine ticket properties for cases like "Tier 1 customer AND Priority High".
The reason to skip universal: a universal SLA forces you to set the bar at the strictest level your worst tickets demand. Your agents then breach on routine questions that should have had a day of slack, and everyone stops trusting the number. Priority-based rules let Urgent mean something instead of being a field nobody fills in.
If your team does not set priority on intake yet, fix that habit first. SLAs on top of tickets that all default to "Medium" are just a stopwatch on chaos. This is the same discipline problem I write about in filter logic for HubSpot Segments: the automation is only as good as the property values feeding it.
.webp?width=900&height=506&name=Focus_Time_Linear_llustrations_Characters(1).webp)
Decision 3: leave routing on default, or assign tickets automatically?
Turn on automatic routing. Incoming tickets in HubSpot Help Desk are left unassigned by default, which means every new ticket sits in a shared queue until an agent manually claims it. At 9:03 Monday morning, three agents open the same ticket, two of them close it, and the customer gets a confused thread.
Ticket routing is available on Service Hub Professional and Enterprise. The simplest version is round-robin across your support team, and that alone kills the "nobody owns it" problem and gives your SLA clock somebody to belong to.
Here is the part support leads underestimate: an SLA without routing is theater. The first-reply timer starts at ticket creation, not when an agent happens to notice the ticket. If a ticket sits unassigned for 45 minutes against a 1-hour target, your agent has already burned 75% of the buffer before touching it.
Decision 4: round-robin or skill-based routing?
Use round-robin if everyone handles everything, and switch to skill-based the moment you have specialists. On a 3-person team where any agent can answer any ticket, round-robin is fine. Once one person owns billing, one owns technical, and one owns onboarding, round-robin starts landing tickets on the wrong agent, who reassigns while the SLA clock keeps ticking.
That is when you enable skill-based ticket routing, configured in Help Desk settings. You define skills that map to your team (Billing, Technical, German-speaking, Enterprise accounts), tag each agent with theirs, and tickets reach the right person on the first hop.
The configuration takes maybe 30 minutes. The payoff shows up in reassignments: I have set this up for teams where the average reassignment count per ticket dropped from over two to well under one, purely by getting the first routing decision right. Every reassignment is dead time the customer never sees and your SLA never forgives.
| Routing method | Best for | Tier | Setup time |
|---|---|---|---|
| Default (unassigned) | Nothing - it means nobody owns the ticket | Any | None, but leaves SLA clock ownerless |
| Round-robin | Small teams where everyone handles everything | Professional, Enterprise | ~10 minutes |
| Skill-based | Teams with specialists (billing, technical, language) | Professional, Enterprise | ~30 minutes |
What order do you build this in?
Build in this sequence: confirm tier, turn on routing, then configure SLAs, then add skills. If I had one hour with a fresh Service Hub Professional portal and a support team waiting, here is the order.
- Minutes 0 to 10: confirm the tier, enable Help Desk, check that the ticket pipeline and priority property are set up sensibly.
- Minutes 10 to 25: turn on ticket routing. Start with round-robin so nothing sits unassigned.
- Minutes 25 to 45: configure SLAs. Priority-based, first reply plus time to close, business hours that match reality.
- Minutes 45 to 60: if you have specialists, add skills and switch to skill-based routing. Otherwise leave round-robin and revisit in a month.
Notice what is not on this list: dashboards, custom reports, Breeze workflows, ticket automation. Those come later. Hour one is about making sure tickets reach a human inside the SLA window. Everything else builds on that.
What HubSpot Help Desk SLAs will NOT do on their own
SLAs measure and flag; they do not staff your desk or set your priorities for you. HubSpot ships a Breeze Assistant inside the SLA settings (Settings, then Inbox and Help Desk, then Help Desk, then the Help desk automation section, then SLAs, then Manage SLAs) that gives recommendations and answers questions like "what happens to SLA timers when a ticket is reopened". I use it to sanity-check edge cases, not to make the calls.
The judgment calls stay with a human: which priorities map to which targets, how skills map to your real team, and which SLA numbers your staffing can actually hit. That is the work I do when I sit with a support team. If you want a second pair of eyes on a Service Hub configuration before it goes live, I run 60-minute portal audits, and our full Service Hub setup work covers tickets, SLA, routing and help desk end to end.
