V1 to V2 Lead Workspace Parity
What the V2 lead workspace preserves now and the exact dependencies for remaining V1 lead-list tools.
V1 to V2 Lead Workspace Parity
Clean Estimate V1 remains the feature and workflow baseline for V2. The only approved estimating removal is the multi-step wizard navigation; it does not authorize removing lead-management features.
The current V2 Pipeline release restores the real-data Board, All leads, Map, Follow-up, and Sources views; search; stage, rep, source, segment, activity, location, and created-date filters; sorting; pagination; CSV view export; responsive cards/table; new/open lead actions; and guarded stage changes. Structured address and appointment controls remain V2's safer replacement for typed address/time shortcuts.
The following V1 tools are still required. They were not silently removed and are not represented by placeholder controls.
| Remaining V1 tool | Missing V2 dependency | Smallest safe follow-up slice |
|---|---|---|
| Client-tag filter and shared tag labels | Tenant-scoped client tag schema, client/tag service, and a location-scoped lead-to-client-tag read join | Add tag storage/service first, then multi-select tag filtering to All leads and mobile cards |
| AI lead score and tier filters/columns | Versioned scored-lead record with model/reason metadata, authorization, recalculation service, and stale-score policy | Add read-only score/tier projection after the scoring service is approved; do not calculate scores in the browser |
| Automation enrollment from selected leads | Tenant workflow definitions, enrollment service, idempotent run records, permissions, and monitoring | Ship the automation engine/enrollment API, then add selected-lead enrollment with per-record results |
| Bulk stage change | Transactional, permission-aware bulk mutation that runs the normal stage guard for every lead and collects a required lost reason | Add selection plus a bulk service returning individual success/failure; never issue uncoordinated browser mutation loops |
| Bulk rep assignment | Transactional bulk mutation that reuses member activity, role, and location-scope validation for every lead | Add selection plus a scoped bulk assignment service with per-record results |
| Estimate-count column/filter | Organization/location-scoped estimate aggregate keyed by lead, including an agreed archived/draft counting rule | Add the server aggregate and indexed query before exposing the filter |
| Multi-select job-type filter | Normalized requested-service relation for a lead; segment only means residential/commercial and must not be overloaded | Add requested-service storage and edit flow, then expose multi-select filtering |
| Saved lead views | User- or organization-scoped saved-filter preference model, ownership rules, and rename/delete service | Persist the existing filter contract after ownership and sharing behavior are approved |
| Unified activity details and date | A secured activity read model across lead changes, notes, messages, estimates, and appointments | Add the activity projection, then replace updated_at-only list context where richer activity exists |
Lead notes, deposit/payment summary, and broader lead-detail editing also remain tracked under the lead-detail parity work. Forecast and weighted-pipeline values remain deferred until an approved probability model and reporting service can produce them from durable data; V2 will not invent them in the UI.
Related articles
Was this article helpful?
Still need help? Contact support