All functionality in Service Hub revolves around the ticket object. SLAs, health scores, and AI ultimately depend on whether tickets are designed correctly.If you start operating without properly designing the ticket structure, the cost of making adjustments later will snowball.. Building properties, defining pipeline stages, channel integration, prioritizing and categorizing, and linking to CRM are the starting points for a scalable support organization.
A ticket object in HubSpot is a unit of record that represents a single inquiry or support request from a customer. It is treated as a first-class CRM object like contacts, companies, and opportunities, soTicket data can be used for reporting, workflow, and AI analysis.. It is important to first understand the structure of ticket records and then design properties based on that.
Creating too many custom properties from the beginning increases the agent's input load and reduces data quality.Don't create properties that don't answer the question, "What should we judge using this data?". We recommend an approach that starts with three custom properties: ticket category, scope of influence, and reason for closure, and then adds whatever is necessary during operation.
A ticket pipeline is a "mechanism that visualizes the process by which a ticket is resolved." It has the same structure as the opportunity pipeline in Sales Hub, butThe design perspective is completely the opposite: business negotiations are based on the actions of the salesperson, but ticket pipelines are designed based on the state of the resolution process.. It is important to use a stage name that expresses ``the current state of the ticket'' rather than ``what the person in charge should do.''
| pipeline name | Purpose | Characteristics of stage configuration | Recommended organization |
|---|---|---|---|
| General support | General inquiries via email/chat | New → In charge → Waiting for customer → Resolved → Closed | Recommended for all organizations (default) |
| Technical support/bugs | Technical glitch/bug response involving the development team | Reception → Investigation → Development confirmation → Waiting for correction → Test → Solved | SaaS/tech product company |
| Onboarding | Process management for initial setup and implementation support for new customers | Kickoff → Setting support → Training → Acceptance inspection → Completion | Organizations where CS team is responsible for onboarding |
| Return/refund processing | Processing of EC/SaaS returns, refunds, and cancellation requests | Application received → Confirming → Approved → Processing completed | EC/Subscription business |
Without the "waiting for customer response" stage, the SLA count would continue to increase while waiting for a response, resulting in continuous SLA violations. In combination with the setting to pause the SLA when moving to this stage (possible in Professional and above),Accurately measure agent response speed. Setting up this stage is essential in order to distinguish between "the customer is slow" and "the agent is slow."
Customers have more than one way to contact support. Email, live chat, phone, form, SNS——Aggregate inquiries from all channels into your HubSpot inbox and automatically generate ticketsThis is the starting point for ``preventing missing data'' and ``centralizing data management.''
If the "Automatically create tickets" setting is turned off for a channel connected to your inbox, you won't be able to track your agent until they manually create a ticket.Setting location: Service → Inbox → Select channel → Create ticket → Turn on “Always create ticket”. This is the first setting you should check on all channels.
Priority, category, and tags are the mechanisms that determine who should respond to tickets, in what order, and how.If these are ambiguous, routing will not work, and SLA management and reporting will be less accurate.. When designing, it is important to narrow down the options with the top priority being that ``the agent inputting information will not be confused.''
| priority | Definition/applicable conditions | SLA guideline (first response) | SLA guideline (resolution) |
|---|---|---|---|
| Urgent | Failure in production environment, loss of sales, security incident, impact on all customers. Immediate escalation to management/CS manager required | Within 30 minutes | Within 4 hours |
| High | Problems with major functions, impact on some customers, and inability to process tasks with deadlines | Within 2 hours | 8 hours (during business hours) |
| Medium | Some functions cannot be used, manual workarounds are required, and non-essential functions are defective. | Within 4 hours | 24 hours (during business hours) |
| Low | Questions about how to use, feature requests, errors in documentation, and improvement suggestions that do not interfere with business operations. | within 8 hours | 72 hours (within business hours) |
Categories are an axis for ``categorizing types of inquiries.'' Used in reports to analyze ``which categories are the most common'' and ``which categories take the longest to resolve.''If there are too many categories, the input will become ambiguous, so start with no more than 7 to 10 categories.It is recommended that the
| Category name | Examples of applicable inquiries | Main team in charge |
|---|---|---|
| technical malfunction | Errors/bugs/API defects/malfunctions | technical support team |
| How-to | Breeze Customer Agent (hereinafter referred to as ``Customer Agent'') is an autonomous agent that uses AI to directly respond to customer inquiries. Browse learning sources such as knowledge bases, websites, PDFs, videos, etc. | General support team |
| Billing/Contract | Check your bill, change your contract, upgrade your plan | Account manager/CS |
| Onboarding | Initial setup support and initial training requests | CS team |
| Data/coordination | Data export/import/external tool linkage | technical support team |
| Feature request | New feature requests/improvement suggestions (feedback to product) | CS/Product Team |
| Security/Authorization | Access privileges/security incidents/login issues | Technical support (immediate escalation) |
By associating tickets with other CRM objects, Service Hub transforms from a ticket management tool to a customer understanding platform.When an agent opens the ticket screen, they can see the entire picture of the customer -- business negotiations, past tickets, health score, NPS -- on the same screen.is ideal.
| Automatic association method | How it works | Setting location |
|---|---|---|
| Automatic matching by email address | Tickets created from emails are automatically searched for and associated with existing contacts and companies based on the sender's email address. | Automatic (no settings required) |
| Form field mapping | By mapping the support form's "company name" and "email" fields to contact/company properties, they are automatically associated when created. | Form settings → Field mapping |
| Association by workflow | Automatically associate the contact's company with the ticket using the "When creating a ticket → Get the contact's company → Associate with the ticket" workflow | Workflow → Ticket Based → Association Action |
| Manual association with renewal opportunity | If the CS is in charge of the renewal opportunity, select the renewal opportunity from "Add association" on the ticket record and link it. Batch operations are also possible from the list view | Ticket record → Right panel → Add association |
HubSpot's default behavior is to associate tickets created from emails with contacts;Association to company is not automaticProgress confirmation emails such as "Did you receive the email I sent earlier?" will be significantly reduced. When a customer creates a ticket through the portal, the ticket is created with all the information from the form fields.
Creating many custom properties from the beginning increases the input load and reduces data quality. Start with the ticket category, scope of influence, and reason for closure, and stick to the principle of adding only "data that will be used to make decisions."
Use stage names that express “the current state of the ticket” rather than “what the person in charge should do.” Always include a “waiting for customer response” stage and combine it with a setting to pause the SLA.
Connecting to your inbox via email, chat, form, and WhatsApp, and enabling automatic ticket generation is the first step to preventing things from falling through the cracks. Since Urgent priority has been added since March 2025, the priority definition will also be maintained in four stages.
By sharing the definitions of Urgent (production failure/immediate escalation), High (major functional failure), Medium (workarounds available), and Low (questions/requests), the accuracy of SLA management and routing will be improved.
By default, it is associated with contacts but not automatically associated with companies. If you do not configure the Create Ticket → Get Contact's Company → Associate to Ticket workflow, company-level health score reports will be inaccurate.
By linking renewal deals and tickets, you can see how many support costs were incurred before this customer's renewal. CS can use support costs as a basis for making decisions on renewal negotiations and price revisions.