Round-robin routing that respects business hours for SLA timing
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.
8 stepsPer-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.
OutcomeTickets still rotate evenly across a queue's rep pool, but the rotation and its timestamp only count against the team during business hours, so a ticket that lands overnight does not make the SLA clock look broken by 8 a.m.
Workflow maptickets-sla-017
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 the plain round-robin from tickets-sla-001 is working and the next problem is overnight or weekend tickets skewing SLA numbers...or waking no one up for nothing.
Use it when a business hours schedule is already defined for the
team (Settings >...Objects or the Help Desk SLA business hours
configuration, whichever your portal exposes).
Read more on when to use itShow less
Skip it
Do not use it if the support team genuinely covers 24/7; there is no
"off hours" to protect against and tickets-sla-001 alone is enough.
Do not use it as a substitute for a real on-call path if some
tickets do need an immediate overnight response; pair it with
tickets-sla-023 for that case.