Lead Status

Lead Status Master - User Guide

1. Introduction 📝

The Lead Status Master defines the lifecycle stages through which a business opportunity transitions from initial discovery to closure. These statuses provide the foundation for sales pipeline velocity tracking, stage-gate forecasting, and conversion analysis.

â„šī¸

In the overall CRM flow:

  1. Tracks the progression state of each opportunity (e.g., Interested, Proposal Submitted, Under Negotiation, Converted, Dropped).
  2. Shapes the Lead Status Distribution donut chart on the Visual Dashboard.
  3. Groups columns dynamically in the Platform Summary and Salesmen Performance worksheets of the Lead Summary Report.

2. Getting Started 🚀

Accessing the Module

Navigate to CRM > Masters > Lead Status (/crmleadstatusmstindex).

The Index Page

The index provides a clear data grid displaying:

  • Status Code: Two-digit system or custom identifier.
  • Status Name: Stage label visible throughout the CRM pipeline.
  • System Created: Indicator specifying whether the status is a core built-in milestone or a custom user-defined stage.
  • Actions:
    • đŸ‘ī¸ View Details: Opens an inspect drawer with detailed status attributes.
    • âœī¸ Edit: Opens an inline modal to modify status labels.
    • đŸ—‘ī¸ Delete: Safely removes unlinked custom statuses.
  • Create New: Button navigating to the creation screen (/crmleadstatusmstcreate).

3. Features ✨

  • 🔒 System vs Custom Milestones: The system separates built-in core milestones (e.g., initial inquiry, final conversion, dropped) from custom interim business stages tailored to your sales process.
  • đŸ›Ąī¸ System Protection Lock: Core system-created statuses (SysCreated = "Y") are permanently protected to prevent breaking transactional workflows and pipeline logic.
  • 📊 Dynamic Report Integration: Adding a new custom status automatically incorporates it as an analytical column in the multi-tab Lead Summary Excel Report.
  • đŸ—‚ī¸ Slide-Out Details Drawer: Rapidly inspect record history and system flags without navigating away from the grid.

4. Complete Flow 🔄

Analyze Pipeline Stages

  • Map out your sales funnel milestones (e.g., Discovery Call, Product Trial, Budget Approval, Commercial Negotiation).

Create Custom Status

  • Open the Lead Status Index and click Create New.
  • Enter a concise, title-cased Status Name (e.g., Technical Feasibility).
  • Click Save. The system assigns the next sequential status code and marks it as a user-created milestone (SysCreated = "N").

Assign to Leads

  • When editing an active lead with recorded interactions, select the current pipeline stage from the Status dropdown.

Pipeline Reporting

  • Review the CRM Dashboard and Lead Summary Reports to observe how many opportunities reside in each status.

5. Validations and Error Handling âš ī¸

The Lead Status master incorporates critical system integrity controls:

Validation ScenarioWhat is checked?Error Message / System Behavior
System-Created Status LockBlocks attempts to modify or delete predefined core system statuses (SysCreated = "Y").“System-created status cannot be modified or deleted.”
Duplicate Status DetectionPrevents creating multiple status records with identical names.“Duplicate Status Name found.”
Referential Integrity Delete-LockPrevents removing any custom status that is currently assigned to one or more leads.“Master Record is live you can not delete this record.”
âš ī¸

âš ī¸ Crucial Transactional Interlock

While custom statuses can be selected at any point during active negotiations, transitioning a Lead to terminal milestones (such as Converted or Dropped) enforces that all scheduled activities must be marked as Done or Cancelled. You cannot close or drop a lead while pending tasks remain open!


6. Tools / Smart Features 🔧

  • ⚡ Modal-Driven Quick Edit: Modify custom status labels directly in an overlay dialog without leaving your search or filter view.
  • 📈 Zero-Code Report Expansions: The analytical engine reads status masters dynamically; new statuses immediately appear in reports without configuration changes.

7. Configuration Requirements âš™ī¸

  • Permissions: Managing lead statuses requires assigned security roles (CrmLeadDetails, CrmLeadCreate, CrmLeadDelete).

8. Best Practices 💡

  • Keep Stages Crisp & Mutually Exclusive: Maintain between 5 to 7 total pipeline stages. Too many micro-stages cause team confusion and reduce adherence.
  • Preserve Core Milestones: Rely on custom statuses for intermediary stages, and reserve the final converted and dropped statuses for concluding deals.