Lead routing based on user availability

Smart CRM & Sales Hub Account & Settings
1

Hi All,

We currently have a fairly complex workflow that looks at various criteria and routes to different users based on the outcome. The issue is the team is quite large (~30) and so every time someone is on vacation, we have to actually go into this workflow to remove the user and then later go and add them back in. It’s quite tedious and also quite risky because this workflow handles all the routing.

So I was wondering if there’s a way to check for user availability before the round robin takes place.. I know in HelpDesk you can route based on availability but this is for the sales team so it’s not as straightforward..

Since it’s a lead based workflow I can’t seem to access the user object anyway so really not sure on how to proceed here.

Any help would be much appreciated! :blush:

2

Hey @RevOpsNinja - thanks for posting in the Community!
This is a really interesting use case, and I’d like to tag in some Community experts to see what insight they may have on best practices here. @danmoyle, @Josh, and @RomyFuchs1 - any thoughts on the best way to approach availability is when the team has a workflow routing conversations?
Shane, Senior Community Moderator

3

Thanks for that @STierney, appreciate it! Just to confirm, it’s not about routing conversations, but rather routing leads to the sales team. Really curious to hear back from the team! :slightly_smiling_face:

4

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:

  1. 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.

  2. 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.

  3. 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

5

Thanks so much for the detailed responses @RomyFuchs1 !!

So the teams option won’t really work because we have routing based on budget, geography and seniority built in where members of the same team get different kinds of leads.

Also I think adding and removing members from teams will be a problem because it’s going to impact forecasting and having reliable data is paramount.

Seems like the marketplace apps or the last solution, e.g. sending an API call to our HR tool and using the outcome to run the RR action might be the best best so we’ll look into those for now.

Any idea if HubSpot plans to release this feature in the near future? I’m sure 1000s of teams would be forever grateful! :grinning_face_with_smiling_eyes:

6

HI @RevOpsNinja

You’re absolutely not the only one asking for this – you’ve basically described the feature request word‑for‑word. :slightly_smiling_face:

From what’s publicly visible today:

  • There are multiple open ideas asking for exactly this:

None of these are tagged as planned/in beta/launched, and there’s no roadmap announcement that this is coming for contact/deal workflows. The only place availability is clearly wired into routing in product docs today is Help Desk ticket assignment and meeting scheduling, as we saw earlier, not lead owner rotation.

So as of now:

  • I can’t point you to an announced near‑term release for “rotate record / lead routing based on availability” for sales objects.
  • The official channel is exactly those Ideas posts – upvoting and adding your concrete use case there is what product uses for prioritisation. The three ideas I linked are already attracting comments from teams with your exact pain, which is a good sign but not a commitment.

Given you’re leaning toward marketplace or HR‑API routing:

  • Apps like “Smart Lead & Ticket Routing for Workflows” and similar solutions (e.g. Distributely, Insycle, etc.) explicitly advertise skipping unavailable users and using availability in routing logic, plugged into HubSpot workflows.
  • Your “ask HR via API, then run the RR” architecture is very much in line with how teams are solving this today when they need it to be robust.

Regards

7

Hi @RomyFuchs1 thanks again for the detailed responses!
Unfortunately the API approach isn’t workable within a HS workflow for us because the result of the request is the full list of available users and there’s no way to get the RR action to look at the list of users in the action AND the previous action with the available users.

An app seems to be the only way for now but again it seems like a very basic feature request and if it’s already in place for Helpdesk I can’t fathom why it’s such a big ask for sales hub? Would you have any insights into a release date for this much needed feature?
Best,
Venkat

8

Hi @RevOpsNinja
You’re absolutely right about the limitation with the API pattern in a native workflow:

  • The “Rotate record to owner” / assign actions can only see:
    • A static list of users and/or teams you configure in the action, not
    • A dynamic list coming from a previous step (like “these 7 are available right now” from an API call).

So you end up stuck: you can set an owner from an API response, but you can’t use HubSpot’s own round‑robin on a dynamic subset of users. That’s exactly the gap the routing apps try to fill.

On the “why is this so hard if Help Desk already has it?” and “when is it coming?”:

  1. What we can see publicly today

The closest signals we have are the Ideas threads we looked at:

  • “Add Availability status to User Based Workflows” – asks for availability to be reusable beyond Help Desk (user properties, reporting, automation). Status: Idea Submitted.
  • “Reference User ‘Working Hours’ in Lead Rotations (Record Rotation Workflow Step)” – explicitly asks to use working hours/availability in record rotation for leads, tasks, tickets, etc. Also Idea Submitted, not marked as In Planning/Delivered.
  • “Allow Contact Owner rotation based on Availability” – precisely your use case: rotate contact owner but skip people who are away instead of editing the rotation whenever someone goes on vacation. Also only Idea Submitted.

On the Community / Ideas board, HubSpot typically marks items as “In Planning”, “In Beta”, or “Delivered” when there’s a committed roadmap step or a rollout in progress. All three of these, as of the latest visible updates, are still at the initial “Submitted” stage, with no official timeline or status change.

There’s also no separate public product‑updates entry announcing “availability‑aware rotation for lead/contact/deal workflows”, only the Help Desk / availability docs we already saw.

  1. What that means for a release date

