Lead pipeline (Kanban + scoring)
The lead pipeline is a drag-and-drop board where each column is a stage (New → Contacted → Qualified → Converted, or whatever stages you configure). Lead scoring ranks leads automatically based on profile and activity so reps work the hottest prospects first instead of working the list top to bottom.
View the board
Go to CRM → Leads. Switch to the Kanban view to see every lead grouped by stage, or use the list view when you need to sort and filter a large volume of leads.
Move a lead forward
Drag a lead card from one stage to the next as you make progress. The stage change is timestamped on the lead’s timeline, so managers can see exactly how long a lead has sat in each stage.
Let scoring prioritize
Lead scoring rules (configured in CRM → Settings) assign points for company size, engagement level, and email opens, among other signals. The Lead Qualifier AI agent can also propose a score and the next best action for a given lead — you decide whether to act on it.
Convert to a deal
When a lead is qualified, click Convert to spin up a Deal (and optionally an Account + Contact) with all captured data carried over automatically. The original lead is marked converted and linked in the document chain, so nothing is entered twice.
Fields on a new lead
| Field | Required | Values | Notes |
|---|---|---|---|
| Title | ✅ | text | The deal title you will carry through conversion |
| Stage | ✅ | your configured open lead stages | Closed stages are filtered out — you cannot create a lead that is already lost |
| Value | ✅ | number ≥ 0 | |
| Currency | ✅ | ISO code | |
| Probability | ✅ | 0–100 | Defaults from the stage; falls back to 20 |
| Priority | ✅ | low, medium, high, urgent | |
| Contact | conditional | contact reference | Required only when you arrive from a contact or account |
| Owner | — | sales rep | Defaults to you |
| Lead source | — | inbound, outbound, referral, partner, event, web, social, cold call, email, other | |
| Expected close date | — | date | |
| Referred by | — | account | Appears when source is referral |
| Description | — | text |
Fields on a new deal
| Field | Required | Values | Notes |
|---|---|---|---|
| Title | ✅ | text | |
| Stage | ✅ | your configured open deal stages | |
| Value | ✅ | number ≥ 0 | |
| Currency | ✅ | ISO code | |
| Probability | ✅ | 0–100 | |
| Priority | ✅ | low, medium, high, critical | |
| Expected close date | conditional | date | Required when Deal close date required is on |
| Contact / account | conditional | reference | Required when Require account on deal is on; the contact must be an organization or belong to one |
| Owner | — | sales rep | |
| Deal source | — | website, referral, event, partner | A lead source of web becomes website on conversion |
| Notes | — | text |
Priority does not use the same values on both forms. A lead’s top priority is urgent; a deal’s is critical. Converting a lead does not translate between them, so a filter or report that expects one value will not match records created on the other form.
The 7 tabs on a deal
Like contacts, the deal tab is in the URL: /crm/deals/:id?tab=commerce.
| Tab | URL | Shows |
|---|---|---|
| Overview | ?tab=overview | Fields, stage, inline edit |
| Activity | ?tab=activity | Timeline, with a count badge |
| Tasks | ?tab=tasks | Linked tasks |
| Commerce | ?tab=commerce | Quotations raised from this deal, CRM and service contracts, and the full document chain |
| Approvals | ?tab=approvals | Approval state; badged when the deal is awaiting approval |
| History | ?tab=history | Every stage move, with reason |
| Files | ?tab=files | Attachments |
The whole deal page sits behind deals:read, so unlike contacts there are no per-tab permission gaps — if you can open the deal, you can see all seven tabs.