Hi @RevOpsNinja
You’re right on both points:
- The Help Desk / ticket routing can natively “skip unavailable users”.
- The same availability concept is not exposed to lead/contact‑based workflows today, so you can’t natively say “round robin only among users who are available” in a contact workflow.
So, within standard HubSpot:
-
Contact / lead workflows
- The “Rotate owner” / “Assign record” actions don’t have a “only assign to available users” toggle like the ticket action does.
- There’s no way in these workflows to query the Help Desk user status (Available/Unavailable) or calendar‑based availability before assignment.
- That means your current “remove from workflow when on vacation” approach is unfortunately the limit of what’s possible purely with native lead workflows.
-
Where availability is supported natively
- Help Desk ticket routing: you can enable “Assign only to available users” on the ticket assignment action, which automatically excludes users marked Unavailable and respects their working hours.
- Meeting links (round‑robin / group meetings) also respect calendar availability, but that’s about booking time, not routing ownership.
-
Workarounds / alternatives
None of these are perfect, but they avoid editing a giant routing workflow for every vacation:
A. Use teams as the stable unit and manage membership
- Instead of listing 30 individual users in your routing logic, route to 2–4 “routing teams” and manage who’s in those teams when people go on vacation (in Users & Teams).
- You still don’t get availability‑aware routing, but the operational pain moves from “editing complex workflow branches” to “moving users in/out of teams”, which is safer.
B. Use an app that brings availability into workflows
- There are marketplace apps specifically for “Smart Lead & Ticket Routing for Workflows” that can:
- Build a rotation from selected users/teams
- Skip unavailable users based on their calendars or status (search for “Smart Lead & Ticket Routing for Workflows” inside the marketplace)
- These typically expose a workflow action you call from your lead workflow; the app decides who is available and returns the right owner.
C. Calendar‑driven process outside HubSpot
- Some teams push lead routing into a scheduling or external routing tool (similar to how round‑robin meeting scheduling uses availability) and then write the chosen owner back to HubSpot via integration or API.
- Your lead workflow then simply assigns the contact to the owner chosen by that external system (e.g., from a custom “Assigned owner (external)” property).
Regards