Combined priority matrix: severity property plus account tier property
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.
OutcomeTicket priority is set from two signals at once, how bad the issue is and how significant the account is, instead of a single property doing double duty and getting it wrong for either a minor issue at a big account or a critical issue at a small one.
Workflow maptickets-sla-025
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
When to use it, when not to
Use it
- Use it once severity and account tier are both reliably captured before or at ticket creation, and a single "priority" value set from severity alone (tickets-sla-002) is not distinguishing enough between accounts.
- Use it when the business genuinely wants enterprise accounts to get a priority bump over an otherwise-identical issue at a smaller account, and that policy is explicit, not assumed.
Read more on when to use itShow less
Skip it
- Do not use it if severity alone already captures everything that matters; adding account tier only makes sense if account size is a deliberate part of your service policy.
- Do not use it if severity is not reliably set at intake; a matrix built on a mostly-blank input column produces mostly-default priority values.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
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