Round-robin using HubSpot Teams (assign within team then round-robin)

Outcome. A lead is routed to the correct regional and functional sub-team first, then rotated evenly among that sub-team's members, instead of one flat pool that ignores your org chart.

Workflow map Enrollment, branches and actions at a glance lead-routing-018

flowchart TD
    A[Contact created / Territory set] --> B{Territory?}
    B -->|north-america| C{Employees > 500?}
    B -->|emea| D{Employees > 500?}
    C -->|Yes| E[Rotate NA Enterprise Team]
    C -->|No| F[Rotate NA SMB Team]
    D -->|Yes| G[Rotate EMEA Enterprise Team]
    D -->|No| H[Rotate EMEA SMB Team]
    B -->|blank| I[Notify sales ops + add to Needs manual routing list]
    E --> J[Set routed date, notify, create task]
    F --> J
    G --> J
    H --> J

When to use it, when not to

• UseUse it when sales is organized in nested Teams (a parent regional team split into child teams, for example an enterprise team and an SMB team inside "EMEA").
• UseUse it when the deciding factors for which child team owns a lead (region plus a size or segment signal) are both reliably captured on the contact record.
• SkipDo not use it for a flat, single-layer team structure; a plain rotation pool per territory is simpler and cheaper, see lead-routing-001.
• SkipDo not use it as a substitute for permission management; Teams control rotation pools here, they do not by themselves restrict record visibility, see lead-routing-046 for that.