Escalate automatically when a company has 3 or more open tickets at once

Outcome. A company juggling several open tickets at the same time gets flagged as a pattern worth a manager's attention, instead of three separate reps each working their own ticket with no view of the bigger picture.

Workflow map Enrollment, branches and actions at a glance tickets-sla-040

flowchart TD
    A[Ticket created] --> B[Companion workflow A: increment open_ticket_count]
    B --> C{open_ticket_count >= 3?}
    C -->|yes, first time crossing| D[Alert escalation contact, add to review list, create task]
    C -->|no| E[No action]
    F[Ticket closed] --> G[Companion workflow B: decrement open_ticket_count]

When to use it, when not to

• UseUse it when multiple simultaneous open tickets from one account usually signals something bigger than three coincidental issues, a rollout problem, a systemic bug, or an account close to escalating a complaint.
• UseUse it when reps do not naturally see other open tickets on the same company unless they think to check the association panel; this workflow surfaces that pattern without relying on someone noticing.
• SkipDo not use it for companies with naturally high ticket volume as part of normal usage (a large account with many active users generating routine tickets); tune the threshold higher for those, or exclude them via a suppression list, or the escalation fires constantly and gets ignored.
• SkipDo not use it if HubSpot's own reporting already gives your team a live dashboard of open-ticket-count by company that people actually check; this workflow adds a push notification on top of that, which is only useful if the pull-based report is not enough on its own.