Sales Pipeline

Work leads from first contact through won or lost using the V2 board, lead list, map, follow-up, and source views.

Beginnerownermanagersales repUpdated 2026-09-24

Sales Pipeline

Open Pipeline under Work in the Clean Estimate V2 sidebar. The workspace keeps the useful V1 lead controls while using V2's location-scoped data, structured appointment fields, managed lead sources, and guarded stage-change service.

Use Pipeline to select the active sales process and Location to show one location or every location you are authorized to see. The header totals are calculated from the leads loaded for that pipeline and location; they are not sample data.

The pipeline report is a date-range cohort across all pipelines, including archived leads, grouped by current stage. The board is the selected pipeline's current unarchived view, so its value need not equal the report total. This clarification does not change either calculation.

Views

Board

Board is the existing stage workspace. Each column shows its live lead count and stored pipeline value. A card shows the customer, lead number, service address, value, idle age, and structured appointment when those values exist.

Use the stage selector on a card to move the lead. Moving to a protected terminal stage can require a reason; V2 saves that reason through the same guarded stage service used by the lead detail page. If you switch pipelines or locations while a stage change is still finishing, CE Pro discards any delayed reason prompt or error from the old board instead of letting it act on a lead that is no longer visible. Select the customer area of a card to open the full lead.

All leads

All leads is the complete list view (called List in early design prototypes). Desktop uses a table and mobile uses compact cards. Both keep the same customer, address, source, assigned rep, appointment, activity, value, and stage context. The view shows 25 leads at a time with Prev and Next.

An Estimates column shows a bounded count of every estimate attached to that lead, in any status. This is V1's own lead-list behavior: V1 has no estimate-count filter, only this count column, so V2 does not add one either. The count also appears on the mobile card and in the CSV export.

Map

Map plots only leads whose saved service property contains valid persisted latitude and longitude. CE Pro never adds a sample pin or guesses a location. If no filtered lead has coordinates, the page explains why the map is empty. If Google Maps is unavailable, the saved location list remains available without inventing map data. After a temporary loading or connection failure, select Retry map to recreate the map and load the saved pins again.

Select a marker or its matching location row to open the lead.

Follow-up

Follow-up shows non-won, non-lost leads whose last saved activity is more than seven days old. The selected Sort order is preserved in both the visible queue and its export. Stage, location, and the other active filters still apply, so this can be used as a rep- or location-specific callback queue.

Sources

Sources groups the filtered leads by their actual managed or retained legacy source. Each card shows the real lead count, share of the filtered result, and stored pipeline value. Unattributed is shown explicitly instead of assigning an unknown lead to a source. Select a source card to open All leads filtered to that source.

Search, filters, and sorting

Search matches the saved customer name, lead title fallback, lead number, service address, source, location, and assigned rep. Combine it with:

  • current pipeline stage
  • assigned rep, inactive or role-changed historical rep who still owns a loaded lead, or Unassigned
  • managed source, archived source retained on older leads, or Unattributed
  • residential or commercial segment
  • one or more shared customer tags, matching any selected tag
  • last activity: 0–7 days, 8–30 days, or more than 30 days
  • exact created-from and created-to dates, interpreted in each lead's saved service-location timezone

Sort by recent or oldest activity, value high or low, customer name, or soonest appointment date and start time. Clear filters restores the default view. The live result label always shows the filtered count and the total loaded lead count. Saved tag pills also appear on lead cards and rows. The selected tag filter is applied to every Pipeline view and the server-authorized CSV export.

Saved views

Save the current filter set on All leads so you do not have to rebuild it every time. Give it a name, then Save, Apply, Rename, or Delete it from the saved-views list. A saved view is scoped to the member who saved it; there is no shared or organization-wide saved view yet.

Saving and reopening a view preserves its selected AI lead-score tier. Assigned lead cards and rows show the teammate's name or email when available. If a saved assignee is missing from the current member directory, CE Pro shows Assigned team member rather than Unassigned or an internal identifier. Unassigned means no sales representative is saved on the lead.

Bulk actions

Select one or more leads on All leads with the row checkboxes to open a bulk action bar:

  • Change stage moves every selected lead through the normal guarded stage

service, one lead at a time inside one transaction. Moving to a protected terminal stage still asks for one reason that covers the whole batch. A rep without Move others' cards can only bulk-act on leads assigned to them.

  • Assign rep reassigns every selected lead to the chosen teammate the same

way.

  • Enroll in automation opens the same automation enrollment dialog V1

used, listing the workflows the selection is eligible for, then enrolls each lead individually through the existing manual-enrollment engine.

Each bulk action reports a real per-lead result — how many moved or were assigned, and how many failed and why — rather than a single pass/fail message for the whole batch.

Job type filter

Filter All leads by one or more requested services (job types), matching any selected type. The same filter is available on the board and mobile, and the CSV export includes the selected job types. Edit a lead's requested services from a chip editor on the lead detail page.

Activity feed

Each lead's detail page shows a single, newest-first activity feed instead of only a last-updated timestamp: every stage move, rep reassignment, and manual note lands in the same feed, paginated 200 rows at a time. Use Log activity on the lead detail page to add a manual note; V1 called this same action Log activity, and V2 never had a note-only entry until this release.

Exporting the current view

Members with the Export data permission can select Export view to download the exact filtered rows as CSV. The server checks that permission on every export, so revoking it takes effect immediately. The export includes lead number, customer, service address, stage, source, assigned rep, segment, appointment date, value in cents, and last activity. Follow-up exports contain only the current follow-up queue.

Creating and opening leads

Select New lead to use the same V2 creation form as before. It requires a real customer and service property, keeps the currently selected pipeline, uses the managed source and assignable-rep rules, and offers calendar and time controls for an appointment. After creation, CE Pro opens the new lead detail page. While the request is saving, the form is locked so the submitted client, property, location, source, and assignment cannot drift. If the response is lost, Try again replays the same request identity and returns the original lead rather than adding a second card or activity. A fresh New lead action is a new intent. If a recovery attempt receives a session or role rejection, the submitted details stay locked because that response cannot prove whether the first request already saved; use Try again to recover it, or choose Start new lead only when you accept that a duplicate may be created. No lead action has been replaced with a decorative prototype control.

Remaining V1 lead-workspace parity

Saved views, bulk automation enrollment, bulk stage/rep changes, the job type filter, the estimates count column, and the unified activity feed all closed in this release. Two items remain open:

  • AI lead score and tier still needs W39's scored-lead model before a

read-only score/tier column or filter can be added here.

  • Weighted Pipeline is not shipped. See

Sales Pipeline stage metrics below for what V1's forecast needs that V2 does not have yet.

See V1 to V2 Lead Workspace Parity for the exact dependency on the one remaining item.

Stage metrics and forecast

Board column totals, All leads, and the Sources view all compute their counts and values from the leads actually loaded for the selected pipeline and location; none of it is sample data.

V1's pipeline also showed six stat cards: Open Pipeline, Weighted Pipeline, Active Deals, Won, Win Rate (90d), and Avg Days to Close. Five of those six already compute from existing stage data. Weighted Pipeline does not exist in V2 yet — it needs a per-stage win-probability value, and pipeline_stages has no such column today. Do not read a weighted or probability-adjusted total anywhere in the current V2 pipeline; only the plain stage/value rollups described above exist.

Was this article helpful?

Still need help? Contact support