Route leads by HubSpot score band into 3 priority queues (hot/warm/cold)

Outcome. A lead's score sorts it straight into a hot, warm, or cold response track, so a rep's time goes to the leads most likely to close first instead of a flat first-in-first-out queue.

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

flowchart TD
    A[HubSpot score set/changed] --> B{Score >= 80?}
    B -->|Yes| C{Already hot?}
    C -->|No| D[Set band = hot, rotate to Hot pool, notify, same-day task]
    C -->|Yes| Z[No action, already handled]
    B -->|No| E{Score 40-79?}
    E -->|Yes| F{Already warm?}
    F -->|No| G[Set band = warm, rotate to Warm pool, notify, next-day task]
    F -->|Yes| Z
    E -->|No| H[Set band = cold, enroll in nurture, no owner change]

When to use it, when not to

• UseUse it once a scoring model is already configured and producing a meaningful HubSpot Score spread across your contacts.
• UseUse it when the team has agreed on score thresholds that map to real response expectations (same day, next day, nurture).
• SkipDo not use it if the scoring model is brand new and untested; validate the score distribution first, thresholds set against noisy data will misroute leads either way.
• SkipDo not use it as a replacement for a needed nurture track; cold-band leads here still need somewhere to go, see Prerequisites and Steps.