Lead Status vs. Sub-Status
Status vs. Sub-Status
Every lead has both a Status and a Sub-Status — two distinct, separately-tracked fields, not one field with two names.
Status is one of 5 fixed top-level stages:
- Fresh — newly arrived, not yet worked
- Reckoning — actively being worked/processed
- Farm — not ready now, being nurtured for later
- Grim — dead-end (wrong number, do not contact, deceased, etc.)
- Void — doesn't count (test lead, duplicate)
Sub-Status is a more specific reason within that Status — for example, under Fresh: New Lead, Left Message, Meeting Scheduled; under Grim: Wrong Person, Do Not Contact, Deceased. Some sub-statuses only apply to Service markets or only to Product markets.
This 5-status structure and its sub-statuses are fixed by the product — an organization can relabel what they're called (see How to Rename Your Status Labels), but can't add, remove, or reorder the statuses themselves.
Why isn't there a "Pipeline"?
Marketing language (including kamocrm.com) describes "managing your sales pipeline" — but in the CRM/Leads module, there's no separate "Pipeline" object. What that phrase maps to, concretely, is the Status/Sub-Status system above: a lead's progress is its Status and Sub-Status.
Worth noting: "Pipeline" is a literal, distinct feature elsewhere in the platform — the Mortgage Applications module has a real Pipeline board tracking loan files through stages like Application Taken, In Processing, In Underwriting, Clear to Close, Funded. That's a different object (a loan application, not a lead) in a different module. If you're documenting Mortgage Applications, "Pipeline" is real there; if you're documenting Leads/CRM, it isn't — use Status/Sub-Status instead.
