Skip to content
Tutorials Center
My learning

Topics

Lesson 19 of 37 ยท Service Hub

Service Hub: Tickets, Pipelines and Statuses

Learn how HubSpot Service Hub models support work: tickets, ticket pipelines, statuses, priorities, ownership and associations, with a runnable ticket-flow simulator.

Service Hub is the part of HubSpot built for the people who keep customers happy after the sale. Its core object is the ticket: one customer problem or request that needs tracking until it is solved. Tickets live in the same CRM as contacts, companies and deals, so a support agent sees the whole relationship, and a salesperson can see that their biggest customer has three open problems.

HubSpot is a hosted product and cannot run on this site. This lesson describes menus and behavior from the product as you use it; the code blocks are small stand-ins written in Python that model the same ideas. Plan names and limits change, so check your own account for what is included.

What a ticket contains

Open Service > Tickets (the exact menu name can differ slightly by account) and create a ticket. The main default properties are:

  • Ticket name and Ticket description: what the customer reported.
  • Pipeline and Ticket status: where the ticket is in your process.
  • Priority: low, medium, high (you can edit the options).
  • Source: email, chat, phone, form.
  • Ticket owner: the agent responsible.
  • Create date, Last activity date, Time to close.

A ticket is associated with a contact (who asked), usually a company, and sometimes a deal. Every email, call note and chat message about it is logged on the ticket timeline.

Pipelines and statuses

Just like deals have a pipeline with stages, tickets have a ticket pipeline with statuses. The default pipeline is typically New, Waiting on contact, Waiting on us, Closed. You change them under Settings > Objects > Tickets > Pipelines. Every status has a ticket state of Open or Closed, which drives reports such as "open tickets by owner".

Life of a ticket

New Created from email, form or chat
Waiting on contact Agent asked a question
Waiting on us Customer replied
Closed Solved, state = closed

Each status is Open or Closed

1 / 2

You can have several ticket pipelines, for instance one for Technical support and one for Billing, each with its own statuses and automation. Keep them short: five statuses or fewer is easier to report on.

Where tickets come from

Tickets can be created manually, from a connected shared inbox when a customer emails your support address, from a chat conversation, from a form (a "Contact support" form can create a ticket directly), by a workflow, or through the API. In the conversations inbox an agent can convert a thread into a ticket with one click, and replies continue to flow into the same record.

Modeling a pipeline

The next block is a stand-in: a tiny ticket pipeline that only allows legal status changes and records how long each ticket stays open. It mirrors how closing a ticket sets a close date in HubSpot.

Python A ticket pipeline stand-in

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Real HubSpot lets any user with permission move a ticket to any status, so treat the stand-in's strict rules as a design you could enforce with a workflow that reverts or flags unusual jumps (see workflow triggers and actions).

Views, ownership and routing

The ticket index page offers saved views such as "My open tickets", "Unassigned", and "High priority". Build them with filters on ticket state, owner and priority. For routing, a workflow can rotate new tickets between agents or assign them by a property such as product line; see sequences and rotation.

Python Filter views like HubSpot saved views

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Good habits

  • Write a clear ticket name convention (for example "Product: symptom").
  • Require the customer's contact association so history is never lost.
  • Close tickets with a reason property so you can report on common causes.
  • Use the Waiting on contact status to pause service-level clocks (next lesson).
  • Do not create a new pipeline for every team opinion; fewer pipelines make reports trustworthy.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. What is a HubSpot ticket?

    Tickets are CRM objects for support requests, associated with contacts and companies.
  2. 2. What decides whether a ticket status counts as open or closed in reports?

    Each status in a ticket pipeline is configured as Open or Closed.
  3. 3. Which is NOT a normal way to create a ticket?

    Editing a deal property does not create a ticket by itself, although a workflow could be built to do so.

Summary

  • Tickets are CRM records for customer issues, associated with contacts, companies and deals.
  • Ticket pipelines have statuses, each marked open or closed.
  • Tickets come from email, chat, forms, workflows and the API.
  • Saved views and routing keep work visible and evenly spread.
  • The Python code here is a labelled stand-in for the product's behavior.

Next: SLAs, Priorities and Escalation