Most routing problems I see in HubSpot portals are not caused by the rotation itself. They come from what happens before it (no territory logic, so the wrong rep gets the lead) and after it (no rule for what happens when the owner never calls). This article walks through how I build routing in HubSpot from the rotation action outwards. It covers the mechanics, not the agreement: the response times themselves belong in your sales and marketing SLA.
What "Rotate record to owner" actually does
The workflow action "Rotate record to owner" assigns enrolled records to a list of users or a team in turn. HubSpot's knowledge base article "Assign and rotate record owners using workflows" describes the details I design around. It is available on Sales Hub or Service Hub Professional and Enterprise. You can rotate into the standard owner property or a custom HubSpot user property, which is useful when you want an SDR owner and an AE owner on the same record. You choose whether to overwrite an existing owner, and I almost always leave that off for contacts, because overwriting a named account owner is how you start an internal fight. The users you rotate to need paid sales or service seats. HubSpot also notes that editing the user list on a live action resets the rotation counts, so batch your team changes instead of tweaking the list every week.
Plain round robin: when it is enough
An even split works when every rep sells the same product, to the same market, in the same time zone, with roughly the same open workload. That describes many small sales teams, and for them I keep routing deliberately boring: one contact-based workflow, enrolment on the property that defines a sales-ready lead (for example Lifecycle Stage becomes Marketing Qualified Lead), a check that the owner is unknown, then the rotate action. Add a task creation step right after the assignment so the rep has something in their queue, not just a notification. If you use the HubSpot Leads object, HubSpot's documentation describes extra distribution options for lead records, but parts of this have been in beta, so check what your portal actually shows before designing around it.
Territory routing with branches before the rotation
HubSpot does not need a separate territory tool for most teams. I put an if/then branch before any rotation, splitting on the properties that define the territory: Country or State, company size, industry, or product interest. Each branch ends in its own rotate action with the users or team for that territory. Two rules keep this maintainable. First, route on properties you can trust. If Country is free text on your form, the branch fails silently, so make it a dropdown first. Second, always build a "none of the above" branch that rotates to a catch-all team and alerts the RevOps owner, because unmatched leads are the ones that disappear. If the account already has an owner, I check that before the territory branch and assign the contact to the company owner instead of rotating.
Capacity-based routing without fragile hacks
The standard rotate action splits evenly, it does not look at how many open leads each rep already holds. I handle capacity in one of three ways, from simplest to heaviest. One: take a rep out of the rotation list while they are on leave or overloaded, accepting that this resets the counts. Two: build separate rotation teams for different lead tiers, so senior reps get high-fit leads and newer reps get the rest. Three: if your portal offers load-balanced distribution for lead workflows, test it on a small team before rolling it out. For anything more complex, such as weighting by quota or live open-lead counts, I would rather use a dedicated routing app from the HubSpot marketplace than build a chain of custom-coded actions that only one person understands.
Re-routing rules when the owner does not act
Routing without re-routing just moves the leak downstream. I build a second workflow that enrols on the same trigger, waits for your SLA window, then checks whether Lead Status is still New or whether there is no logged activity. If so, it notifies the manager first. If the next window also passes, it rotates the record to a fallback team, using the overwrite option deliberately this time, and logs the reason in a property such as "Re-routed reason". Keep the windows business-hours aware, or a Friday evening lead will be re-routed before anyone has had a fair chance. Report on the re-routed count by rep monthly. It is a coaching signal, not a punishment tool.
Testing and monitoring the routing
Before switching a routing workflow on, I create a handful of test contacts that cover every branch, including the empty-territory case, and check where each one lands. After launch, three views tell you if routing is healthy: unassigned sales-ready contacts (should be close to zero), leads per rep over the last 30 days (should match your intended split), and time from assignment to first activity by rep. HubSpot's rotate action processes records one at a time, so a large bulk import can take a while to route. Do imports outside working hours or route them with a separate workflow so live inbound leads are not stuck behind them.
FAQ
HubSpot's knowledge base lists the rotate action under Sales Hub or Service Hub Professional and Enterprise. On lower tiers you can assign owners manually or through chat routing, but not through rotate actions in workflows. Check the current product and plan page for your hubs.
Yes, with if/then branches in a workflow on properties like Country, State, company size or industry, each ending in its own rotate action. Make the territory properties dropdowns so the branches match reliably.
The standard rotate action splits evenly. Lead workflows may offer additional distribution options, which HubSpot has listed as beta for lead records, so confirm in your own portal. Otherwise, manage capacity with separate rotation teams or a marketplace routing app.
Routing decides who gets the lead and what happens if they do not act. The handoff playbook and SLA define when a lead is ready and what each team owes the other. You need both.