Guide
Customer support in HubSpot – tickets, SLAs and Customer Agent
How to build customer support in HubSpot: ticket pipeline, priorities, SLAs and routing. Then Customer Agent takes the common questions and hands over the rest.
By Viktor Olsson, founder and RevOps consultant
Guide · Support· Updated · 19 min read
Customer support in HubSpot is built in Help Desk, HubSpot's workspace for tickets in Service Hub Professional and Enterprise. Every email, chat, form and call becomes a ticket with an owner and a priority. SLA targets show how long you have to reply and to resolve the ticket, and a workflow raises the alarm before time runs out. Once that foundation works, Customer Agent, HubSpot's AI agent for customer service, can take the common questions and hand the rest over to a person. Build it in that order. An AI agent that hands over to a queue nobody watches helps nobody.
Why tickets get lost in a shared inbox
Take the example customer Solvik Teknik AB. One Monday, the CFO, Maria Ström, emails support about an incorrect invoice, for 48 licences instead of the 40 in the contract. The email lands in support@, a shared inbox read by three people. Everyone sees it, and everyone assumes someone else has picked it up. The next day the rep sends the same customer a quote for an upgrade. The invoice error takes three weeks to resolve in the end.
Nobody does anything wrong. A shared inbox lacks what keeps tickets in order:
- No owner. Everyone can read the email, but nobody owns it.
- No status. You can't see whether the customer is waiting for you or you're waiting for the customer.
- No clock. Nobody knows how long the customer has waited until the customer gets in touch again.
- No link to the customer. The rep and the customer success manager (CSM) can't see that the customer has a problem.
- No numbers. You can't say how long a ticket takes or which questions come up most.
We've seen the difference at a client, a B2B company with five people in support. Every ticket sat in a shared inbox, and nobody knew who owned what. After the move to HubSpot with ticket queues, automatic routing and reply templates, the time from a ticket coming in to it being resolved dropped by 80%. The number is the client's own, taken from HubSpot.
The ticket pipeline: a status for every situation
In HubSpot every ticket moves through a pipeline of statuses, and each status is either open or closed. Out of the box there are four: new, waiting on contact, waiting on us and closed. For a B2B team we usually use five, and write down exactly when a ticket moves:
| Status | The ticket moves here when | SLA clock |
|---|---|---|
| New | The ticket has been created from an email, chat, form or call. Nobody has replied yet. | Running |
| In progress | Someone owns the ticket and is working on it. | Running |
| Waiting on customer | You've asked a question or proposed a fix and are waiting for a reply. | Paused |
| Waiting internally | The ticket is with the developers, finance or a supplier. The owner in support stays the same. | Running |
| Closed | The customer has confirmed the fix, or hasn't replied in ten days. | Stopped |
Two rules make a big difference:
Waiting internally doesn't pause the clock. The customer is still waiting, whoever on your side has the ball. Pause the clock here and the report looks good while the customer gets more and more annoyed.
Tickets waiting on the customer close automatically. A small workflow sends the customer a reminder after five days and closes the ticket after ten. Otherwise the list fills up with tickets nobody is waiting for any more.
If the customer replies to a closed ticket, it can reopen. In Help Desk you choose whether that always happens, only within a set time or never. HubSpot filters out automated replies such as out-of-office messages, so they don't reopen the ticket.
The ticket also needs two fields:
Category. A field with five to eight options, for example Invoice and contract, Login and access, Product fault, Question about a feature and Feature request. Make it required when the ticket is closed, which you set per status in the pipeline settings. The category shows which questions come up most, and which ones Customer Agent can take.
The company. Every ticket should be associated with a company, not just a contact. It's the company that has an account owner, a contract and a renewal date.
Priorities everyone reads the same way
HubSpot has its own priority field on the ticket, and the SLA targets can be based on it. What matters is that everyone on the team gives the same ticket the same priority. We use three levels and write down what they mean:
-
High
The customer can't work, or a payment is on hold
- The service can't be used
- A fault that affects many users
- An incorrect invoice
-
Medium
Something doesn't work, but there's a workaround
- A fault that affects one user
- A feature that doesn't do what it should
-
Low
Questions and requests that can wait
- How do I …?
- A request for a new feature
- A new billing address or contact person
High means the customer can't work, many users are affected or a payment is on hold. Incorrect invoices go here for two reasons. The customer won't pay until the error is fixed, and the person complaining is often the one who decides on the renewal.
Medium is a fault with a workaround, or one that affects only one person. Most fault reports land here.
Low is questions about how something works, feature requests and changes that can wait a few days.
The person who picks up the ticket sets the priority. If almost everything becomes high, the priority stops meaning anything. Look at the split every month, and rewrite the descriptions if the share of high keeps growing.
SLAs: how fast you reply and resolve
SLA stands for service level agreement. In customer support it means targets for how fast you reply to and resolve a ticket. In HubSpot you set targets for time to first reply, time to next reply and time to close.
The targets can apply to all tickets or be based on one field: priority, team, source or pipeline. With Service Hub Enterprise they can also be based on several fields at once, for example priority and the customer's contract level. Then customers on an extended support agreement can get shorter times.
This is a starting point we often use for B2B companies open weekdays 08–17. The times only count within opening hours. Adjust them to what you promise in your contracts and what the team can manage.
| Priority | First reply | Next reply | Closed |
|---|---|---|---|
| High | 1 hour | 2 hours | 2 working days |
| Medium | 4 hours | 1 working day | 5 working days |
| Low | 1 working day | 2 working days | 10 working days |
The settings that make the targets work in practice:
- Opening hours. Set a time zone and opening hours. Otherwise nights and weekends count as waiting time.
- Pause. Pause the clock when the ticket is in Waiting on customer, and only then.
- Due soon. Choose how long before the target a ticket is marked as due soon. We usually pick 15 minutes for high priority and an hour for the others.
- Measure first. If you've never measured response times, start with generous targets for a month and see where you land. Then tighten them. A target that's missed every day is one the team stops caring about.
Every ticket then gets SLA status fields for the first reply and for time to close. It goes from active to due soon and overdue, and finally to completed on time or completed late. You can use these fields in workflows, lists and reports, and they're what the workflow further down is built on.
Routing: who takes the ticket?
A ticket without an owner is an email in a shared inbox again.
In Help Desk you set up routing per channel: the support@ address, the chat, the form and so on. A ticket can go to a specific person, to a team or to nobody at all. Within a team, tickets can be distributed in three ways:
- Load balanced: to the person with the fewest open tickets. This is where we usually start.
- Round robin: to each person in turn.
- Random: to someone on the team, in no particular order.
By default, only people who are available get new tickets. If nobody is available, the ticket stays unassigned, and someone needs to watch the unassigned view. There's also a waitlist. When everyone has reached their ticket limit, new tickets wait in a queue, ordered by SLA and waiting time. They're handed out as soon as someone has room. It requires you to set a limit per person first.
Skills and languages. With Service Hub Enterprise, tickets can also be routed by skill, for example language. If you have customers in Norway and Denmark, tickets in Norwegian and Danish can go to the person who speaks the language.
Categories to the right person. Invoice tickets can go straight to the person who handles invoices, with a workflow that reads the category. Decide on one place for each rule. Otherwise routing in Help Desk and a workflow can overwrite each other's choice of owner.
Who owns what. Support owns the ticket until it's closed, even while it's in Waiting internally. The account owner, usually the rep, owns the customer. The account owner needs to know when a high-priority ticket comes in from a customer with an open deal or a renewal within 90 days. We describe that handover in One customer, one place.
The workflow: escalate before time runs out
HubSpot keeps track of the time for you, so the workflow needs no delays. It starts when the first-reply SLA status changes, and reads the priority.
First reply SLA status becomes due soon or overdue
SLA status and priority
Alert the team lead, copy the account owner
Summarise the ticket and the customer's other open tickets as a note
Team lead: reply to the customer or reassign the ticket. Due in 30 minutes
Escalated = Yes
Medium or low priority
Notify the team lead
Escalated = Yes
All priorities
Remind the ticket owner
Swipe sideways to see the whole flow.
The workflow step by step:
- Start. The workflow starts when the first-reply SLA status becomes due soon or overdue. Turn on re-enrollment, since the same ticket often becomes due soon first and overdue later.
- Branch. The branches are checked in order, so overdue high-priority tickets come first.
- Overdue, high priority. The support team lead gets an alert, with a copy to the account owner. An AI step summarises the ticket and the customer's other open tickets as a note, so the team lead doesn't have to read the whole thread. The team lead gets a task due in 30 minutes: reply to the customer or give the ticket to someone who can. The Escalated field is set to Yes.
- Overdue, medium or low. The team lead gets a notification and Escalated is set to Yes. No task here, since there would be too many.
- Due soon. The ticket owner gets a reminder while there's still time. Unassigned tickets are caught when they become overdue.
- Resolution time. Build a similar workflow on the time-to-close SLA status. A notification to the owner and the team lead is usually enough there.
- Follow-up. A report of tickets with Escalated = Yes per month and category shows where things fall short. If it's often the same category, you may be missing a knowledge base article, or a person who knows the area.
Customer Agent: AI that takes the common questions
Customer Agent is HubSpot's AI agent for customer service. It answers customers in chat, by email, in forms, on WhatsApp and on Facebook Messenger, and by phone (public beta). It answers from your knowledge base and other sources you choose, and hands over to a person when it can't answer. The agent requires Professional or Enterprise, in any hub, and uses HubSpot Credits. An overview of HubSpot's agents is in AI in HubSpot.
What the agent should answer, and what it should hand over
| Let the agent answer | Hand over to a person |
|---|---|
| How do I …? Questions with an answer in an article | Incorrect invoice or credit note |
| Where do I find the invoice or the contract? | Cancellation, renewal and price |
| Opening hours and how to get in touch | Complaints |
| Known issues, if you have a status page as a source | Can't log in |
| Security and personal data | |
| The customer mentions a competitor |
By default the agent hands over when it can't answer, when the customer asks for a person and when the agent is paused. On top of that, you write your own rules with words and phrases that should always go to a person. Start from the right-hand column: anything about money, contracts or a customer who may be about to leave. An email where the customer mentions a competitor should be answered by a person.
Then you choose how the handover happens. The conversation can go straight to the next available person, to a person who follows up later, or stay with the agent. During opening hours we hand over straight away. Outside opening hours it becomes a ticket that's picked up the next morning. In the chat you can also let the agent take the conversation when no person is available.
The handed-over ticket lands in the same queue as everything else, gets an owner and follows the same SLA.
The whole conversation comes along
The person who takes over sees the whole conversation and what the agent has already said. The customer shouldn't have to start over. Since summer 2026 Help Desk shows which of the agent's tickets are waiting for a person. For every reply you can also see which sources the agent used, which is where you find the article that gave the wrong answer.
The knowledge base decides the answers
The agent answers from the sources you connect: knowledge base articles, website pages, blog posts, files and links. HubSpot says the sources should be comprehensive and up to date. If you have customers in several languages, the articles also need to exist in their language. We describe how the knowledge base can be connected to a translation management system in Translate your HubSpot knowledge base with Phrase.
An example. An article from last year says you invoice quarterly, but since the summer you invoice annually. A customer asks why the invoice is so high, and the agent answers as confidently as ever that it must be a mistake, since you invoice quarterly. Now you have one more ticket, and a customer who has been told two different things.
That's why every article needs an owner and a date when it's reviewed again. Two tools help:
- Knowledge from resolved tickets (beta). HubSpot can draft questions and answers for the agent from resolved tickets. Someone approves each pair before the agent uses it.
- Knowledge Base Agent (beta, Service Hub Professional and Enterprise) reads closed tickets and suggests new articles where answers are missing. It also suggests edits to articles that may be unclear, outdated or incomplete. A person approves every suggestion before it's published. It needs at least five closed tickets to work from and uses credits for each article it writes.
The same need for order applies to the customer data in the CRM, which the agent reads too.
Measure how much the agent resolves
The number to follow is the share of conversations the agent resolves completely, without handing over. HubSpot's reports for the agent show resolved conversations and handovers. Since 14 April 2026 you pay per conversation the agent resolves, so the same number also drives the cost.
Also read a sample of the conversations every week for the first few months:
- Was the answer right? A resolved conversation with a wrong answer is worse than a handover.
- Did the agent hand over when it should? If not, the handover rules need tightening.
- Which questions couldn't it answer? That's where an article is missing.
Start with one channel, usually the chat, and read the handovers for a few weeks before you add email. That's HubSpot's own advice too.
The same invoice, with support in place
This is how Maria's email about the invoice goes with all of this in place:
| When | What happens |
|---|---|
| Monday 08:12 | Maria emails support@ about the invoice. The email becomes a ticket in Help Desk, associated with Maria and Solvik Teknik AB. |
| 08:12 | The ticket goes to Lina in support, who has the fewest open tickets. |
| 08:25 | Lina sets the category to Invoice and contract and the priority to high. The first reply is due by 09:12. |
| 08:25 | The rep who owns Solvik Teknik is notified of a high-priority ticket from a customer with an open deal. |
| 08:40 | Lina replies to Maria that the error is confirmed and a new invoice will arrive by Wednesday. The ticket is in Waiting internally, with finance. |
| Tuesday 14:00 | Finance credits the invoice and sends a new one. Lina closes the ticket, within the two-working-day target. |
| Wednesday | The rep calls Maria, hears that the invoice is sorted and sends the quote for the upgrade. |
Had Lina been off sick, the ticket would have gone to someone else, since only people who are available get new tickets. Had nobody replied, the team lead would have had an alert at 09:12.
Two days instead of three weeks, and the rep sends the quote after the invoice is sorted. An open high-priority ticket also lowers the customer's health score in the model from Customer health score in HubSpot, for as long as it stays open.
All of this assumes that the customer exists only once in HubSpot. If the company is in there twice, the ticket can end up on the duplicate, and then the rep isn't notified even with the workflow in place. How duplicates come about and how to clean them up is in How to clean up HubSpot before you switch on the AI agents.
How quote, contract and invoice fit together in HubSpot, so that fewer invoices go wrong in the first place, is covered in From quote to invoice in HubSpot.
How to build it in HubSpot
- Connect the channels to Help Desk: the support@ address, the chat, the contact form and the phone. Every message becomes a ticket.
- Set up the pipeline with the statuses above, and add the Category and Escalated fields. Make the category required when the ticket is closed.
- Write down the priorities and put the description where the team sees it, for example in an internal article.
- Create the team and the routing per channel: load balanced, and only to people who are available.
- Set the SLA targets per priority, with opening hours, time zone and a pause on Waiting on customer.
- Build the workflows: the escalation above, a similar one for resolution time and the one that closes tickets waiting on the customer.
- Create the views the team works in: my open tickets, due soon, unassigned, and high priority from customers with a renewal within 90 days.
- Build the reports: share of tickets within SLA per priority, time to first reply and number of tickets per category.
- Write the articles for the 20 most common questions, based on the categories. Then connect Customer Agent to the chat.
For a support team of a few people, this usually fits in an implementation of SEK 25,000–50,000.
Common mistakes
- Everything becomes high priority. Then the priority means nothing and the SLA alerts go off all the time.
- Tickets without an owner. Assigning tickets to a team without anyone watching the unassigned view is a shared inbox with a new name.
- Tickets not associated with a company. Then the account owner never hears about them, and the ticket doesn't show on the company record.
- Customer Agent before the knowledge base. The agent answers just as confidently from an old article as from a new one.
Common questions
Which HubSpot licence do you need for tickets and SLAs? Help Desk, SLA targets and automatic routing are in Service Hub Professional and Enterprise. The people working the tickets need a Service seat to get custom views, SLA warnings and tickets from automatic routing. SLA targets based on several fields at once, and routing by skill, require Enterprise. Features change often, so check what your licence includes.
What does Customer Agent cost? The agent requires Professional or Enterprise and is paid for with HubSpot Credits. Since 14 April 2026 you only pay for the conversations the agent resolves. If the credits run out, the agent stops taking new conversations until the credits renew or you buy more, unless you've turned on automatic top-ups. Routing to your staff needs to work then too. Prices change often, so check HubSpot's current price list before you budget.
Does Customer Agent reply in Swedish? Yes. Swedish is one of the languages HubSpot supports. In the agent's settings you choose which languages it should reply in. If you choose none, it replies in the language it detects in the customer's first message. Still, test it with your most common questions before you switch it on. The agent answers from your sources, so they need to exist in Swedish too.
What's the difference between a shared inbox and a ticketing system? In a shared inbox everyone sees the same emails, but nobody owns them and nothing is measured. In a ticketing system like HubSpot's Help Desk, every ticket gets an owner, a status and a clock, and it shows on the customer.
What is an SLA in customer support? A target for how fast you reply to and resolve a ticket, often different for different priorities. It can be an internal target or something you promise the customer in the contract. Don't promise customers shorter times than you already manage internally.
Do we need several ticket pipelines? Rarely at the start. One support pipeline is enough for most B2B teams. Add another when the process really differs, for example returns where equipment is sent back. Every new pipeline adds statuses, views and reports to keep in order.
About the author
Viktor Olsson, founder and RevOps consultant
Viktor has worked with HubSpot for six years, with teams from 3 people to organisations with 30 sales reps across the Nordics. He also works in RevOps at an international SaaS company.