Skip to main content

The leads list

What this page is — the leads table: the screen most people have open all day, with its ten columns, its filters and its four tabs.

What it is for — finding a lead, seeing the state of the whole pipeline at once, and acting on many leads together.

The problem it solves — a lead database is only useful if you can get back to the right record. This page covers how to search and filter it, what each column is actually telling you, and the one column that shows something other than what it appears to.

Route: /org/marketing/leads (?tab=list) · Module: mkt_manage_leads — 53 permissions Permission to view: View Marketing Suites lead management

Four tabs share this route; this page covers the list.


1. What the list is​

A paginated table of every lead in the selected project, with ten columns and a filter rail.

ListBoardQueues
ShowsEvery lead, including ones with no statusOnly leads with a status in the chosen pipelineOnly leads in a queue
Sorted byNewest firstStatus column, then order within itQueue order
Best forSearching, filtering, bulk actionsSeeing progressClaiming the next call
URL?tab=list?tab=kanban?tab=queues
Figure 1 — 1 Queues · 2 List · 3 Kanban · 4 Create Lead.

2. The columns​

Figure 2 — Ten columns. Contact details of real people are blurred in this documentation; the legible rows are invented records.
#ColumnHoldsComes from
1PipelineThe pipeline namelead_pipelines — may be a pipeline this project cannot select
2Lead Name & DetailsFull name, with job title beneathfull_name, job_title
3Assigned QueueQueue name, or -lead_queues
4Contact InfoEmail above phoneemail, phone
5Source & OriginSource name with its iconThe configured lead sources
6Lifecycle StageStage chip, plus the score and a grade chiplifecycle_stage, lead_score
7OwnerAssigned user's display nameusers
8Lead GradeA grade chipComputed from the score — not the stored grade
9BudgetBudget range, or -budget_range
10ActionsView · settings · Delete—
Figure 3 — The header row, numbered to match the table above.
Grade and score are separate signals

The Lead Grade column shows the grade held on the lead. Scoring keeps it up to date automatically, and a grade you set by hand is treated as deliberate and left alone.

The difference between the two, and when each is worth using, is in status, grade and score.


3. Step by step — finding a lead​

The Search leads… box matches name, email, company and phone.

Filters​

Figure 3 — The filter rail. Every value is drawn from configuration, so an empty selector means nothing is configured.
FilterValues from
PipelinePipelines visible to this project
Stage / statusStatuses of the chosen pipeline
SourceThe active lead sources
OwnerUsers enabled as agents
GradeThe configured grades
Lifecycle stageThe five fixed lifecycle values
Only My LeadsA checkbox — leads owned by you
A filter that offers nothing is a configuration gap, not a bug

Every selector reads a configuration table. An empty Source filter means no sources are configured, not that filtering is broken.

Saved filters​

A filter combination can be saved and recalled from the toolbar.

Saved filters are personal

A filter you save is yours — it is not shared with the team and nobody else can change or remove it. Anyone who can view leads can save their own.

View modes​

The toolbar switches between list and grid (card) layouts, and offers a fullscreen toggle.

The view choice is remembered per project

View mode, fullscreen and the auto-refresh interval are stored and restored. If the list opens in an unexpected layout, that is why.

Auto-refresh​

The list can refetch on an interval. Useful on a shared queue; disruptive while reading, because rows reorder underneath you as new leads arrive.


4. Field reference — what the row tells you​

ReadingMeans
Pipeline populated, Lifecycle Stage chip present, no board positionThe lead's status belongs to a pipeline this project cannot see
Pipeline blankThe lead has no pipeline. Imported leads arrive this way
Owner blankNo assignment rule matched, or no agents are enabled
Score 0Normal. Scoring runs only on Recalculate
Grade chip disagreeing with the recordSection 2

5. The admin contract​

NeedsOr
A selected projectThe list is empty
View Marketing Suites lead managementAccess denied
Configured sources, pipelines, gradesFilters offer nothing
Enabled agentsThe Owner filter is empty

6. Downstream​

Bulk actions taken here affect the board, the queues and every report — see bulk actions. Exporting from here is server-side and honours the current filters, unlike the contact and deal exports.


7. The Analytics tab​

The fourth tab on this route is a compact analytics view, distinct from the Lead Analytics module.

Figure 4 — The in-page Analytics tab.
Two different analytics surfaces, two different permissions

This tab is part of mkt_manage_leads and needs only View Marketing Suites lead management. The five-report Lead Analytics module is org_lead_analytics with a permission per report. They show different things and are configured separately.


8. Don't confuse this with…​

ThisNot this
The Analytics tab on this pageLead Analytics and Reports
The Queues tab — working queuesQueue configuration
Lead Grade columnThe grade stored on the lead

9. Troubleshooting​

SymptomCause
List emptyNo project selected, or no leads in this project
Rows reorder while readingAuto-refresh is on
Grid layout on openView state is remembered per project
A grade differs from the recordThe column is computed. Section 2
Export has fewer rows than expectedLeads export is server-side and complete — the contacts export is not