On this page
What HubSpot supports natively
| Lead status (contact property) | Lead stage (Leads object) | |
|---|---|---|
| Lives on | The contact record | A separate lead record associated with the contact |
| Default values | New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected, Bad Timing | A lead pipeline with stages including New, Attempting and Connected |
| Moves automatically | Only if you build a workflow for it | Yes: HubSpot moves a lead to Attempting when a rep logs outreach, and to Connected on a reply, completed meeting or connected call (Sales Hub Professional or Enterprise) |
| Customizable | Yes, edit the property’s options | Yes, the lead pipeline’s stages |
Companies have their own Lead status property, which HubSpot describes as the company’s sales, prospecting or outreach status, with five options by default. HubSpot positions lead status as the detail inside the Sales Qualified Lead lifecycle stage: lifecycle says the contact is with sales, lead status says what sales is doing about it. HubSpot’s lead pipeline automation doesn’t mention updating the lead status property, so if you use both, decide which one reps work from.
How to use HubSpot lead status
- Agree the values with sales first. Keep it short. Most teams need five or six values, each with a one-line definition of when it applies.
- Map each value to an action. “Attempted to Contact” should mean a specific number of attempts. “Unqualified” should require a reason property.
- Set the starting value automatically. A workflow that sets lead status to New when a contact becomes a Sales Qualified Lead gives reps a clean queue.
- Let deals drive the late values. Setting Open Deal when a deal is created keeps lead status in step with the pipeline.
- Report on it weekly. A saved view of SQLs by lead status and owner shows who has untouched leads.
- Don’t use lead status for marketing stages. That’s what lifecycle stage is for. See lifecycle stage vs lead status vs deal stage.
Common mistakes
- Merging options that workflows use. Workflows compare against each option’s internal value, which can’t be changed once saved, so renaming a label is safe. Merging two options isn’t: HubSpot doesn’t update the workflows, segments or filters that use the merged value, and they stop matching without any error.
- Two writers. A workflow sets Connected while a rep sets Bad Timing; the next workflow run overwrites the rep. Give each value one writer, as with lifecycle stages.
Where Jetstack AI fits
When the values and rules are agreed, Jetstack AI Projects builds the automation around them. Describe when each status should be set in the brief; Jetty turns it into a plan you review, and approving it generates the properties, lists and workflows that set lead status. You approve deployment separately, workflows are created switched off so you can test them first, and the receipt shows what was created, read back from HubSpot. Projects is currently in limited release; see what Projects can build.
Sources
- Use contact and company lifecycle stages: lead status (HubSpot Knowledge Base)
- Set up lead pipeline automation (HubSpot Knowledge Base)
- HubSpot's default contact properties: Lead status (HubSpot Knowledge Base)
- Manage enumeration property options (HubSpot Knowledge Base)
- Projects capabilities (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
Workflows & automation
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects