How the score drives your workflow

What the score really does

• Rings your bell. The moment a lead crosses up into Hot or Very hot, the owning agent's in-app bell fires. If nobody logs any activity on it, the alert escalates to the team lead and then to the brokerage owner. Logging a real touch clears it; simply opening the lead does not.
• Orders your pipeline. The leads list sorts by score, highest first, with unscored leads last.
• Ranks your day. The Pilot brief on the leads page picks who to call next using the score together with its 7-day momentum, recent activity, and pre-qualification.
• Re-plans Cultivate. A significant score change or a band crossing triggers Cultivate to regenerate the lead's strategy, and the score plus its recent trajectory are given to REHL AI as context when it writes the new plan.

What the score does not do

It does not set Cultivate cadence intensity. A regenerated plan is a fresh plan, not a tighter one: the timing and number of touches come from REHL AI reading the whole lead, and a Very hot lead is not mechanically given a faster rhythm than a cold one.

It does not affect routing. Auto-routing picks an owner by your chosen strategy (brokerage owner, round robin, or by source) and runs at the moment of capture, before the lead has been scored at all. There is no priority queue and no load balancing.

It is not what agents are measured on. The performance page scores your team on response time, lead volume, close rate, days to close, GCI, and logged activity. The one temperature-flavoured metric, hot leads touched, counts leads currently banded hot that an agent logged anything on. It is a coverage count, not a measure of moving temperature.