Pipeline Stages
The complete list of pipeline columns Aura tracks each lead through, in order.
Pipeline Stages
Aura's pipeline has 13 stages, derived at read time from each lead's call history. Stages are computed (not stored) — the underlying leads.status field exists for non-pipeline consumers (Zapier, partner API), but the pipeline view always recomputes the column from the lead's current call state.
Stages in display order
| # | Stage | Meaning |
|---|---|---|
| 1 | interested | Visitor started a booking flow (checked availability or selected a slot) but hasn't submitted contact info. |
| 2 | disqualified | Lead failed a disqualification rule on the booking form. Stays visible in the pipeline; DQ reason tracked for analytics. |
| 3 | qualified | Lead passed DQ rules and provided contact info but hasn't yet booked a call. |
| 4 | booked | Lead has a scheduled future call. RSVP is pending. |
| 5 | confirmed | Lead has a scheduled future call AND confirmed attendance (RSVP=yes). |
| 6 | declined | Lead declined the most recent call invite (RSVP=no or status=declined). |
| 7 | cancelled | The call was cancelled before it occurred. |
| 8 | attended | Lead attended their scheduled call (most recent past call). |
| 9 | unfit | Sticky state: lead was marked not a fit for the role on the most recent past call (post-call, not ICP). Cleared when the lead books a new call. |
| 10 | no_show | Lead didn't attend their scheduled call (guest no-show on the most recent past call). |
| 11 | follow_up | Sticky state: lead is awaiting a follow-up touchpoint. Cleared only by Won or Lost on a new call. |
| 12 | lost | Sales outcome: deal was lost on the most recent past call. |
| 13 | won | Sales outcome: deal was won (closed) on the most recent past call. |
Derivation rules
Stages are evaluated by derivePipelineStatus() in a fixed order — the first matching rule wins:
- Disqualified — if the lead failed a DQ rule, no further evaluation.
- Future booking call — if the lead has any scheduled future call, place by RSVP state (
booked,confirmed,declined). - Most recent past call — if a past call exists, place by its outcome (
attended,no_show,cancelled,won,lost, etc.). - Intent booking_stage — if no calls yet, place by where the visitor got in the booking flow.
- Fallback —
interested.
Some stages are sticky: once a lead enters follow_up, it stays there across new bookings until cleared by Won or Lost on the most recent call.
Related
- Pipeline overview — kanban board UI and how to manage leads
- Lead lifecycle — moving leads between stages manually