A ticket pipeline that doesn't match how your team actually works will quietly lie to you in every report. The goal isn't to add more statuses — it's to design ticket stages that mirror your real support process, so the board reflects reality and your metrics mean something. HubSpot's ticket pipelines are flexible, which is exactly why teams over-build them. Here's the practitioner's read on setting them up so they help, not hinder.
What is a ticket pipeline, and why does it matter?
A ticket pipeline is the set of stages a support request moves through, from opened to closed — and it's what your whole support reporting is built on. Each stage represents where a ticket stands: new, being worked, waiting on the customer, resolved. Get the stages right and you can see your backlog, response times, and bottlenecks at a glance. Get them wrong and tickets pile up in vague buckets nobody trusts. The pipeline isn't decoration — it's the backbone of how you measure and manage support.
How do you design statuses that reflect reality?
Map the actual journey a ticket takes through your team, then name a status for each meaningful handoff or wait. Start from how work really flows, not from a template. Most teams need a status for new, in progress, waiting on the customer, and closed — and the "waiting on the customer" stage matters more than people expect, because it stops you from being penalized in time-to-resolution metrics for delays that aren't yours. Worked example: a team that lumps "waiting on customer" into "in progress" sees its average resolution time balloon and can't tell whether the holdup is the agent or the customer — splitting that one stage out makes the bottleneck obvious.
How do you actually create and customize a pipeline in HubSpot?
Build it in settings under Objects then Tickets, add or rename stages, and use separate pipelines only when teams have genuinely different processes. In HubSpot you can rename the default statuses, add new ones, reorder them, and create additional pipelines for distinct teams — for example, one for customer support and one for IT requests. Resist the urge to give every team its own pipeline; only split when the actual stages differ, because each extra pipeline is another thing to maintain and report on. Keep the stage list short enough that an agent can place any ticket without hesitating.
How do you keep the pipeline from going stale?
Automate the routine transitions and set rules so tickets don't quietly rot in a status. Pipelines drift when humans have to remember to move every ticket by hand. Use automation to route new tickets to the right pipeline and owner, nudge agents when a ticket sits untouched, and update status on key actions. Worked example: a ticket with no reply for three days triggers an internal reminder, so nothing slips silently into the void. This is the same order we follow with clients — design the stages around the real process first, then automate the movement so the board stays honest without constant babysitting.
The IV-Lead take
The teams that get the most from HubSpot ticketing aren't the ones with the most elaborate pipelines — they're the ones whose stages match how work actually happens and whose automation keeps the board current. A clean, well-designed pipeline turns support from a black box into a system you can measure and improve. The trap is treating statuses as free; every extra one is a decision an agent has to make and a column a report has to explain. Fewer, truer stages beat a sprawling map every time.
Not sure your ticket pipeline reflects reality? Book a 30-minute portal audit — we'll tell you straight where your stages and automation are working against you. For the bigger picture, see how we approach HubSpot implementation and optimization.
Frequently asked questions
How many ticket statuses should I have?
As few as cleanly capture your real workflow — usually four to six. Each status should mark a meaningful change in who's responsible or what's happening. More than that and agents hesitate and reporting gets muddy.
Can I have more than one ticket pipeline in HubSpot?
Yes. You can create separate pipelines for teams with genuinely different processes, such as support and IT. Only split when the stages actually differ, since each pipeline adds maintenance and reporting overhead.
Should I use a "waiting on customer" status?
Almost always. It separates delays caused by the customer from delays caused by your team, which keeps your resolution-time metrics honest and shows where the real bottleneck is.
Can I automate moving tickets between statuses?
Yes. HubSpot lets you route tickets, assign owners, send reminders, and update status based on triggers, so tickets don't sit forgotten and the board stays current without manual upkeep.
