CRM lead statuses: which you need and how to set them up

Short answer

A lead status shows the state of the work on a lead: not yet touched, being worked, cannot be reached, closed as won, closed as lost. A sales stage answers a different question — how close the customer is to a buying decision. Set up properly, five to seven statuses are enough, each has a clear entry and exit rule, some transitions require a field, and a lead sitting too long in "new" becomes visible automatically. The longer the status list gets, the more managers fill it in wrongly and the less the report means.

Status and stage: two different questions

The most common muddle is putting statuses and stages in one list: "New, Called, Proposal sent, No answer, Won". Two different measures are mixed here. "Called" and "no answer" describe the state of the manager's work; "proposal sent" describes where the customer is on the path to buying.

Major CRMs keep the distinction too. In HubSpot's documentation, for example, the lifecycle stage shows where a contact is in the overall process, while lead status describes sub-states within a sales-qualified lead. Stages are covered separately under sales pipelines; this article is about statuses only.

Five statuses to start with

1. 1NewThe lead exists and nobody has touched it. How long a lead stays here is the single most important checkpoint.
2. 2WorkingIt has an owner, and contact has been made or is being attempted.
3. 3UnreachableThe agreed number of attempts has been made and the customer does not respond.
4. 4WonA sale, a meeting or whatever the company counts as success has happened.
5. 5LostThe customer declined, is not a fit or chose a competitor — with the reason.

These five are enough for most small and mid-sized teams. Add a sixth only when there is a real need — for example "future contact": interested, but in three months.

Entry and exit rules for each status

A status is a rule, not just a label. Without written rules, each manager applies statuses their own way:

• Leaving "new": when an owner is assigned or the first contact attempt is made.
• Entering "unreachable": for example, three attempts on two different days at different times. One unanswered call is not this status.
• Entering "lost": impossible without choosing a close reason.
• Entering "won": what counts as a win is written once, company-wide — payment, contract or meeting?
• Going back: a "lost" lead is not reopened; when the customer writes again a new lead is created and the old one stays in the history.

Required fields on transition

Some transitions are meaningless without data. If no reason is recorded when a lead is closed as lost, there will be no answer at month end to "why are we losing?". The minimum:

• Lost → close reason: price, not ready, competitor, not a fit, other.
• Unreachable → number of attempts and date of the last one.
• Working → the next step and its date.
• Won → amount or type of outcome.

Time limits: how long a status may last

Every status has a "normal" duration. When it is exceeded, the lead should become visible to a manager and the owner should get a reminder. Illustrative starting values:

• New: no more than 30 minutes during business hours.
• Working, with no next step: 2 business days.
• Unreachable: after 7 days, either closed or another channel is tried.
• Future contact: returns to "working" automatically on the set date.

Adapt the numbers to your sales cycle: in real estate and B2B the limits are long; in online retail they are short.

Who changes statuses

Some status changes can be automatic: when an owner is assigned, "new" becomes "working"; after the third unanswered call, "unreachable" is suggested. "Won" and "lost" are human decisions and should not be set automatically: AI might read a customer's "I'll write later" as a refusal.

Reporting from statuses

Good statuses give three simple reports. First, the number and age of leads waiting in "new" — a speed problem. Second, the share of "unreachable" by channel — a lead-quality or attempt-rule problem. Third, the breakdown of lost leads by reason — a product, price or competition problem. The order in which leads should be worked is covered in lead prioritisation.

An illustrative example

This is an illustrative example. A training centre's CRM had 14 statuses: "Called 1", "Called 2", "WhatsApp sent", "Thinking", "Will talk to parent" and so on. In the report, 40% of leads sat in "Thinking", and nobody could explain what that meant.

The team moved to five statuses and started writing "thinking" as a next step rather than a status: "will talk to parent on Friday, call on Saturday". Two weeks later, the manager saw a list of "leads with no next step" for the first time.

Common mistakes

• Mixing statuses and stages in one list.
• Creating a status for every attempt ("call 1", "call 2") — that is a counter, not a status.
• Allowing "lost" without a reason.
• Adding new statuses without removing old ones.
• Letting AI close leads automatically.

Limitations

A status is only as accurate as the manager's record. If a deal was agreed by phone but the status was not changed, the report stays wrong. So statuses must be changeable with one tap where the work happens — in the notification, inside the conversation. Statuses also do not replace designing the sales process itself.

Lead statuses in Vexvon

In Vexvon a lead has five statuses: new, working, won, lost and unreachable. Separately, the customer record holds sales stages — nine by default, which the company creates, names and colours itself. When a manager taps "Start" on a Telegram notification, the lead is assigned to them and moves to "working". A lost lead gets a close reason — price, not ready, competitor, other — and the number of contact attempts is shown on the record. Every change goes into the lead's activity log. More on Vexvon CRM.

Next step

Export your CRM's status list and write one question next to each: is this the state of the work, or the customer's place on the buying path? Those in the second group should leave the status list. The overall logic of an AI CRM is in what is an AI CRM. More articles are in the lead management section, and we can review your statuses together during a demo.