Weighted round-robin by rep capacity (custom property counter)

Outcome. Leads split across the team in proportion to each rep's actual capacity (a senior full-time rep gets more, a part-time or ramping rep gets less) instead of everyone getting an identical even share.

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

flowchart TD
    A[Contact created, owner unknown] --> B{Random split 50/50}
    B -->|50%| C[Assign Rep A]
    B -->|50%| D{Random split 50/50}
    D -->|50%| E[Assign Rep B]
    D -->|50%| F[Assign Rep C]
    C --> G[Set routed date, weighted assignee, notify, create task]
    E --> G
    F --> G

When to use it, when not to

• UseUse it when the team is not uniform: mixed tenure, part-time reps, ramping new hires, or reps carrying a different existing pipeline load who should get fewer or more new leads than an even split would give them.
• UseUse it once plain lead-routing-001 or lead-routing-002 is already working and the team has agreed on relative capacity numbers (not exact live workload, see Known pitfalls for that distinction).
• SkipDo not use it if the team is genuinely uniform in capacity; an even round-robin (lead-routing-002) is simpler to build and to audit.
• SkipDo not use it expecting a live, real-time workload balancer. HubSpot workflows cannot dynamically compare one rep's current open-lead count against another rep's inside a single branch; this fiche uses a pre-agreed weighting, reviewed and rebalanced on a cadence, not a real-time optimizer. A true live capacity balancer needs a custom coded action to compute and compare counts across reps, which pushes this into Data Hub Professional territory, out of scope for the sales-professional tier this fiche targets.