Based on the public signals:

  • There is clear demand and multiple converging ideas (which is good for prioritisation).
  • There is no public indication that:
    • It’s in active development for Sales Hub workflows, or
    • It has a planned release window.

I don’t have access to internal, non‑public roadmap details, so I can’t give you a private/earlier date than what product has shared externally. All I can honestly say is: as of what’s visible right now, there is no announced ETA for availability‑aware round robin on contacts/deals/leads.
Maybe @STierney have more information about it.

  1. What you can do that actually moves the needle

Since you clearly have a strong, real‑world use case (30‑person team, geo/budget/seniority routing, forecasting implications), that context is exactly what product managers look for:

  • Add your scenario to one or more of these ideas:
    • “Add Availability status to User Based Workflows”
    • “Reference User ‘Working Hours’ in Lead Rotations (Record Rotation Workflow Step)”
    • “Allow Contact Owner rotation based on Availability”
  • When you comment, call out:
    • You already use Help Desk availability for service, and you want the same concept applied to record rotation in sales workflows.
    • Why team membership hacks are not acceptable (impact on forecasting and reporting).
    • That 1:1 API‑based workarounds don’t work because the rotation step can’t consume a dynamic user subset.

That doesn’t magically create a date, but it does get your specific constraints in front of the right people and strengthens the case that this is more than a “nice‑to‑have”.

Regards

9

Thanks again @RomyFuchs !
@STierney would it be possible to get some feedback from the concerned PM on this thread regarding a releast date please?

10

Hi @RevOpsNinja,

I’m doing a little bit of research on these areas where HubSpot routing gets a bit brittle with things like availability, previous owner protection, and better debugging, and a search turned up this post which is one of the types of issues that I’m trying to understand. I don’t want to derail this thread, but I’m wondering if you’re open to a DM. I’d really value hearing about how you’re handling this specific situation now and what sorts of things can be improved.

11

Any updates on this?

12

Hey @RDeRosier7,
Thanks for following up here!
Outside of @RomyFuchs1’s recommendations, we’d recommend upvoting and expanding on the ideas linked in the accepted solutions. These are the forums where our Product team can directly review user feedback and needs. I’d also encourage you to expand on the ideas if you feel that any of those ideas are missing features you’d like to see!
Shane, Senior Community Moderator

13

Hey @RDeRosier7 Magdalena Georgieva from the HS product team said they’d likely launch the feature this quarter (probably April at this point). Hopefully it’ll be with the fallback option to assign it to a fixed user is no one in the round robin is available, otherwise leads would just go unassigned in our case. Fed this back to Magdalena already so hoping they have the complete solution rolled out in one go.

14

We would also really like this :raising_hands:. So we can route leads to people who are available now, and reduce our advertising spend wastage - which happens when leads are allocated to people in the round-robin who are on annual leave, or work a different time-zone.

Thanks!

15

Hi @RevOpsNinja,

This is a common issue in large sales teams. Manually removing and re-adding users in routing workflows is time-consuming and risky. Automating availability in lead routing is essential. Instead of editing the workflow every time, use a simple “available for routing” flag or group. The system then assigns leads only to active reps.

This keeps routing stable, reduces manual work, and ensures no leads go to unavailable users.

LeadAngel is the solution I tried for this, handling cases like PTO availability and its real-time lead handoff feature absolutely worked for me.

16

Hey! If you still have this problem - it is exactly the problem we built Inleado to solve. We have an “Away Mode” toggle on each team member - when someone goes on vacation, you just flip the switch and they’re automatically skipped in the round robin. No need to edit any workflows or routing rules. When they’re back, flip it off and they’re back in rotation. It works with any routing setup - conditional rules, round robin, individual assignment. The routing logic just skips anyone marked as away. Would be happy to show you how it works if you’re interested - takes about 2 minutes to set up. https://www.inleado.com/

17

Hey everyone- thanks so much for posting on here. I have recently taken over this product area and we are working on getting underway on strengthening our routing capabilities to the rest of the CRM. If folks are open to connecting on it, please reach out!

-Jordan

18

You are correct @RevOpsNinja HubSpot supports “assign only to available users” for Help Desk tickets, but that functionality isn’t available for contact or lead workflows.

With native HubSpot:

  • Lead/contact workflows can’t check whether a user is available before assigning ownership.
  • The Rotate record owner action doesn’t have an option to skip users who are out of office.
  • So, if you’re relying only on native workflows, updating the workflow when someone is on PTO is unfortunately one of the current limitations.

A few alternatives you could consider:

  • Route to teams instead of individual users. Managing team membership is generally safer than editing a large workflow every time someone is away.
  • Use a dedicated routing solution. Tools like LeadAngel, Chili Piper, or Distributely can handle more advanced routing logic, including rep availability or out-of-office scenarios, without requiring changes to your workflow each time.
  • Maintain a custom availability property. Some teams update an “Available” or “Out of Office” property and use that as part of their routing logic. It requires a bit of setup but helps reduce ongoing workflow edits.

For a team of around 30 users, try to keep rep availability separate from the workflow itself. It makes the routing much easier to maintain and reduces the risk of accidentally breaking a workflow that’s handling all of your lead assignments.

19

Hi @Jaron2 just wondering if this feature is scheduled into any of the upcoming sprints?

20

@SimranMakhija previous replies already cover these options. The Smart lead routing app is what we’re using now and it’s fantastic!