Skip to content

Pipelines and stages

A pipeline is a business process, not a sales funnel. Name it after what you actually do — "Property Enquiries", "Admissions", "Service Requests" — define its stages, and say what it carries.

This is the backbone. Leads and deals sit on a stage of a pipeline, and your reports are calculated from how they move.

Before you start

  • You need the tenant.pipelines.manage permission.
  • Decide your stages on paper first. Changing them later is possible but your team will have learned the old ones.

Steps

  1. Go to Settings → Pipelines.
  2. New pipeline, then give it a name and choose what it carries:
Carries Use when
Lead An enquiry process — before there is a sale to track
Deal A sale with its own value and close date
Both A small team that does not separate the two
  1. Add your stages in order. Each stage has a category:
Category Meaning
Open Just arrived, nobody has worked it
In progress Being worked
Waiting Blocked on the customer
Won Succeeded
Lost Did not succeed
Closed Finished, neither won nor lost
Archived Off the board
  1. Mark any stage that requires a reason. A lead moved into it must be given one — this is what makes lost-reason reporting possible at all.
  2. Save.

A new pipeline starts with six sensible stages (New, Contacted, Interested, Negotiation, Won, Lost). Rename or remove them.

Stages are not statuses

Both exist and they answer different questions:

  • A stage is where this lead is in your process. One at a time, it moves forward, and every move is recorded.
  • A status is a label about the lead itself.

If you only need one of them, use stages.

What this affects elsewhere

  • The pipeline board shows one pipeline at a time, as columns.
  • Reports — win rate, stage velocity, pipeline value — all read stage history.
  • Automation can trigger on a stage change and can move a lead to a stage.
  • A lead-only pipeline never appears where a deal is being filed, and the other way round. That is what "what it carries" decides.

What you cannot change later

Three things, each deliberate:

Nothing deletes a pipeline. You archive it. Leads keep pointing at the pipeline and stage they were on, because a report of last quarter has to still be able to name both. An archived pipeline disappears from the dropdowns and stays in history.

A pipeline carrying live leads cannot be narrowed to deal-only. Those leads would be stranded on a board that no longer admits them. Move them first.

Stage history is append-only. It is never edited or deleted — win-rate and stage-velocity figures are calculated from it, and a history somebody could tidy up is a history nobody can trust.

If it does not work

What you see What it means What to do
A stage will not accept a lead That pipeline carries deals only Check what the pipeline carries
"Cannot narrow usage" Live leads are on it Move them to another pipeline first
A move is refused The stage requires a reason, or that transition is not allowed The message says which
An archived pipeline still shows on old leads Expected Archived means hidden from new work, not erased

Last checked against the product on 2026-10-10. Needs the tenant.pipelines.manage permission.