Automatic lead qualification: a score born from the conversation

Where the score comes from

Each lead's score adds up different signals collected during the conversation: how far they have engaged (products of interest mentioned, volume of messages exchanged), how many buying-intent signals appeared, the qualification stage (from first contact through qualified) and how much of the budget, decision authority, urgency and timeline criteria the lead has confirmed themselves.

Engagement has a ceiling: past a certain volume of messages exchanged or products of interest mentioned, it stops adding to the score. Buying-intent signals, on the other hand, have no cap — the more of that kind of signal the conversation reveals, the higher the score climbs, with no fixed ceiling, which keeps a long, commercially hot deal from being bottled up at a low number just because basic engagement has already saturated.

That score is recalculated with every relevant new message — it is not a number someone sets once and forgets. The breakdown stays available internally by criterion, so you can understand exactly what made a specific lead's score climb or stall.

Temperature is not the same thing as score

Beyond the qualification score, every lead also carries a temperature — Hot, Warm, Cool, Cold or Frozen — calculated from how many days they have gone without replying, not from the qualification number. A lead can be highly qualified and still cool off after days without interacting, and that alert is exactly what temperature exists to give.

Keeping the two metrics apart avoids a common mistake: treating a lead as lost just because they stopped replying, when in fact they had already revealed enough budget and urgency to be worth another attempt — the score stays high even as the temperature falls.

Qualification status, visible in the pipeline

Each lead also carries a qualification status — from not qualified through engaged, in nurturing or qualified — that sums up, in one word, what stage they are at, without opening the whole conversation history to work it out. That status evolves alongside the score and the confirmed budget, authority, urgency and timeline criteria.

The moment a lead starts counting as qualified is recorded too, with date and time — no digging through the conversation history to find out when that lead became a priority, and no working out by hand how long they have been at that stage.

It is that status, combined with the score, that feeds the automatic decision to hand a qualified lead to a sales rep — the sales team does not have to comb through conversation after conversation to find out who is ready for a direct approach.

The point at which a lead turns Hot

SDRBOT.ai already counts a lead as Hot from 70 qualification points, and raises an alert to the responsible team when the score crosses 80 — two fixed thresholds, applied the same way across the whole organization, that help standardize what "worth approaching now" means, instead of leaving it to each sales rep's personal judgment about when a lead is worth pushing.

Those numbers appear both on the individual lead profile and on the team tracking dashboards, giving the manager an objective way to prioritize who the team should contact first on a day with many leads in the queue — without relying on intuition or rereading conversation after conversation to decide where to start.