Skip to content
The Workflow Library
Get the full library

Approval-style gate before closing a high-priority ticket (property-based workaround)

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.

Ticket3 stepsUpdated for HubSpot seat pricing
OutcomeA high-priority ticket cannot look finished to the team without a manager's explicit sign-off recorded on the record, using a property gate rather than a native approval mechanism that does not exist for tickets.
Workflow maptickets-sla-047
Ticket reaches Ready to close, High/Urgent priority leads to Set manager_approval = requested. Set manager_approval = requested leads to Notify manager, create review task. Notify manager, create review task leads to Manager manually reviews. Manager manually reviews leads to approves: Sets manager_approval = approved; rejects: Sets manager_approval = rejected. Sets manager_approval = approved leads to Native stage requirement configured?. Native stage requirement configured? leads to yes: Ticket can now move to Closed; no, VERIFY: Nothing actually stops manual closure without this, workaround only. Sets manager_approval = rejected leads to Notify owner, move ticket back to active work. approves yes no rejects Ticket reaches Ready to close, High/Urgent priority Set manager_approval = requested Notify manager, create review task Manager manually reviews Sets manager_approval = approved Sets manager_approval = rejected Native stage requirement configured? Notify owner, move ticket back to active work Ticket can now move to Closed Nothing actually stops manual closure without this, workaround only
Ticket reaches Ready to close, High/Urgent priority leads to Set manager_approval = requested. Set manager_approval = requested leads to Notify manager, create review task. Notify manager, create review task leads to Manager manually reviews. Manager manually reviews leads to approves: Sets manager_approval = approved; rejects: Sets manager_approval = rejected. Sets manager_approval = approved leads to Native stage requirement configured?. Native stage requirement configured? leads to yes: Ticket can now move to Closed; no, VERIFY: Nothing actually stops manual closure without this, workaround only. Sets manager_approval = rejected leads to Notify owner, move ticket back to active work. approves yes no rejects Ticket reaches Ready to close, High/Urgent priority Set manager_approval = requested Notify manager, create review task Manager manually reviews Sets manager_approval = approved Native stage requirement configured? Ticket can now move to Closed Nothing actually stops manual closure without this, workaround only Sets manager_approval = rejected Notify owner, move ticket back to active work

When to use it, when not to

Use it

  • Use it when a manager wants to review high-stakes ticket resolutions before they close, but HubSpot has no native approval workflow for the ticket object; native approval workflows (the kind used for deal or quote approvals) live in a different part of the product and are not available for tickets at all (check in your portal: confirm current product scope for approval workflows, this fiche assumes there is no ticket-object equivalent).
  • Use it as a discipline layered on top of pipeline configuration: if your pipeline supports requiring specific properties to be set before a record can move into a given stage, that native stage requirement is the actual mechanism enforcing the gate, this workflow's job is to make requesting and recording that approval simple, not to invent the enforcement itself. Stage-specific required properties are configured per pipeline stage with the Required checkbox, on deal and ticket pipelines alike, with no separate tier gate beyond the pipeline itself (https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines).
Read more on when to use itShow less

Skip it

  • Do not use it expecting this workflow alone to block a rep from manually closing the ticket if no native stage requirement is configured; without that native enforcement, a rep can still close the ticket while this workflow's property sits unanswered, this is a workaround, not a hard block, say so plainly to the team before relying on it.
  • Do not use it for every ticket regardless of priority; reserve it for the priority levels where a manager's review before closure is genuinely worth the extra step, most teams will not want this friction on Low or Medium tickets.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 3 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Tickets and SLA spec

Not the workflow you needed?

More in Tickets and SLA

50 specs in this section

See all 50 This category, 39 EUR
FreeRound-robin ticket assignment by team/queueTicket12 steps SLA "Time to first response" breach alert to owner and managerTicket7 steps Routing based on association to an open enterprise dealTicket3 steps Ticket priority auto-set from source and keyword matchTicket8 steps

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.

149 EUR199

Full library, 565 specs
Get the full library