A support pipeline should make the next action clear. A ticket waiting for a customer, a ticket waiting for a specialist and an unassigned ticket require different follow-up, even if all three are “open.”
Design the service promise before configuring stages. Identify the request types, responsible teams, working hours and escalation paths. Then choose the fields and statuses that help people deliver that promise.
Separate status, priority and ownership
Status describes the state of work. Priority describes urgency under an agreed definition. Owner identifies who is accountable for the next action. If all three are encoded in a stage name, routing and reporting become difficult to maintain.
Split pipelines when the work genuinely follows different steps. Language or customer tier alone may be better represented by properties and routing rules. Validate this against permissions, operating requirements and the features available in your account.
Example: a ticket waiting for another team
Illustrative scenario: a customer reports a billing discrepancy. Support acknowledges the request, but finance must confirm the correction.
| Decision | Operating rule | Check |
|---|---|---|
| Customer communication | A named support owner keeps the customer informed. | An internal escalation does not leave the customer without an owner. |
| Internal dependency | Finance receives a request with the reference and evidence needed. | The receiving team can act without reconstructing the conversation. |
| Waiting state | Track the dependency and next review time. | Waiting tickets appear in a follow-up queue. |
| Closure | Record the correction and communicate the outcome. | Resolution type and customer-facing response are captured. |
Configure SLA rules deliberately
HubSpot documents first-reply, next-reply and close-time goals, scheduling options and pause behavior in its help desk SLA guide. Check the subscription requirements and how the selected rules apply to the relevant tickets.
A status named “Waiting on customer” does not itself prove that a timer pauses. Test the actual configuration, including business hours, priority changes, reopening and transfers between teams. An internal dependency should not automatically suspend a customer commitment.
Check when the rule is selected. HubSpot’s SLA documentation states that the applicable rule is determined when the SLA is applied; later changes to the ticket or associated properties do not re-evaluate that rule. If priority changes after intake, document how the team handles the new commitment instead of assuming the timer follows automatically.
Make routing failures visible
Routing needs a fallback for missing language, an unknown product, an unavailable team or an incomplete customer record. Assign an exception queue and review it. A ticket should never look assigned merely because an automation ran.
Test both the expected recipient and the absence of one. Include cases where the ticket category changes after the initial assignment.
Use reporting to improve the service
- Backlog: open work by owner, category and age.
- Commitment risk: tickets nearing or exceeding the applicable SLA.
- Reopens: issues returned after resolution, using an agreed definition.
- Root causes: recurring product, billing or process problems.
- Handoffs: time spent waiting for an internal or external dependency.
Sample the underlying tickets with the team before interpreting a trend. A change in categorization or working-hours settings can change the report without changing the customer experience.
Continue with workflow design and ownership or reporting definitions.
Make support commitments visible.
I can help structure ticket pipelines, routing, SLA rules, exception queues and reporting around the way your service team works.
Explore CRM architecture →