Skip to content

Temperature Signals

A lead’s temperature reflects recent engagement, not where they are in the pipeline. Use this page when you want to know “why is Marcus Williams showing Hot?” or “why did this Warm lead drop to Cold yesterday?”

BandScore rangeWhat it usually means
Cold< 30Quiet. Either never engaged much, or hasn’t touched the site in a while.
Warm≥ 30 and < 70Active. Returning visits, some saved properties, some replies.
Hot≥ 70Heavily engaged — multiple recent sessions, multiple favorites, tour requests, fast back-and-forth.

Transitions happen at the thresholds: a score crossing 30 upward flips Cold → Warm; crossing 70 upward flips Warm → Hot. The reverse thresholds are the same numbers — drop below 30 and a lead goes Cold again.

The score is recalculated on read with a 1-hour cache. Each signal contributes a point value, points sum, and the total is compared to the thresholds above.

The exact point values per signal are currently being calibrated against real session data from converted leads. The table below describes signals by relative contribution, not exact weights. Treat ordinal magnitude (high / medium / low / dampening) as load-bearing and the actual numbers as moving targets.

These are the strongest predictors that a lead is close to acting.

SignalSourceWhy it matters
Tour request submittedLead form / admin actionThey’ve named a property and asked to walk it.
Pre-approval letter uploadedLead documentThey’ve spent money getting financing-ready.
Multiple property favorites savedClientFavoritePattern of returning to specific homes.
Replied to your last outreachCrmStateEventTwo-way conversation is the strongest signal.

Consistent activity but no clear intent-to-act yet.

SignalSourceWhy it matters
Returning sessions within 7 daysSessionEventHabit of coming back.
Saved search criteriaSessionPreferenceDefined what they’re looking for.
Multiple property detail-page viewsSessionEventGoing deeper than browse.
Communication preference set by leadCrmFlagCaring enough to manage their inbox.

Baseline activity. Counts, but won’t move a Cold lead to Warm on its own.

SignalSourceWhy it matters
Search-result page viewsSessionEventBrowsing, not deep-diving.
Email opensSessionEventThey saw it. They didn’t act on it.
Newsletter signupsLeadLow-commitment interest.

Engagement decays. A lead that was Hot last month and hasn’t been on the site since slowly drops without anything bad happening.

BehaviorEffect
Time since last sessionContinuous decay. The longer they’ve been silent, the more the score erodes.
Time since last replied outreachDecay, weighted heavier than passive silence.
Explicit unsubscribe / DNC flag setDoesn’t zero the score directly, but the absence of outreach removes future positive signals.

The score is not zeroed by a state change. A lead moving from QUALIFIED → ARCHIVED keeps whatever score they had; archive itself doesn’t mean Cold (though usually a lead reaches ARCHIVED because they’ve gone Cold).

A card shows the temperature chip with the current score:

  • Hot 92.0 — score is 92, well into the Hot band
  • Warm 41.5 — score is 41.5, in the middle of Warm
  • Cold 12.0 — score is 12, deep Cold

The decimal precision is intentional. A score of 69.8 is almost Hot — that’s information you’d lose with rounded bands alone.

Temperature is computed independently of pipeline state. Common combinations and what they mean for tactics:

State + temperatureRead
NEW + HotLead is engaged before you’ve even called. Get to them now.
CONTACTING + ColdOutreach without engagement. Try a different channel before you give up.
QUALIFIED + HotMarcus Williams. Showings and offer prep.
QUALIFIED + ColdPre-approved but ghosting. Re-engagement attempt; tactic differs from a hot pursuit.
ARCHIVED + Warm risingThey came back. The score climbed past 30 — manual reactivation may be worth it.

For the philosophical version of why these two axes don’t collapse into one, see why state and temperature are separate.

  • Weights are not finalized. The point values per signal will shift as the model is backtested against closed-loop data from real converted leads. Bands (30 / 70) are firm; per-signal weights will change.
  • No backfill yet. Leads from before the lifecycle feature shipped (2026-05-16) don’t have synthesized temperature history. They’ll show a current score based on whatever signals exist, but the chart can look sparse.
  • No SLA-style alerting on temperature. A Hot score doesn’t currently push a notification — visibility only. Watch the board.