How Do You Set Up Round-Robin Lead Routing by Territory in HubSpot?

How do you rotate new leads among reps in each territory in HubSpot?

Create one HubSpot team per territory, set a territory property on each contact, then build a workflow that branches by territory and uses the Rotate record to owner action inside each branch. Each branch rotates leads only among that territory's team. A fallback branch catches anything without a territory.

This tutorial is for a specific situation. You have a small sales team, maybe four to ten reps, split into two or three territories such as North America, EMEA, and APAC. Leads arrive from Webflow forms or other sources into HubSpot. Today someone assigns them by hand, or one rep gets everything because they check the inbox first.

By the end, every new lead will land with the right territory and rotate fairly among the reps there. You will also have a fallback so nothing sits unowned, which is the failure I care about most.

What do you need before you start?

You need a HubSpot subscription that includes the Rotate record to owner action, paid seats for every rep in the rotation, and a clear rule for which country belongs to which territory. HubSpot's knowledge base lists Sales Hub or Service Hub Professional or Enterprise for this action, and says assignees must have paid sales or service seats.

Check the seat point carefully. HubSpot's documentation says deactivated users or users without a paid seat show with a red border in routing rules and will not be included in assignments. If a new rep joined last week and has a free seat, they will silently get nothing.

Write your territory rule on paper first. Decide which countries map to which territory, and what happens to edge cases such as a US subsidiary of a European company. Most teams use the contact's country, or the company's country when the contact field is blank. Pick one source and stick to it.

How do you set up territory teams in HubSpot?

In HubSpot's user and team settings, create one team for each territory. Add the reps who should receive leads from that territory to the matching team. Name teams plainly, such as "Sales NA" and "Sales EMEA," so the workflow is readable later.

Teams are the cleanest unit for rotation. When a rep moves from EMEA to North America, you change their team membership instead of editing the workflow. That matters because of a detail in HubSpot's docs covered below: editing the owner list inside the action resets the rotation counts.

If one territory has only one rep, still make it a team. The workflow stays consistent, and when you hire a second rep there, you add them to the team and the rotation starts working with no workflow change.

How do you create the territory property?

Create a custom contact property called "Sales territory" as a dropdown with one option per territory plus "Unassigned." Then set it automatically with a small workflow, or as the first branch of your routing workflow, based on the contact's country. Reps should be able to see this property on the contact record.

In the property settings, choose the contact object, give it a clear label, and pick dropdown select as the field type. Add options that exactly match your team names, such as North America, EMEA, APAC, and Unassigned. Matching names make the workflow and reports easy to read side by side.

To fill it, use an if/then branch on the Country property. Contacts whose country is in your North America list get "North America," and so on. Anything that matches no list, including a blank country, gets "Unassigned." Keep the country lists in one place so they are easy to update when your territory plan changes.

How do you build the routing workflow?

Create a contact-based workflow that enrolls new contacts who have no owner and come from your lead sources. Add an if/then branch on the Sales territory property, with one branch per territory. Inside each branch, add a Rotate record to owner action set to rotate between the matching team.

For enrollment, start narrow. A good trigger is "contact owner is unknown" combined with a lead source or form submission filter, so existing customers and imported lists do not get rotated by accident. Test the trigger on a few sample contacts before turning anything on.

In each Rotate record to owner action, HubSpot lets you choose the user property, whether to overwrite an existing owner, and whether to rotate between specific users or teams. Pick the contact owner property, leave overwrite off, and choose the territory team. HubSpot's docs say records are assigned equally within a selected team by default for most record types.

What should the fallback branch do?

Send unassigned leads to one named person and alert them. The fallback branch, for contacts whose territory is Unassigned or that match no branch, should assign a single owner, usually a sales manager, and send an internal notification. An unowned lead is the most expensive kind of lead, because nobody feels responsible.

HubSpot's documentation also says that if there is no eligible user to rotate to, or if no team is selected for team-based assignment, no owner will be assigned. So a territory team where every rep is on leave, or has lost a paid seat, will produce unowned leads even inside a normal branch.

To catch that, add a second check after each rotation step. If the contact owner is still unknown, route the contact to the fallback owner and notify them. It is one extra branch per territory, and it closes the gap where leads quietly go nowhere.

What are the common gotchas with this setup?

The big three are rotation resets, CRM sync conflicts, and lead objects. HubSpot says that adding or removing owners in the action after the workflow is on resets assignment counts. It also warns that if the owner property syncs to Salesforce, the action may not work as expected.

The reset rule is why I prefer teams over specific users in the action. If you list users directly and edit that list every time someone joins or leaves, you restart the count each time. With teams, membership changes happen outside the action. Check HubSpot's current docs for how team changes are handled, since the behavior can change.

The Salesforce warning matters for any team running both systems. HubSpot's docs say Salesforce may try to update HubSpot with the previous owner even after HubSpot clears ownership. If you sync owners both ways, decide which system owns assignment first. If you are on the newer leads object, HubSpot documents extra distribution options such as load balanced and round robin, and a setting to turn off before assigning leads.

How do you test the routing before going live?

Create test contacts for each territory and one with no country, enroll them manually, and check who owns each one afterward. Then submit a real form on your Webflow site from a test email and confirm the full path works, including the notification to the rep who receives it.

Watch the first week closely. Count how many leads each rep received per territory and compare that to what you expected. Uneven numbers in the first few days are normal with small volume. A rep with zero leads after a week usually points to a seat or team membership problem.

Once it is stable, measure what matters: how fast reps respond after assignment. I walked through that report in building a lead response time report in HubSpot. If you are still deciding whether HubSpot or Zapier should own routing at all, see routing inbound leads to the right owner in HubSpot.

What should you do next?

Write your country to territory map, create one team per territory, add the Sales territory property, and build the branched workflow with a fallback owner. Test with sample contacts and one real form fill. Review lead counts by rep after the first week and fix any seat or team gaps.

Fair rotation is not only about fairness to reps. It is about speed. A lead that lands with an available rep in the right territory gets a faster, better first call than one that waits in a shared inbox. If your territories are still being drawn, settle that split before you build the rotation.

Rotations break most often when someone is out, so I wrote about how to reroute leads when the assigned rep is away.

If you want help building territory routing in HubSpot or untangling an existing setup, reach out and let's chat.