Lead status sits on the contact record next to lifecycle stage, and the two are often confused. Lifecycle stage answers "how far along is this relationship?" Lead status answers "what is sales doing with this person right now?" A contact can stay at the SQL lifecycle stage while lead status moves from new to attempted to contact to connected over a week of outreach.
The default values cover a typical outreach cycle, and admins can edit the options in the property settings to match their own process. Because it is a normal dropdown property, lead status can be set by hand, by workflows, or by sequences and integrations, and it can be used in segments (lists in older portals), views and reports. Newer portals may also have a separate leads object with its own stages, depending on your subscription. If you use it, decide which one your team treats as the source of truth so reps do not update two fields for the same thing.
Lead status matters because it shows the gap between leads handed to sales and leads actually worked. A view of SQLs with a lead status of new and no activity for five days is one of the fastest ways to find leads that fell through the handoff. It also gives marketing a reason code when a lead is sent back, such as bad timing or unqualified, which is far more useful than a lead that simply goes quiet.
Teams that use it well keep the option list short, define when each value applies, and automate the obvious changes. For example, a workflow can set lead status to new when a contact becomes an SQL, and to open deal when a deal is created. Reps then only change it when the conversation changes.