What Is Lead status?

The state of current lead work

A lead-status field can tell a rep that a record is new, has been attempted, is connected or needs another action. The exact values and transition rules depend on the CRM and the team's process. A label is useful only when people understand what event changes it, who owns the update and what work should happen next.

This is distinct from broader lifecycle stage. HubSpot documents lead status as sub-stages within its sales-qualified lifecycle convention, but other systems organize leads differently. Do not assume every company uses the same model. A contact's operational status, a person's relationship to the business and a particular opportunity's deal stage can all change independently, and each needs its own field definition.

Avoid a mapping mistake

An enrichment import may contain valid as an email-verification result. Mapping that value into a lead-status field would confuse contact-point evidence with sales progress. Similarly, a campaign reply event should not automatically become connected if the reply is an out-of-office notification. Review the event meaning before letting an integration advance a record or trigger the next seller task.

Make transitions auditable

Keep the prior status, new status, source event and update time where the system supports them. Define how records enter review, return for follow-up or stop being worked. Protected contact restrictions should remain explicit even if the operational status changes. A new source record must not turn an opted-out person into a fresh lead merely by resetting the field to new.

Use status in work queues and handoffs with an agreed vocabulary. If a manager cannot explain why a record holds its label, the field is reporting an assumption rather than a controlled process state. The useful outcome is clear ownership and next action, not a colorful stage name that obscures whether anyone actually contacted the person.