Mastering Hubspot Default Ticket Properties
Hubspot provides a powerful set of default ticket properties that help you organize support requests, standardize your pipeline, and report on customer service performance without complex setup. Understanding how these built-in fields work is the key to creating a clean, scalable help desk in your CRM.
This guide explains each major default ticket property, how it behaves in Hubspot, and how to use these properties to build effective views, automation, and reports.
Why Hubspot Default Ticket Properties Matter
Before customizing anything, it is important to understand what Hubspot gives you out of the box. Default ticket properties:
- Define the core structure of your support pipeline
- Ensure consistency across all tickets
- Feed dashboards and standard reports
- Power automation, SLAs, and routing rules
Because many of these properties are tied to system behavior, they cannot be edited or deleted. Instead, you configure your processes to work with them.
Core Identity and Tracking Properties in Hubspot Tickets
Every ticket in Hubspot is uniquely identified and tracked. Several default properties support this function.
Hubspot Ticket ID and Name
- Ticket ID: A unique numeric identifier automatically assigned to every ticket. It is read-only and ideal for referencing specific cases in integrations or reports.
- Ticket name: A human-readable subject line or title of the request. Agents use this in boards, lists, and inbox views to quickly understand the issue.
Use the ticket name to capture the essence of the request, while relying on the ticket ID for precise technical referencing.
Hubspot Create Date and Update Date
- Create date: Timestamp when the ticket was created in the CRM. Used in time-based reporting, SLA tracking, and historical analysis.
- Last activity date: Updated when tracked activities are logged on the ticket.
- Last modified date: Captures when a ticket property was last updated.
These default timestamps let Hubspot calculate durations such as time to close or time in pipeline stages.
Hubspot Ticket Status and Pipeline Properties
Tickets progress through a pipeline powered by a set of default properties that determine where they sit in your process.
Hubspot Ticket Pipeline
The Ticket pipeline property defines which pipeline the ticket belongs to when you use multiple support flows, such as:
- General support
- Technical support
- Onboarding or implementation
- Customer success escalations
You can create additional pipelines, but the property itself is system-defined. Reports and views often filter by this property to separate different service teams.
Hubspot Ticket Status
The Ticket status property tracks the stage of each ticket within its pipeline. Common default statuses include:
- New or Open
- Waiting on contact
- In progress
- Closed
Each pipeline can have its own set of stages, but the status property remains the core field used by Hubspot to show progress, trigger workflows, and measure resolution metrics.
Time in Ticket Status
Hubspot automatically tracks how long a ticket stays in each stage through duration properties, which can be used to:
- Monitor bottlenecks where tickets stay too long
- Validate SLAs based on time in specific statuses
- Drive escalations when thresholds are exceeded
Use these duration fields in reports to understand where tickets slow down and how process changes affect handling times.
Ownership and Responsibility in Hubspot Tickets
Ownership properties ensure every ticket has a clear responsible person or team inside Hubspot.
Hubspot Ticket Owner
The Ticket owner property assigns the ticket to an individual user. It helps you:
- Route incoming tickets to the right person
- Filter views by specific agents
- Analyze performance per owner
Workflows can automatically set this default property based on form fields, conversation channel, or ticket subject.
Team and Assignment Properties
Depending on your account, tickets can also be associated with teams. This allows managers to see all tickets for their group and balance workloads. Assignment logic can be configured based on:
- Round-robin rules
- Priority fields
- Ticket pipeline or source
Ownership properties are central to how Hubspot distributes and tracks work across your service organization.
Customer Context Properties in Hubspot Tickets
Default ticket properties connect each case to contacts, companies, and relevant context so you can see the full customer picture inside Hubspot.
Associated Records
Tickets are linked to:
- Contacts: The person requesting support
- Companies: The organization associated with the contact
- Deals: Related opportunities or subscriptions
These associations power reporting and make it easy to see all tickets related to a given account or opportunity.
Source and Channel Properties
Hubspot also includes properties that describe how a ticket was created, such as:
- Source channel (form, email, chat, API)
- Connected inbox or team
- Conversation thread details
These defaults allow you to understand which channels drive the most volume and how different sources perform in terms of response and resolution times.
Service Quality and SLA Properties in Hubspot
To measure service quality, Hubspot provides default ticket properties that track service times and outcomes.
Time to Close and Resolution Metrics
Key properties may include:
- Time to close: Duration from ticket creation to closed status
- First response time (when enabled via tools and tracking)
- Other time-based SLA indicators
Combine these fields with ticket status and owner to build powerful reports and dashboards in Hubspot.
Customer Feedback Associations
When using surveys or feedback tools, tickets can be linked to customer satisfaction scores. This allows you to:
- Track which ticket types lead to poor satisfaction
- Identify agents or teams that need support
- Refine processes to improve outcomes
How to Use Hubspot Default Ticket Properties Effectively
Because default fields are deeply integrated into the platform, using them correctly makes your entire support system more reliable.
Step 1: Review Hubspot Ticket Property Definitions
- Open your Hubspot account settings.
- Navigate to Data management and then Properties.
- Filter by the Ticket object.
- Locate the default properties described in the official documentation at Hubspot’s default ticket properties.
Note which fields are read-only and which can be edited for labeling or display.
Step 2: Align Pipelines and Statuses in Hubspot
- Map your current support process on paper.
- Match each stage to a ticket status in your pipeline.
- Configure the pipeline stages using the built-in status property rather than creating redundant custom fields.
- Enable duration tracking and reporting for critical stages.
This ensures that every report in Hubspot uses a consistent definition of ticket progress.
Step 3: Standardize Ticket Creation and Forms
- Review all forms or channels that can create tickets.
- Map important form fields to existing default ticket properties where possible.
- Use workflows to set pipeline, owner, and status automatically.
- Keep custom fields to a minimum and only when a default property cannot be reused.
Relying on default properties keeps your data clean and easier to maintain over time.
Step 4: Build Views and Reports Using Hubspot Defaults
- Create ticket views for agents based on ticket status, owner, and pipeline.
- Design dashboards that use time-based properties such as create date and time in stage.
- Filter by source and channel properties to optimize your support mix.
- Combine ticket properties with contact and company properties for deeper analysis.
Using the standard property set maximizes the value of built-in Hubspot reporting tools.
Best Practices for Managing Ticket Properties in Hubspot
- Document how each default property is used in your process.
- Train agents to update only the most important fields consistently.
- Audit ticket property usage regularly to keep data clean.
- Limit new custom properties and prefer reusing defaults.
For additional strategic guidance on structuring your CRM and service processes, you can review consulting resources at Consultevo.
Next Steps: Deepening Your Hubspot Ticket Setup
Once you are familiar with the default ticket properties in Hubspot, you can extend your setup with automation, custom properties where truly needed, and advanced dashboards. Start by reviewing the full list and descriptions in the official documentation and then design your pipeline, forms, and workflows to align with these built-in fields for a scalable, reliable support operation.
Need Help With Hubspot?
If you want expert help building, automating, or scaling your Hubspot , work with ConsultEvo, a team who has a decade of Hubspot experience.
“`
