How a lead gets assigned
When a new Contact or Deal is created in HubSpot without an owner, RoundRobinLeads gives it to the next available rep in the rotation pool, in turn order or by weight, skipping anyone out of office or outside working hours. It needs no workflow and no Sales Hub Professional. Here's exactly what happens, step by step.
A Contact or Deal is created in HubSpot
HubSpot fires a webhook to RoundRobinLeads the instant a new Contact or Deal is created — there's no polling delay.
RoundRobinLeads checks if it already has an owner
If the record already has an owner set — someone assigned it manually, or a workflow already handled it — RoundRobinLeads leaves it alone. It only assigns unowned records.
It looks up which rotation pool applies
Pools are scoped by object type (Contacts or Deals) and, optionally, by pipeline. Only active pools are considered.
It builds the list of eligible reps
Reps marked out-of-office, or outside their configured working hours, are skipped. If a pool is configured to fall back to "anyone" when nobody's currently available, that kicks in here. Otherwise the lead waits, and goes to the next rep who becomes available. The audit log shows it waiting and who got it.
It picks the next rep in rotation
By default this is a straightforward turn order. If you've set weights (say, a senior rep should get twice as many leads as a new hire), the rotation expands proportionally so higher-weight reps come up more often, while still cycling through everyone fairly over time.
The owner is set on the record
RoundRobinLeads calls the HubSpot CRM API to set hubspot_owner_id on the Contact or Deal — the same field HubSpot's own UI uses, so nothing else in your portal needs to change.
The rotation pointer updates
RoundRobinLeads remembers who was assigned last, so the next lead picks up from the correct place in the rotation — even across restarts.
It writes an audit log entry
Every assignment gets a plain-English reason attached — "next in rotation", "skipped Sarah — OOO", or an SLA reassignment reason. You can always see who got what, and why.
What happens if a rep doesn't respond
Assignment isn't the whole job — a lead that's assigned but ignored is just as cold as one that was never routed. On the Starter and Growth plans, you can set an SLA window (say, 30 minutes) on any pool. If RoundRobinLeads doesn't see the assigned rep log any engagement — a call, email, meeting, note, or task — within that window, it reassigns the lead to the next eligible rep automatically, and logs the reassignment as an SLA breach. If the next rep also misses the window, it keeps going, highest-weighted rep first, and once every rep has missed it the lead goes to an escalation owner you choose, such as your sales manager.
This is deliberately conservative: it only reassigns based on real engagement activity in HubSpot, not a guess, and every reassignment is visible in the audit log with the reason attached. To switch it on, see SLA escalation in the setup guide.