Leads
Lead Statuses
Understanding the different lead statuses in LeadSail.
Leads move through 22 possible statuses that represent their lifecycle from submission to final outcome. Statuses are shared between leads and submissions.
| Status | Description |
|---|
new | Lead was imported via CSV or created directly — not yet submitted for processing |
pending | Submitted to the qualification engine, waiting to be picked up |
processing | Engine is actively evaluating the lead |
| Status | Description |
|---|
qualified | Passed all qualification checks (DQ conditionals, required fields, field qualification) |
disqualified | Failed one or more qualification checks |
| Status | Description |
|---|
queued | Delivery deferred because a cap was hit or the current time is outside the delivery schedule |
pending_action | Waiting for a first submission action to complete (voice call, SMS, human review, or webhook) |
These statuses indicate ongoing contact attempts, typically from voice AI or SMS agents:
| Status | Description |
|---|
no_answer | Call attempt was not answered — will retry |
voicemail | Voicemail was left — will retry |
contacted | Lead was reached but conversation is not yet resolved |
scheduled_callback | Lead requested a callback at a specific time |
| Status | Description |
|---|
no_contact | Auto-dialer exhausted all configured attempts without reaching the lead |
| Status | Description |
|---|
pending_signature | A document requiring signature has been sent to the lead |
document_sent | A document not requiring signature has been sent |
signed | The lead signed the document |
| Status | Description |
|---|
delivered | Lead was successfully posted to the client's endpoint |
accepted | Client confirmed acceptance of the lead |
duplicate | Client reported the lead as a duplicate |
failed | Delivery attempt failed (endpoint returned an error or rejection) |
error | System or technical error occurred during any processing phase |
| Status | Description |
|---|
rejected | Client rejected the lead, or it was manually rejected by a user |
dnc | Lead is marked Do Not Contact |
Statuses generally flow forward through the lifecycle, but some transitions can move backward:
- A
queued lead re-enters processing when its schedule window opens or the cap resets
- A
no_answer or voicemail lead returns to the auto-dialer queue for retry
- A
delivered lead can be manually reposted, creating a new submission that starts at pending
Users can manually change a lead's status from the leads list (inline editing) or the lead detail page. Manual status changes do not trigger engine reprocessing.
When a campaign uses a human review first submission action, the lead enters pending_action with an approval object:
pending — Awaiting reviewapproved — Reviewer approved, processing continuesrejected — Reviewer rejected, lead is marked rejected
Approval can be done from the lead detail page or via the POST /api/v1/leads/{leadId}/approve API endpoint.