HubSpot’s ticket pipeline gives your support team a structured way to track, manage, and resolve customer issues. Instead of handling requests through a shared inbox or spreadsheet, tickets move through defined stages so nothing gets missed and every conversation has an owner and a clear status.
This guide covers how to set up a ticket pipeline, choose the right stages for your team, and use automation to keep response times short.
Open HubSpot and go to Service Hub, then Tickets. You will land on the board view of your default pipeline.
Click the pipeline name dropdown at the top of the board and select “Edit pipelines” to access stage configuration.
Create stages that reflect how your team actually works — for example: New, In Progress, Waiting on Customer, Escalated, Resolved.
Require specific fields to be filled in before a ticket can move forward — such as Category, Priority, or Root Cause. This keeps reporting accurate without relying on manual discipline.
Add workflow triggers to route new tickets, send acknowledgment emails, or alert the team when a ticket has not moved in a set number of hours.
What Is a HubSpot Ticket Pipeline?
A ticket pipeline is a visual board that tracks the status of customer support requests from the moment they are created to the point they are resolved. It works the same way as a deals pipeline in HubSpot’s Sales Hub — each ticket moves through a series of stages you define based on how your team handles incoming issues.
Tickets can be created manually by your team, automatically from a form submission or email, or via the shared inbox when a customer contacts you. Once created, a ticket appears on the board and stays there until it reaches a closed stage.
The key difference from a shared email inbox is visibility. A pipeline shows you at a glance what is open, who owns each ticket, how long it has been sitting in each stage, and whether it is on track or overdue. That information is very difficult to get from an inbox alone.
How Do You Set Up a Ticket Pipeline in HubSpot?
A basic pipeline setup takes around 15 minutes. The most important step is deciding on your stages before you build them.
Plan your stages first. Common stage structures for a small team include: New, In Progress, Waiting on Customer, Resolved. For teams with escalation paths, add an Escalated stage between In Progress and Resolved. Keep the total number of stages below six — more than that creates friction and leads to tickets stalling in intermediate states.
Navigate to pipeline settings. In HubSpot, go to Service > Tickets. Click the pipeline dropdown at the top of the board and select “Edit pipelines.” From there you can rename stages, set their order, and mark which stage counts as the closed state.
Configure required properties per stage. When a ticket moves into a new stage, you can require specific properties to be filled in before the move completes. For example, require a “Root Cause” property before a ticket can move to Resolved. This keeps your data clean without extra policing.
Set your default board view. Use filters to save a board view that shows only open tickets assigned to the current user. This becomes the starting point for each team member at the beginning of each day.
How Should You Structure the Stages in Your Ticket Pipeline?
The right structure depends on how your team works and how complex your support cases tend to be.
A lean B2B team handling a mix of technical and account queries typically needs: New, Assigned, In Progress, Waiting on Customer, Resolved. The “Waiting on Customer” stage is worth adding early, because it removes tickets from the active queue without closing them. Your team is not chasing things that are blocked waiting for a reply, but the ticket does not disappear either.
Teams that escalate to a technical lead benefit from an “Escalated” stage between In Progress and Resolved. This makes escalation volume visible in reports and creates a natural checkpoint for quality review before closure.
If you have genuinely different request types with separate workflows, use separate pipelines rather than adding more stages to a single one. HubSpot supports multiple pipelines on the same account, and keeping each pipeline focused makes the board easier to manage and the automation easier to maintain.
How Do You Automate Ticket Management in HubSpot?
HubSpot’s workflow tool connects directly to tickets. A few automations that add immediate value when you first set up a pipeline:
Auto-assign by category. When a ticket is created with a specific category — such as Billing or Technical — automatically assign it to the relevant team member or rotation group. This removes the manual triage step that typically slows down first response times.
Send an acknowledgment on creation. Trigger an email to the customer as soon as a ticket is created, confirming receipt and sharing an expected response window. For Southeast Asian teams where customers often reach out via LINE, you can extend this notification through a LINE integration as well.
Flag inactivity. Set a workflow to reassign or alert on tickets that have been sitting in “In Progress” for longer than a defined period without activity. This prevents tickets from going quiet without resolution.
Auto-close after no reply. When a ticket moves to “Waiting on Customer” and no reply comes within a set number of days, automatically close the ticket and send a summary to the customer. If they do reply, move the ticket back to “In Progress” so it reappears on the active queue.
For more on setting up workflows in HubSpot, the HubSpot automation workflows guide covers the workflow builder and common trigger patterns in detail.
How Do You Track Ticket Performance and Response Times?
Service Hub includes built-in reporting views for ticket volume, first response time, time to close, and tickets by owner or category. These are available without custom configuration once your pipeline is active and tickets are flowing through it.
The three metrics worth tracking first are: average first response time, average time to close, and ticket volume by category. These tell you whether your team is keeping pace with incoming volume and where the most common issues come from.
To go deeper, create a custom report that filters tickets by category and stage, then adds a time-in-stage column. This shows you where tickets are getting stuck. If Escalated tickets are sitting longer than expected, that is a signal the escalation path needs attention — either more resource or a clearer handoff process.
The HubSpot reporting guide covers dashboard setup and the metrics worth tracking across your CRM, including service-specific views.
Can You Run Multiple Ticket Pipelines in HubSpot?
Yes. HubSpot supports multiple ticket pipelines on the same account. This is useful when you have clearly distinct request types that need different stage structures, owners, or automation rules. A common example is a standard customer support pipeline alongside a separate bug-tracking or escalation pipeline for technical issues.
Each pipeline has its own stage configuration, and workflows can be scoped to run only on tickets in a specific pipeline. Multiple pipelines are available on Service Hub Starter and above. The free tier is limited to one pipeline.
When a ticket needs to move between pipelines — for example, from customer support to a technical escalation pipeline — create a new ticket in the second pipeline and link it to the original using the ticket’s associations. This keeps the audit trail clear without duplicating the record.
Frequently Asked Questions
Do I need Service Hub to use ticket pipelines?
The Tickets tool and a single pipeline are available on the HubSpot free plan. Additional pipelines, SLA management, and advanced automation require Service Hub Starter or above.
Can tickets be linked to contacts and companies?
Yes. When you create a ticket, you can associate it with an existing contact and company record. This links the support history directly to the CRM record, so your sales or account team can see any open or recent issues before a call. The HubSpot contacts guide covers how contact records and associations work.
What is the difference between a conversation and a ticket in HubSpot?
A conversation is a thread in the shared inbox — it represents an active exchange with a customer. A ticket is a structured record with a pipeline stage, properties, and a formal resolution status. Conversations can be converted into tickets, and a single ticket can be linked to multiple conversation threads.
How do I set SLAs on a ticket pipeline?
SLA management is available on Service Hub Professional. You can set time-to-first-response and time-to-close targets per ticket priority level. HubSpot highlights tickets that are approaching or past their SLA target directly on the board view, so your team can prioritise without manually checking every record.
How do tickets connect to the HubSpot deals pipeline?
You can associate tickets with deals, which is useful when a support issue directly affects the status of an active or renewal deal. The HubSpot deals guide covers deal associations and how to use them to maintain visibility across the customer relationship.
This is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us