Lead Nurture Sequences

Lead nurture sequences automate staged follow-ups for leads that are not yet ready to convert.

Goals

Column	Type	Notes
`tenant_id`	uuid FK → tenants
`name`	varchar(255)
`status`	enum	`draft` \| `active` \| `paused` \| `archived`
`entry_rules`	jsonb	Segment + score + status-based conditions
`exit_rules`	jsonb	Reply/conversion/disqualification/inactivity rules
`created_by`	uuid FK → users

Column	Type	Notes
`tenant_id`	uuid FK → tenants
`sequence_id`	uuid FK → lead_nurture_sequences
`step_order`	integer	1..N
`channel`	enum	`email` \| `task` \| `call_reminder`
`delay_hours`	integer	Delay from previous step
`template_id`	varchar(255)	Nullable for non-message steps
`requires_human_approval`	boolean	HITL gate for this step
`conditions`	jsonb	Conditional execution rules

Column	Type	Notes
`tenant_id`	uuid FK → tenants
`lead_id`	uuid FK → leads
`sequence_id`	uuid FK → lead_nurture_sequences
`current_step_order`	integer	Current pointer
`status`	enum	`active` \| `paused` \| `completed` \| `exited`
`enrolled_on`	timestamptz
`next_step_on`	timestamptz	Scheduler pickup timestamp
`exit_reason`	varchar(255)	Nullable until exited

A lead can be auto-enrolled when all are true:

Manual enrollment is also allowed from CRM lead detail.

Steps execute in order with delay_hours between steps
Each step checks lead state again before sending/executing
Exit immediately on conversion, disqualification, explicit unsubscribe, or positive reply
Pause when a human task is pending or approval is required

Messages generated by agents must pass human approval when requires_human_approval = true
Pre-approved templates can run without per-step review when tenant policy allows it
Respect opt-out and contact frequency caps
Stop all sequences for leads marked as do-not-contact

The following activity types provide full traceability: