Lead statuses

Every lead sits in a status — the stage your team has it at. Each workspace defines its own list in Settings › Leads (/settings/leads): add statuses, rename them, recolour them, put them in the order you work in, and delete the ones you don't use. The Inbox status picker, the Inbox and Dashboard filters, the lead pipeline on the Dashboard and every agent's Leads page all read the same list.

Owners and Admins manage the list; Editors can still move a lead between statuses from the Inbox.

The built-in statuses

A workspace starts with five statuses. Workspaces that existed before statuses became editable got exactly these, so no lead changed status and every report kept its numbers:

Key	Label	Counts as	Notes
new	New	Open	New leads start here
qualified	Qualified	Qualified
contacted	Contacted	Qualified
won	Won	Won
lost	Lost	Lost

While a built-in label is unchanged, everyone sees it in their own interface language. Once you rename it, everyone sees your label exactly as you typed it.

What a status means

Names are yours; reports never read them. Each status instead has a meaning, one of four:

• Open — still being worked on.
• Qualified — a real opportunity.
• Won — became a customer.
• Lost — will not buy.

The Qualified total on an agent's Leads page counts every lead whose status means Qualified or Won. With the built-in statuses that is qualified, contacted and won — the same number the page showed before statuses became editable. A status you add, such as "Demo booked" with the meaning Qualified, is counted the moment you save it.

Rules the editor keeps

• One status receives new leads, and it must mean Open. Tick New leads start in this status on another open status to move the default; the default itself can't be switched off or deleted.
• At least one status means Open.
• Deleting a status moves its leads first. The delete dialog shows how many leads have the status and asks which status they move to.
• Labels are unique within a workspace, up to 60 characters. Colours are #RRGGBB codes; the preview follows what you type.
• A workspace can have up to 30 statuses.

Keys never change

When you add a status, PoriFyx Chat derives a key from its label — "Proposal sent" becomes proposal_sent (a–z, 0–9 and underscores; a number is appended if the key is taken). Leads store the key, and the key is what integrations receive, so it stays the same when you rename the status. The key is shown next to each status in the editor.

Webhooks, Zapier and exports

Everything that sends a lead out keeps sending the key and adds the workspace's current label:

• The lead.captured webhook — what Zapier, Make and n8n catch — carries lead.status (the key) and lead.status_label. See Outgoing webhooks.
• Conversation exports have a lead_status and a lead_status_label column (CSV) or field (JSON).
• GDPR data exports list each lead's status and status_label.

Map your CRM fields on the key: it survives renames. Use the label for anything a person reads.

Upgrading an existing install

Two migrations ship the feature: create_lead_statuses_table adds the lead_statuses table, and seed_default_lead_statuses gives every existing workspace the five built-in statuses. Leads are not touched. If a workspace had leads with a status outside the five, that value becomes an extra status of its own (meaning Open, label made from the key), so those leads keep their status. Workspaces created later get the built-in statuses on creation.