ZenotiHelp

Lead pipeline and lifecycle overview

ZTZenoti Docs Team Updated November 3, 2026 6 min readGuide

The lead pipeline in AI Lead Manager defines how leads move from initial capture to final outcome. Each lead progresses through configurable stages that represent your sales process, with scoring to help prioritize the most promising leads.

How the pipeline works

Every lead in AI Lead Manager is assigned to a pipeline stage. Stages are ordered by display position and represent the steps in your sales process. As sales employees interact with leads β€” making calls, sending emails, scheduling follow-ups β€” they advance leads through the pipeline until the lead is won or lost.

The pipeline is configured at the organization level. All centers in your organization share the same pipeline stages, sources, types, and priorities.

Stage types

Each pipeline stage has a type that determines its role in the pipeline:

Stage type Purpose
Initial The entry point for new leads. Leads start here when first captured. The pipeline must have exactly one Initial stage.
Default Working stages where leads are actively being pursued. You can create multiple Default stages to represent your sales process steps.
Won A terminal stage indicating the lead converted to a customer. Leads cannot move out of this stage.
Lost A terminal stage indicating the lead did not convert. Leads cannot move out of this stage.

The pipeline must always have exactly one Initial stage and at least one Won and one Lost stage. The Initial stage is always first in the pipeline; Won and Lost are always last. Default stages can be reordered by their display order.

Users with the Reopen Leads permission can move leads out of Won or Lost stages back into the pipeline.

Stage configuration

Each lead stage is defined by the following properties:

Field Description
Name The display name for the stage.
Order The position of the stage in the pipeline sequence.
Code A unique code used to identify the stage.
Color A visual color chosen from 16 preset options to distinguish the stage in kanban and list views.
Description Optional free-text description of the stage's purpose.

Note: The Order field controls where a Default stage appears between the Initial and terminal stages. When you save a new stage, all subsequent stages shift down one position automatically.

Priority levels

Each lead is assigned a priority to indicate urgency. The five priority levels are:

  • Highest
  • High
  • Medium
  • Low
  • Lowest

Priority levels are centrally provisioned for the organization. They are distinct from the AI lead score priority label, which uses a separate Low/Medium/High scale based on the scoring model.

Call outcomes

Call outcomes (also referred to as dispositions) categorize the result of a logged call. They are managed under Lead Management > AI Lead Manager > Lead settings > Call outcomes and are used to record what happened at the end of a sales call β€” not to indicate whether a lead was won or lost. Won and Lost are determined by the stage type, not the call outcome.

Each call outcome has the following properties:

Field Description
Name The label displayed when logging a call.
Description Optional notes about when to use this outcome.
Follow-up Days The number of days (0–99) after which a follow-up reminder is automatically scheduled. A value of 0 means no automatic follow-up is scheduled.

Lead lifecycle

A lead's lifecycle includes these phases:

1. Capture

Leads enter the system through one of several channels:

  • Manual creation β€” A sales employee creates the lead directly in AI Lead Manager.
  • Platform integration β€” A prospect submits a lead form on Meta (Facebook) or Google Ads, and the lead is automatically captured.
  • Custom form submission β€” A prospect fills out a published lead capture form, and the lead is created automatically.
  • Expiry generation β€” The system auto-creates a lead when a guest's membership or package is approaching expiration.
  • API β€” An external system creates the lead through the API.

Each lead record tracks how it entered the system through its lead origin, which can be one of: manual entry, platform integration, import, or API.

2. Assignment and qualification

Once captured, a lead is assigned to a sales employee and enriched with context:

  • Assigned employee β€” The lead owner responsible for follow-up.
  • Source β€” Where the lead came from (tracks the acquisition channel).
  • Type β€” The category of inquiry or interest.
  • Priority β€” The urgency level for follow-up (Highest, High, Medium, Low, or Lowest).
  • Guest linking β€” The lead is automatically matched to an existing Zenoti guest profile, providing full guest history.

3. Engagement

Sales employees interact with leads through activities recorded on the timeline:

  • Add notes to document conversations and next steps.
  • Create tasks with due dates and due times for follow-up actions.
  • Log calls with call outcomes and duration.
  • Log emails to track communication history.
  • Attach files to notes for supporting documentation.

4. Progression

As the relationship develops, leads move through pipeline stages:

  • Manual stage changes by the assigned employee.
  • Automated stage changes triggered by automation rules (for example, moving to a conversion stage when the guest books a service or when a membership invoice is created).
  • Workflow-triggered actions such as sending follow-up emails or creating tasks.

5. Resolution

Every lead eventually reaches a terminal stage:

  • Won β€” The lead converted to a customer (booked an appointment, purchased a membership, etc.).
  • Lost β€” The lead did not convert (not interested, went to a competitor, unresponsive, etc.).

The lead's call outcome captures the specific result of the most recent interaction for reporting and analysis.

Lead scoring

AI Lead Manager includes a scoring system that ranks leads by their likelihood of conversion. Lead scores are computed automatically based on lead activity and attributes, and displayed alongside each lead to help sales teams prioritize their efforts.

The AI lead score card on a lead's detail page shows:

  • Overall score β€” A numeric score from 0 to 100.
  • Priority label β€” Low, Medium, or High (distinct from the lead's priority field).
  • AI Reasoning β€” A plain-language explanation of why the score was assigned.
  • Intent β€” The detected intent signal from lead activity.
  • Confidence β€” The model's confidence in the score.
  • Signal Breakdown β€” Seven contributing signal categories: Explicit intent, Booking flow, Time references, Engagement depth, Contact signals, Source context, and Deferred negative.

A Needs Human Review banner appears when the AI confidence is low.

Lead scoring is a display-only feature β€” scores are computed by the system and cannot be manually configured.

Availability: AI lead scoring requires both the org-level and center-level AI scoring toggles to be enabled. The org-level toggle must be enabled before the center-level toggle becomes available.

Lead fields

Each lead record captures the following information:

Field Description
Name The lead contact's name.
Description Free-text description of the lead.
Assigned To The employee responsible for the lead.
Stage The current pipeline stage.
Source Where the lead originated.
Type The classification of the lead.
Priority The urgency level: Highest, High, Medium, Low, or Lowest.
Listed Price The listed price of the product or service.
Offered Price The price offered to the lead.
Follow-up Date The next scheduled follow-up date.
Expected Close Date The target date for closing the lead.
Last Contacted Date The most recent date of contact (calculated from activity).
Center The center the lead belongs to.
Disposition The call outcome recorded when a call is logged.

Pipeline analytics

The dashboard provides visibility into pipeline health:

  • Overview β€” Shows five key metrics: Total leads, Open leads, Conversion rate, Revenue generated, and Leads at risk.
  • Lead to win progress β€” Shows how many leads are at each stage, the estimated funnel value, and where the highest drop-off occurs.
  • Lead source distribution β€” Reveals which lead sources drive the most leads and conversions, and highlights best conversions.
  • Lead capture trends β€” Tracks lead volume over time, including peak day capture and average new and returning leads.
  • Agent leaderboard β€” Ranks employees by performance to identify top performers.
  • Center performance β€” Compares pipeline metrics across centers for multi-center organizations.
Was this article helpful?
Your feedback helps us improve our documentation.