Lead statuses

A status says where a lead stands. Each workspace has its own list of statuses, in the order your team works through them.

A new workspace starts with five statuses: new, contacted, qualified, disqualified and converted. In Dashboard → Settings → Statuses, keep them, rename them, add your own or delete the ones you do not use, except new.

API value, label and color

Each status has three parts:

• API value: what Klozeo stores on the lead, for example meeting. Your API calls, imports, n8n and Make scenarios, exports and webhooks all use it. It is exact and case-sensitive, up to 50 characters, and it cannot change once the status exists.
• Label: the name your team sees in the dashboard, for example “Meeting booked”. You can rename it at any time. Leave it empty to keep the built-in name of a default status, or to show the value.
• Color: gray, blue, green, red, violet, amber, pink or teal. It colors the status badge in the leads table.

A workspace can have up to 30 statuses.

Rename without breaking your scenarios

Renaming a status changes its label only. Exports and webhooks carry the value, not the label, so a scenario that filters on meeting keeps working after you rename “Meeting booked” to “Demo scheduled”. Renaming changes no lead and sends no webhook.

To use a different value, add a new status and move your leads to it. Then update the scenarios that send or filter on the old value.

Delete a status

Deleting a status leaves your leads unchanged: they keep their value, and the dashboard flags it “Not in the list”. You can add the status back at any time with the same API value, or move those leads to another status.

new cannot be deleted, because a lead created without a status gets it.

A lead can also receive a value that is not in the list, from the API, an import or an automation. Klozeo keeps it as sent and flags it the same way, so nothing is lost.

Who can edit the list

In an editable workspace, the owner and admins can edit the list. On Free, only the owner can. In a read-only workspace, nobody can edit it. Everyone else sees it read-only, and editors pick from it when they set a lead’s status.

Group leads by status

In the leads table, filter on a status, or turn on Group by status to see your leads under one heading per status, in list order, each with the number of leads that match your filters. Leads whose value is not in the list come last, under “Not in the list”.

For developers

Read and replace the list with the Statuses API. In the API, gray is grey. Sort leads in list order with sort_by=status. The TypeScript and Python SDKs read and replace the same list. On the Claude connector and the classic MCP endpoint, the list_statuses tool reads it, so an assistant can set a status your workspace uses; the MCP overview has the details.