The Workflow Library

Library / Tickets and SLA / tickets-sla-033

Urgent-priority ticket alert to the account owner (CS or sales rep)

Tickets and SLATicketService Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. The rep who actually owns the account relationship, not just the support agent assigned the ticket, finds out the moment one of their accounts opens an urgent ticket.

Workflow map Enrollment, branches and actions at a glance tickets-sla-033
flowchart TD
    A[Ticket created or escalated to Urgent] --> B[Copy company owner to account_owner_copy]
    B --> C{account_owner_copy known?}
    C -->|yes| D[Notify account owner, create check-in task]
    C -->|no| E[Notify support ops, no account owner found]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the ticket owner (support rep) and the account owner (CS manager, AE, or CSM listed as the company's hubspot_owner_id) are routinely different people, and the account owner wants to know about urgent issues without living in the ticket queue.
  • UseUse it for renewal-risk visibility: an urgent ticket on an account nearing renewal is exactly the kind of thing a CSM should hear about immediately, not discover in a health score report days later.
  • SkipDo not use it if the ticket owner and the account owner are already the same person on your team structure; the notification would just duplicate what they already see.
  • SkipDo not use it for every priority level; this fiche targets Urgent specifically, pair with tickets-sla-009 if High-priority enterprise tickets also need account-owner visibility.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the tickets and sla pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.