What This Update Actually Is
Until now, HubSpot gave you exactly two built-in ticket automation emails: Ticket Received and Ticket Closed. That was it. If your support workflow branched into multiple paths, escalated to different queues, or needed a status update like "Waiting On Customer," you had to work around those limits or stitch together workarounds.
This update removes that ceiling. You can now create as many custom ticket automation emails as your workflows require. These emails live inside Service Hub, get built in a drag-and-drop editor, and can be sent to any contact, including non-marketing contacts and contacts not subscribed to a marketing list. That last part matters a lot for support teams.
The feature ships as part of Service Hub at no additional cost. It's available today on Service Hub Professional and Enterprise.
Why HubSpot Shipped This
Support workflows don't fit in two buckets. Real ticket pipelines have branches. A billing issue goes one way. A technical escalation goes another. A ticket that's stalled waiting on a customer response deserves its own message, not silence.
The internal frustration was real. Support leaders knew what they wanted to communicate at each stage. But the tooling forced them to either send the wrong message or build brittle workarounds using marketing email sends that weren't really built for transactional support flows.
HubSpot also had a language gap. Companies serving customers in multiple regions couldn't send localized ticket emails without significant technical debt. Now they can build the same workflow with different email branches per language, all managed inside Service Hub.
How to Use It Step by Step
- Navigate to Settings, then Objects, then Tickets, then Pipelines, then Automate.
- Scroll down to "Create Workflows from Scratch" to open the ticket-based workflow builder.
- Add or edit a Send Email action inside any ticket-based workflow.
- In the email selector, choose to use an existing ticket email, edit an existing one, or click "Create new email."
- A drag-and-drop editor opens. Build your email here, same interface you already know.
- Fill in all four required fields: subject line, from name, from address, and email body. All four are required before the email can be published.
- Publish the email and wire it to the correct workflow branch. Repeat for each status, branch, or language variant you need.
One important note: these emails bypass marketing subscription requirements. That means they'll reach non-marketing contacts and unsubscribed contacts. Use that power carefully. These are transactional support communications, not a back door for marketing sends.
What It Touches in Your HubSpot Strategy
This update isn't just a Service Hub convenience. It ripples into several parts of a well-built HubSpot portal, and it's worth mapping those out before you start building.
Ticket pipelines become more strategic. Each stage of your pipeline can now carry a purpose-built communication. That changes how you should think about pipeline design. Stages that previously felt like internal-only tracking steps now become customer touchpoints.
Key Takeaway
Every ticket pipeline stage is now a potential customer communication moment. Review your pipeline structure before building new emails so your stages and messages stay aligned.
Workflow branching gets real mileage here. You can build an if/then branch that sends a "Waiting On Customer" message when a ticket status changes to that value, sends an escalation notice when priority flips to high, and sends a language-specific close message based on a contact property. That's a genuinely different level of communication precision than the old two-email model.
Contact data quality matters more now. If you're branching workflows based on contact properties (like preferred language or region), those properties need to be clean. Messy data means the wrong humans get the wrong message. If you haven't run a recent portal audit, that's the right place to start.
Our complete HubSpot portal audit checklist covers ticket pipeline structure, workflow logic, and contact property hygiene in one pass. It's a good companion resource as you build out these new email branches.
Email deliverability deserves attention too. Because these emails reach non-marketing contacts, your from address reputation carries extra weight. A spike in sends to cold or unengaged contacts can affect your domain health.
If your portal sends high volumes, pair this with intentional sending practices. We covered related deliverability thinking in our breakdown of HubSpot's email throttle controls, which is worth reading alongside this update.
Key Takeaway
Ticket automation emails reach non-marketing contacts and bypass subscription filters. Treat them as transactional communications and document when and why each email fires, so your team stays compliant and your domain stays healthy.
Who Should Care Most
Not every HubSpot update hits every team the same way. Here's who should move on this one quickly.
- Support managers running multi-stage ticket pipelines who've wanted stage-specific customer communication but had no clean way to do it.
- RevOps and HubSpot admins who design workflow logic and have been patching ticket comms with workarounds inside marketing email tools.
- Companies serving multilingual customer bases where a single Ticket Received message in English wasn't serving their full audience.
- B2B teams with long support cycles where humans need regular status updates to feel informed without having to chase your team for answers.
- Service Hub Pro and Enterprise subscribers who've been paying for the tier but still relying on manual email sends for ticket status updates.
If you're on Service Hub Starter or Free, this update isn't available yet. The feature requires Professional or Enterprise.
George's Take
I've been inside hundreds of HubSpot portals, and one of the most common service gaps I see is the moment between "we got your ticket" and "here's your answer." That middle stretch is where trust erodes. Humans don't mind waiting if they feel informed. They mind silence. What HubSpot just shipped closes that silence gap in a way that actually fits how real support workflows are built, with branches, escalations, status changes, and multiple languages. This isn't a minor feature flag. It's the kind of update that makes Service Hub behave like the serious support platform it's been trying to become.
“The gap between 'we got your ticket' and 'here's your answer' is where trust erodes. Custom ticket automation messages let you fill that silence with the right words at the right moment.”
The most important next step is connecting your ticket pipeline stages to your contact data intentionally. The teams that flourish with this update will be the ones who've already thought about how service data connects to the rest of the CRM. If you haven't explored how shared data across HubSpot hubs becomes a real business advantage, that article will give you the strategic foundation to make this update count.
If you want help mapping your ticket pipeline stages to a communication strategy, or you want a second set of eyes on your existing Service Hub workflows before you build on top of them, let's talk. Book a strategy call with the Sidekick team and we'll show you exactly where to start.
Frequently Asked Questions
What are custom ticket automation messages in HubSpot?
Custom ticket automation messages are emails you build inside HubSpot Service Hub for use in ticket-based workflows. Unlike the default Ticket Received and Ticket Closed emails, you can create as many as you need for any workflow branch, ticket status, or language. They're available on Service Hub Professional and Enterprise.
Can custom ticket emails be sent to non-marketing contacts?
Yes. Custom ticket automation emails bypass marketing subscription requirements, which means they can be sent to non-marketing contacts and contacts not subscribed to any marketing list. This makes them suitable for transactional support communications, but it also means you should use them carefully and document their purpose.
Where do I find the custom ticket email builder in HubSpot?
Go to Settings, then Objects, then Tickets, then Pipelines, then Automate. Scroll to "Create Workflows from Scratch," then add or edit a Send Email action in any ticket-based workflow. From there you can select an existing email, edit one, or create a new one using the drag-and-drop editor.
What information is required to publish a custom ticket automation email?
HubSpot requires four fields before a custom ticket email can be published: subject line, from name, from address, and email body. All four must be completed. Once published, the email becomes available to select inside any ticket-based workflow Send Email action.
Which HubSpot tiers include custom ticket automation messages?
Custom ticket automation messages are available on Service Hub Professional and Service Hub Enterprise. They're not available on Service Hub Starter or Free. The feature is included in your existing Service Hub subscription with no additional cost.
How is this different from regular HubSpot marketing emails?
Ticket automation emails are designed for support workflows, not marketing campaigns. They can reach contacts regardless of marketing subscription status, they live inside the Service Hub ticket pipeline settings, and they're triggered by ticket workflow actions. Marketing emails require opt-in and are managed in the Marketing Hub email tool.
