HubSpot will run a round robin for you with a single workflow action called Rotate record to owner, and you don't need a routing app to use it. You do need Sales Hub or Service Hub on Professional or Enterprise, which HubSpot lists at $90 a seat a month on annual billing, $100 on monthly, plus a one-time $1,500 onboarding fee for Professional.
The top results we read for this query came from two routing vendors and a HubSpot agency, so they spend most of their words on what native rotation can't do. The native action handles plain rotation fine. Where routing actually goes wrong is the record that already had an owner getting rotated anyway, or a lead that gets assigned and never called.
One workflow, built in this order
Start with two contact properties of your own: a dropdown called Routing status (new, routed, escalated) and a date picker called Routed at. They cost nothing, and they're how you'll find leads that slipped through later.
Then build one contact-based workflow. The enrollment trigger is whatever makes a lead worth a rep's time, usually a demo form submission or a lifecycle stage change to MQL, and add a filter for Contact owner is unknown so you don't touch records someone already owns. Turn on re-enrollment only if you mean it.
Inside it, the order matters more than the rotation settings.
- Branch on whether the associated company has an owner. If it does, copy the company owner to the contact and skip the rotation. Without it, a new contact from an account a rep has worked for a year goes to whoever is next in line.
- For everything else, add Rotate record to owner. Pick Specific users or a team, and tick Assign to available users only.
- After the rotation, set Routing status to routed, stamp Routed at with the enrollment date, create a call task due today for the new owner and send them an internal notification.
- Add a final branch for contacts that came out of the rotation with no owner, and send those to one named person.
You need step 4 because HubSpot's own documentation says that if nobody in the pool is eligible, or every user is set to Away, the record is left unassigned. With a named fallback person, those leads land in someone's queue instead of nowhere.
If you route the newer leads object instead of contacts (still marked beta in HubSpot's docs), the action gives you three distribution choices: round robin, load balanced (whoever has the fewest open assignments gets the next one) and random. We'd pick load balanced when reps work at very different speeds. To use leads you also have to switch off the setting that syncs lead owner with contact or company owner, which catches people out.
Where it quietly breaks
The rotation counter resets whenever you edit the pool. Per HubSpot's docs, when you add or remove a user after the workflow is on, the counts reset and new records are spread evenly across the current list as if nothing came before. So if you hire a rep mid-month, they don't get extra leads to catch up. Expect a lopsided month after any roster change and don't chase it as a bug.
People leave and nothing tells you. Deactivated users and anyone without a paid Sales or Service seat get a red border in the action and receive no assignments, according to HubSpot. That's the right behavior, but you only see it if you open the workflow. Put a check of the rotation pool on your offboarding list, or the pool shrinks and nobody clocks it. Away status has the same problem in reverse: it only works if the rep actually sets it before a week off.
Salesforce can undo your work. If your HubSpot owner field syncs to Salesforce, HubSpot's docs warn that Salesforce may push the previous owner back. Pick one system to own assignment and route there. If Salesforce is the system of record, do the routing in Salesforce.
There's a smaller one too. HubSpot notes that only one record moves through the action at a time and the rest retry, so a big list import can take a while to fan out. Don't route imports through the same workflow as live form fills.
The follow-up check matters more than the rotation
The rotation has no idea whether anyone called the lead. A second workflow that checks is worth more than any amount of tuning on the first.
Build it off Routing status is routed. Add a delay that matches the first-touch promise you actually make to reps, which in our view should be 15 minutes for demo requests. Then branch on Last activity date (or Last contacted) being unknown. If nobody has touched the lead, set Routing status to escalated and notify the rep's manager. We'd notify first and reassign at a second check an hour later, because reps who get leads pulled out from under them stop trusting the system.
Run a report on Routing status by owner every Monday. One rep sitting on far more escalated leads than the others is a coaching conversation, and the report gives you the numbers for it.
Starter teams, and when to buy a router
On Sales Hub Starter you don't get the workflow action, but you do get round robin meeting links. Per HubSpot's meetings docs, when several reps are free at the chosen time, the one who has gone longest without a meeting gets it, and you can tell it to show the contact owner's calendar first. The trap is that a rep with a disconnected calendar counts as always available, so check every rep's calendar connection before you put the link on your demo form. For a small team that only routes demo requests, this alone covers most of the job.
Buy a router like LeanData or Chili Piper when you need to match new leads to existing accounts by domain and your company records are a mess, or when Salesforce owns the record. Native HubSpot handles the first badly and the second not at all, and more branches won't fix either.
You also don't need to hire anyone to build this. With a handful of reps and one form, a sales manager who is comfortable in HubSpot can build both workflows from the docs. The time sink is the upkeep afterwards, as people join and leave the pool and somebody has to chase the escalations every week. That ongoing work is the case for a full-time admin, which we lay out in HubSpot admin or a HubSpot agency.
If your routing fits in three branches and lives entirely in HubSpot, build it native this week. If you need account matching across messy company data, or Salesforce owns the record, budget for a router and route there instead.