Score band thresholds

Every brokerage has a Warm at score and a Hot at score stored on its account, but the controls for them are not currently shown in settings. Here is what they are and what they are not.

The display bands are fixed and universal

  • Cold: 0 to 29.
  • Warm: 30 to 59.
  • Hot: 60 to 84.
  • Very hot: 85 to 100.

Every REHL account uses these cutoffs, and you cannot move them. That is on purpose: a Hot lead means the same thing in your brokerage as in anyone else's, which is what makes analytics and benchmarks comparable.

What your thresholds do

Warm at score and Hot at score are your brokerage's own tier thresholds, kept separate from the fixed bands on purpose. They exist for lead-tier pricing: when a lead is sold, its tier and price are meant to be worked out by comparing its score to these two numbers. That path is a Phase 2 feature and is not active yet, so REHL currently hides the Warm at / Hot at controls in settings rather than let you tune something inert. The underlying values are still stored, and Cultivate passes them to REHL AI as context when it drafts a message, but nothing branches on them for any customer today.

None of this affects cadence intensity, routing priority, or notification urgency, and those three are not affected in the same way, so it is worth being precise. Your bell is the only one of the three that watches a temperature band at all, and it watches the fixed cutoffs above, so once tier pricing goes live, changing Hot at will still not move your bell earlier. Auto-routing reads nothing about temperature: it runs at capture, before a score exists, and only the By source strategy reads where the lead came from. Brokerage owner and Round robin never look at the source. Cultivate's touch timing comes from the plan REHL AI writes for that lead, not from a band; what a band crossing does is prompt Cultivate to rewrite the plan, which is a fresh plan rather than a tighter one.

If you want more attention on a lead earlier, the lever is your Cultivate settings, not these numbers.

Was this helpful?

Need more help? Contact support.