Published August 16, 2026

HubSpot Ticket Pipelines, Done Right

A pipeline is a workflow with stages. Most HubSpot support problems are really a pipeline modelled as a wish list.

Fewer pipelines than you think

Create a separate pipeline only when the stages genuinely differ. Different teams working the same stages belong in one pipeline, separated by owner or a property, not by duplicating the workflow.

Five pipelines with the same four stages is a reporting problem you will regret in three months when nobody can answer a simple question across all of them.

Stages that mean something

Each stage should represent a real change in who is doing what. New, waiting on us, waiting on customer, closed covers most support operations honestly.

Avoid stages that describe feelings rather than states. "Escalated" is useful only if something specific happens because of it.

Waiting on customer is the stage that earns its place, because it separates our delay from their delay, and every meaningful response metric depends on that split.

The HubSpot-specific duplicate trap

HubSpot associates tickets with contacts. If one person exists as two contact records, their emails create tickets on two separate records, and neither ticket knows the other exists.

That's a duplicate that no pipeline design will surface, because the two tickets are attached to what HubSpot believes are two different people. Fix both ends: merge the contacts, and merge the tickets automatically.