How to Create a Ticket in HubSpot
How to create a ticket in HubSpot has four answers, and they aren't interchangeable. Which one you use decides how much the ticket already knows about itself.
How to create a ticket in HubSpot: the short answer
Manually from the tickets index or a contact record. Automatically from a connected email or chat channel. From a support form that maps fields to ticket properties. Or programmatically through the CRM API.
The interesting question isn't how. It's which properties on the ticket record are populated at the moment of creation, because routing and automation can only read what's already there. A ticket created with nothing but a subject line is a ticket a human has to triage.
Manually
Go to the tickets index or open the contact and create a ticket from their record. Fill in the name, pick the pipeline and stage, set the owner, add whatever properties you require, and save.
Creating from the contact record is the better habit, because the contact association is made for you. Creating from the index and then hunting for the right contact is how tickets end up attached to the wrong person or to nobody at all.
Use manual creation for phone calls, corridor requests, and anything that arrived through a channel you have not connected. It should be a small slice of your volume. If it's a large slice, you have an unconnected channel.
From an email or chat
This is where most tickets should come from. Connect the support address as a channel in the conversations inbox, then set that channel to create a ticket for new conversations.
A few things that catch people out:
From a form
A support form that writes to ticket properties is the highest quality intake available to you, because the customer does the categorisation.
Map a dropdown to your category property, a dropdown to product area if you have one, and let the email field resolve the contact. Now your routing workflow has something real to read at creation, rather than an empty field and a fallback team.
The trade-off is honest and unavoidable: every extra required field costs you completed submissions. Three fields plus a description is usually the ceiling. Anything you can infer from the channel or the contact record, infer, don't ask.
The best ticket is the one that arrives already knowing what it's about. Forms are the only intake where you get that for free.
Through the API
For product-side ticket creation: an in-app support widget, an alerting system, a migration, or another tool that needs to open work in HubSpot.
Broad shape: authenticate with a private app access token scoped to tickets, post to the tickets object endpoint with your properties, then create the association to the contact. Batch endpoints exist for volume, and you should use them rather than looping single calls.
Two rules learned the hard way. Set the contact association in the same operation, otherwise you create orphan tickets that never appear in a customer history. And make your integration idempotent, because a retry after a timeout is the single most common way an API integration manufactures duplicate tickets.
Which method, when
One anti-pattern worth naming: offering a form and an email address for the same request type, with no connection between them. Customers use both, often within the same hour, and you get two tickets for one problem.
Frequently asked questions
How do you add a ticket in HubSpot manually?
From the tickets index, choose Create ticket, then set the pipeline, stage and owner. A HubSpot new ticket created this way starts with no contact attached, so associate it before you save or the history is orphaned.
How do you create a ticket in HubSpot from an email?
Yes. Connect the address as a channel in the conversations inbox and enable ticket creation for that channel. New conversations then open tickets automatically.
Can customers create their own tickets in HubSpot?
Yes, through a support form, chat, or the customer portal on the tiers that include it. A form gives you the most usable data at creation.
Why is my ticket not associated with a contact?
Usually because it was created from the tickets index rather than the contact record, or because an API call created the ticket without adding the association. Create from the record where you can.
Can I bulk create tickets in HubSpot?
Through import or the batch API endpoints, yes. Bulk creation is also the fastest way to fill a queue with duplicates, so deduplicate the source data first.
Four ways in, one problem twice
When a customer uses the form and then emails you, you get two tickets. Ticket Merger spots and merges those on Zendesk and Freshdesk today, and HubSpot is on the roadmap.
Start free trial14-day free trial. No credit card required.