Every request becomes a record you can manage
A ticket carries the details your support team needs to act, follow up, and report on resolution.
Status tracking
See where each request sits, from new to closed.
Clear ownership
Assign a single owner so nothing falls between agents.
Priority levels
Sort low, medium, high, and urgent so the right work surfaces first.
SLA timers
Track time to first response and time to close against your targets.
Linked context
Each ticket connects to the contact, company, and conversation behind it.
Custom fields
Capture product, region, or issue type to route and report more precisely.
A pipeline that mirrors how your team actually works
Tickets move through stages you define, so a request is never just open or closed. Teams running mixed channels such as email, web chat, and LINE can manage every request in the same pipeline.
- Build stages like New, Waiting on customer, In progress, and Closed
- Run separate pipelines for support, onboarding, and returns
- View tickets as a board or a list, filtered by owner or priority
- Drag a ticket between stages or let automation move it for you
How to set up ticketing in Service Hub
-
Connect your channelsLink your support email, chat, forms, and messaging apps so incoming requests reach a shared inbox.
-
Define your pipeline stagesMap the steps a request passes through, from first reply to resolution, and name them to match your process.
-
Set properties and priorityDecide which fields each ticket needs, such as priority, category, and product, and mark the ones agents must fill in.
-
Add routing and SLA rulesAutomate owner assignment, stage moves, and SLA targets so urgent work is escalated without manual sorting.
-
Report on resolutionBuild dashboards for open volume, response time, and time to close, then refine stages and rules as patterns emerge.
Build a connected support workflow
Tickets are one part of Service Hub, which gives your team the tools to capture, route, and resolve requests in one place.
