HubSpot Service Hub Automation
HubSpot Service Hub automation runs on the same workflow engine as marketing, which is a genuine advantage and an occasional trap.
The HubSpot Service Hub automation worth building first
The advantage of shared automation
Because tickets, deals and contacts live in one system, a support workflow can read sales data without an integration. Escalating a ticket because the customer renews in thirty days is a one-step condition here and a project anywhere else.
That's the strongest practical reason to run support inside HubSpot rather than beside it.
Where the engine stops
A workflow evaluates one record at a time. There is no condition that says "another open ticket from this contact says the same thing", so duplicate detection can't be expressed here, in the same way it can't be expressed in Zendesk triggers or Freshdesk rules.
You can approximate it: notify when a contact has more than one open ticket. That flags the pattern for a human and catches only the same-contact case, which is the easy half.
Frequently asked questions
What HubSpot ticket automation can workflows actually do?
Create, route, escalate, chase and close. The HubSpot Service Hub customer support automation features are ticket-based workflows reading properties, and what they cannot do is compare two tickets with each other.
Can HubSpot workflows merge tickets?
No. Workflows act on one record, and merging is a decision about the relationship between two.
Which tier does HubSpot Service Hub automation need?
Professional and above for the useful ones. Starter automation is limited to simple actions.
The rule workflows can't express
Comparing every arriving ticket against the whole open queue is a different kind of job. Ticket Merger does it on Zendesk and Freshdesk today.
Start free trial14-day free trial. No credit card required.