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 means "nobody owns it". We fixed both in one afternoon. This is the playbook.
If you are setting up HubSpot Service Hub and you want Help Desk to actually behave like a support tool and not a shared inbox with extra steps, there are four decisions you make in hour one. Get them right and the rest of the configuration is mechanical. Get them wrong and you will spend three months retrofitting.
Do you have the right Service Hub tier for SLAs and routing?
Short answer: you need Service Hub Professional or Enterprise for SLA goals in Help Desk, and the same tier for ticket routing. Starter does not have either. 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".
One nuance worth knowing: accounts created after April 1st, 2024 cannot set SLAs in the conversations inbox anymore. HubSpot wants you on Help Desk for ticket management and SLA goals. If you are on a newer portal and still trying to configure SLAs in the old inbox, that is why the option is missing.
Decision 1: First reply time or time to close, or both?
HubSpot lets you set SLA goals on time to first reply and time to close. Most teams I work with want both, but they should not be the same number for the same priority.
What I see work: first reply gets the aggressive SLA (because it is the customer-facing promise), time to close gets a realistic one (because resolution depends on engineering, third parties, the customer responding to your questions). A common shape:
- First reply: 1 hour for Urgent, 4 hours for High, 1 business day for Medium/Low
- Time to close: 4 hours for Urgent, 1 business day for High, 3-5 business days for Medium/Low
Pick numbers your team can actually hit during business hours you actually staff. An SLA you breach 40% of the time is not an SLA, it is a guilt-trip generator.
Decision 2: One SLA for everyone, or priority-based rules?
HubSpot supports both. You can apply a universal SLA rule to all tickets for a consistent experience, or use one ticket property like Priority is Urgent to trigger a stricter goal, such as a 30-minute response requirement for emergency cases. You can also combine ticket properties for things like "Tier 1 customer AND Priority High".
My rule of thumb: start with priority-based, not universal. The reason is that a universal SLA forces you to set it at the strictest level your worst tickets demand, which means your team breaches on routine stuff that should have had 24 hours of slack. Priority-based lets you actually use Urgent as a signal, not a vibe.
If you do not have a priority property habit yet, fix that first. SLAs without a discipline of setting priority on intake are just a stopwatch on chaos.
Decision 3: Leave routing on default, or assign tickets automatically?
This one is non-negotiable. By default, incoming tickets in Help Desk are left unassigned. Which means: every new ticket sits in a queue until somebody manually claims it. Which means: at 9:03 AM Monday, three agents open the same ticket, two close it, and the customer gets a confused thread.
Ticket routing is available on Service Hub Professional and Enterprise. Turn it on. The simplest version is round-robin across your support team. That alone fixes the "nobody owns it" problem and gives your SLA clock somebody to belong to.
Worth saying out loud: an SLA without routing is theater. The 1-hour first-reply timer starts at ticket creation, not when somebody happens to notice the ticket. If routing leaves it unassigned for 45 minutes, you already burned 75% of your buffer before a human touched it.
Decision 4: Round-robin or skill-based routing?
Round-robin is fine for a 3-person team where everyone handles everything. The moment you have specialists (one agent handles billing, one handles technical, one handles onboarding), round-robin starts costing you. Tickets land on the wrong agent, get reassigned, the SLA clock keeps ticking.
That is when you flip on skill-based ticket routing, configurable in Help Desk settings. You define skills (Billing, Technical, German-speaking, Enterprise accounts, whatever maps to your team), tag each agent with their skills, and tickets route to the right person on the first hop.
The configuration takes maybe 30 minutes. The payoff is real: I have seen teams cut average reassignments per ticket from 2.3 to under 0.4 just by getting the first routing decision right. That is the difference between meeting an SLA and breaching it.
What order do you actually build this in?
If I had one hour with a fresh Service Hub Professional portal and a support team waiting:
- Minutes 0-10: Confirm tier, enable Help Desk, check that ticket pipeline and priority property are set up sensibly.
- Minutes 10-25: Turn on ticket routing. Start with round-robin across the team so nothing sits unassigned.
- Minutes 25-45: Configure SLAs. Priority-based, first reply + time to close, business hours that match reality.
- Minutes 45-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 in this list: dashboards, custom reports, Breeze, automation workflows. Those come later. Hour one is about making sure tickets get to a human inside the SLA window. Everything else is optimization on top.
One more thing: Breeze can help you stress-test the setup
HubSpot ships a Breeze Assistant inside the SLA settings (Settings > Inbox & Help Desk > Help Desk > Help desk automation > SLAs > Manage SLAs). You can ask it for recommendations on your specific setup. I do not use it to make the decisions, but it is decent for sanity-checking edge cases like "what happens to SLA timers when a ticket is reopened". Saves a tab to the docs.
If you want a second pair of eyes on your Service Hub configuration before you roll it out to the team, I run 60-minute audits of existing HubSpot portals. Book a call: spectage.co/en/contact.
Frequently asked questions
Which Service Hub tier do I need for SLAs and ticket routing?+
Both SLA goals in Help Desk and ticket routing require Service Hub Professional or Enterprise. Starter does not include either feature.
Can I still set SLAs in the conversations inbox?+
Not if your HubSpot account was created after April 1st, 2024. Newer accounts have to use Help Desk for ticket management and SLA goals. Older accounts can still configure SLAs in the conversations inbox, but HubSpot recommends moving to Help Desk.
What happens to tickets in Help Desk if I do not configure routing?+
By default, incoming tickets in Help Desk are left unassigned. They sit in a shared queue until an agent manually claims them, which usually means SLA timers burn down before anyone is accountable for the ticket.
What is skill-based routing in HubSpot Help Desk?+
Skill-based routing assigns incoming tickets to agents tagged with matching skills (for example Billing, Technical, or a specific language). You configure it in Help Desk settings and it replaces or augments round-robin assignment so tickets reach the right specialist on the first hop.
Should I set one universal SLA or use priority-based rules?+
Priority-based rules work better for most teams because they let you apply strict goals only to Urgent tickets while giving routine tickets realistic buffer. A universal SLA forces you to set the bar at the strictest case, which leads to constant breaches on tickets that did not need that speed.