A lead fills out the demo form on a Tuesday afternoon. The workflow rotates it to the next rep in line. That rep is on vacation. The account it came from already belongs to a different rep, who has been working the CFO for two months. By Friday, two of your people have emailed the same company, and the one who should have gotten the lead finds out from the prospect.
The workflow did exactly what it was told. Nobody told it enough.
HubSpot lead routing is not hard to switch on. The rotate action takes a few minutes to set up. What takes thought is the order of the rules, the data each rule needs, and what happens when a rule has nothing to work with. Get those three right and leads land with the right person without anyone babysitting a queue.
What order should HubSpot lead routing rules run in?
Run HubSpot lead routing rules from most specific to least specific, and stop at the first one that matches: existing owner, named accounts, territory, round robin within the territory, then a fallback queue owned by a named person. That order protects reps already working an account, and it guarantees every lead lands with someone, even when the data behind it is incomplete.
- Existing owner. If the contact or its company already has an owner, the lead goes to that person. This rule comes first because few things damage a deal faster than a second rep showing up in an account someone is already working.
- Named accounts. If the company is on a target account list owned by a specific rep, it goes to them, even if it is brand new to the CRM.
- Territory. If neither of the first two applies, route by region, segment or company size, whatever your team is divided by.
- Round robin within the territory. When more than one rep covers a territory, rotate among them.
- Fallback queue. Anything that fails every rule goes to a named person, usually the sales leader, with an alert. Never to nobody.
Many HubSpot setups start at step four. Round robin is the feature everyone finds first, so it becomes the whole design.
What data does each routing rule depend on?
Every routing rule is only as good as the field it reads. Existing-owner matching depends on clean company association, named accounts depend on a flag and an owner on the company record, territory depends on consistent location data, and round robin depends on an accurate rotation list. When any of those is missing or messy, leads misroute quietly and nobody notices for weeks.
Existing owner needs contacts associated with the right company. If your form creates a new contact without matching it to an existing company record, the rule never fires. Turn on automatic company association by email domain, and clean up duplicate companies before you trust it.
Named accounts needs a property on the company record that marks it as named, and an owner on that record. A spreadsheet of target accounts that lives outside HubSpot does nothing for routing.
Territory needs location or segment data that is filled in and consistent. Country is usually reliable. State, region and employee count are where routing breaks quietly, because forms skip them, enrichment tools fill them in different formats, or a rep types “Colo.” into a field the workflow expects to say “Colorado.” Use dropdown properties instead of free text for anything routing depends on.
Round robin needs an accurate list of who is in the rotation. That list goes stale the day someone leaves or goes on leave.
How do you set up round robin lead assignment in HubSpot?
Set up round robin with HubSpot’s workflow action that rotates record owners, but put it inside one workflow that runs the full rule order. Rotate among a team instead of a list of names, enroll only contacts with no owner, and decide up front what happens to the company and deal owner, so rotation never creates a second rep in the same account.
HubSpot’s workflow tool includes an action to rotate record owners among a set of users or a team. The HubSpot knowledge base covers the mechanics. The design choices are where teams go wrong.
Build one workflow with branches that follow the rule order above, instead of a separate workflow per rule. Separate workflows race each other, and whichever fires first wins.
Rotate among a team, not a hand-picked list of names, so adding or removing a rep happens in one place.
Only rotate leads that have no owner. Add an enrollment condition that the contact owner is unknown, or the workflow will reassign leads that someone already owns.
Decide what happens to the company and the deal. If the contact gets a new owner and the company does not, you have built the next duplicate-outreach problem yourself.
How do you handle reps who are out of office or leave?
Take reps out of the rotation team before planned time off and put them back when they return. When a rep leaves the company, reassign their open leads, contacts and companies the same day, then remove them from every rotation. In a small team this is often where routing fails, because nobody’s job is to notice until a prospect complains.
A departed user still listed as an owner is a black hole. Leads route to them, notifications go to an inbox nobody reads, and the prospect waits.
How do you audit lead routing each month?
Audit lead routing with two saved reports reviewed once a month: contacts created in the last 30 days with no owner, and contacts whose owner differs from their company’s owner. Each record on either list points to the missing data or rule that caused it. Ten minutes a month catches problems before a prospect hears from three of your reps.
Unowned leads. Contacts created in the last 30 days with no owner. Every one of them fell through every rule, so each one tells you which data was missing.
Owner mismatches. Contacts whose owner differs from their company’s owner. Some are legitimate, most are routing misses or duplicate companies.
Where should you start?
Start with the last 50 inbound leads. For each one, check who got it, who should have gotten it, and how long it sat before someone touched it. The pattern in the misses tells you which rule to build first, whether that is existing-owner matching, territory data or a fallback queue, and it gives you a baseline to measure the change against.
If you want an outside look at how leads move through your CRM today, take our free CRM diagnostic. If duplicates are part of the problem, read about what happens when two systems sync into one CRM.
Round robin decides whose turn it is. Routing decides whose lead it is. Build the second one first.