Lead Overview

What a Lead Is

A Lead in TrackDrive represents a consumer the company
intends to contact or attribute. Leads enter the platform
through several paths: API submission (POST /api/v1/leads),
CSV bulk import (/leads/import), ping/post integrations,
and generation from inbound calls. Once a Lead exists, a
schedule (or off-hook instant-agent pipeline) can dial it,
send SMS, post it to external systems, and route it into
the outbound queue.

Leads are stored per-company. Each lead belongs to an owner,
which is either an Offer or a Schedule, and carries a phone
number, an optional email, a status, opt-out flag, state,
country, timing fields (expires at, next action at, last
action at, schedule ended at, etc.), and a set of rollup
counters for calls, conversions, and costs.

Lead Status

The permitted status values are: scheduled, waiting,
running, queue, success, completed,
completed_attempted, completed_connected,
completed_converted, completed_with_one_call,
completed_with_many_calls, exceeded_max_calls,
exceeded_short_calls, dnc, failure, disabled,
blocked, opt_out. A separate wait status tracks
transient waits such as waiting_call_disposition.

Lead vs Contact

A Contact is the per-phone-number dedupe record. A Lead
is an instance of campaign intent. The same phone number
can produce many Lead rows across different offers and
schedules, but all of them share a single Contact per
company. Suppression, blacklist, and cross-campaign state
live on the Contact. See the Contacts article for reference.