Ticket escalation to manager when SLA time-to-close is breached
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Service Hub Professional.
Per-hub plans: also Marketing Hub Professional
On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.
When to use it, when not to
Use it
- Use it when tickets regularly age past their resolution target and no one is watching for it until a customer complains.
- Use it as the second stage after the first-response breach alert (tickets-sla-003); this one targets the close-time target, which is usually a longer window.
Read more on when to use itShow less
Skip it
- Do not use it on pipelines without SLA targets configured; there is nothing for it to branch on, see Prerequisites.
- Do not use it as a substitute for the reopen-limit escalation (tickets-sla-040); that one tracks a different failure mode (repeated reopens), not simple aging.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Tickets and SLA
50 specs in this section
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Tickets and SLA spec