HubSpot Ticket Pipeline Template

How do you plan a ticket pipeline with the template?

Start with the pipeline plan: one row per ticket pipeline with its purpose, the tickets it holds, its owner, which teams can use it and its ticket defaults. Then write the statuses in order with your agents, choose required properties, record channels and routing, set the SLA plan, and only then build it in HubSpot.

Keep separate pipelines for processes that really differ, such as support and onboarding. One pipeline per team usually splits reporting without changing how tickets are worked. Our HubSpot help desk guide covers plans, seats, channels and views in more depth.

What should each ticket status record?

Its order, whether it is Open or Closed, what is true when a ticket enters, what must happen before it leaves, what the customer is waiting on, the properties an agent must fill in, whether it pauses the SLA or counts toward capacity, and who moves the ticket. Your agents write the criteria; the examples are illustrative.

• Default statuses: HubSpot's default Support Pipeline has New, Waiting on contact, Waiting on us and Closed. Rename or add statuses so they match how your team really works.
• Open or Closed: help desk views such as Unassigned and All Open only show tickets in an Open status, so set the flag deliberately.
• Name by who is waiting: a status like Waiting on contact tells a support lead at a glance who owes the next step. The template's standards page has examples of vague and checkable criteria.

Which HubSpot help desk settings does it cover?

When we checked HubSpot's documentation in October 2026, the help desk workspace needed Service Hub Professional or Enterprise, custom pipelines needed Starter or higher, and routing rules and capacity limits needed an assigned Service Seat. The template records your choice for each: ticket defaults, required properties, routing per channel and capacity.

• Required properties: conditional stage properties can require a value, such as Resolution, when a ticket moves to a status. Ticket name, Pipeline and Ticket status are required by default when you create a ticket manually.
• Routing: each channel's Routing tab can send tickets to specific users and teams, a team only, the contact owner, an assignment workflow or the customer agent, distributed by Load Balanced, Round Robin or Random.
• Capacity: limits cap open tickets per user, in total or per channel type, and you can exclude statuses such as Waiting on contact from the count. Skill-based routing needs Service Hub Enterprise.
• Team access: restricting a pipeline by team and stage calculated properties such as time in each status need Professional or Enterprise.

How do you plan SLAs per priority?

Fill in one row per priority, or per rule, with targets for time to first reply, time to next reply and time to close, the due soon point, the schedule and the statuses that pause the timer. The targets are left blank on purpose: your team sets them, because HubSpot's documentation examples are not recommendations.

Two HubSpot behaviors shape the plan. Snoozing a ticket does not pause its SLA, so use a pause condition on a status instead. And the SLA rule is chosen when the SLA is applied and not re-evaluated, so priority must be set when the ticket is created. Our HubSpot ticket SLA guide covers setup, statuses and breach alerts.

How do you run the monthly ticket review?

Once a month, work through the review checks: the backlog by status and owner, SLA breaches by rule, reopened tickets, unassigned tickets, tickets waiting on the customer too long, and whether seats, routing and capacity still fit the team. Enter tickets created and closed to calculate the backlog change, and log every change.

HubSpot's help desk pages describe replies to closed tickets in different ways, so check how your account handles them before you count reopened tickets. For automation you add after the review, our free workflow design template keeps each workflow documented. More templates and guides are in our HubSpot resources.

Ticket pipeline planning checklist