Round-robin with fairness cap (max N leads per rep per day)

Outcome. The team keeps rotating leads evenly, and sales ops gets alerted the moment a rep crosses the agreed daily maximum, so the pool can be adjusted before the same rep gets overloaded again tomorrow.

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

flowchart TD
    A[New lead created] --> B[Rotate to Standard SDR rotation]
    B --> C[Set routed date, notify owner]
    D[Sales ops checks daily report] --> E{Any rep at or above cap?}
    E -->|Yes| F[Remove rep from rotation list for rest of day]
    E -->|No| D
    F --> G[Next morning: re-add rep to rotation list]

When to use it, when not to

• UseUse it when a rep's daily lead intake genuinely needs a ceiling (ramping reps, part-time reps, or a period where one rep is doing double duty on another task).
• UseUse it when a soft cap enforced by a daily check and a manual pool adjustment is an acceptable trade-off against building a hard, real-time automated block.
• SkipDo not expect a true real-time stop. Native HubSpot workflows act on one enrolled record at a time; there is no built-in action that counts "how many contacts a given owner already received today" and refuses the next one inline. If a hard, fully automated cap is a requirement, see the Data Hub Variant below, and confirm that tier before promising this at Sales Hub Professional alone.
• SkipDo not use it if the team is small enough that a manager already watches the rotation manually; the reporting layer described here may be more process than the team needs.