Lead Nurture Sequence
Slug: ai-lead-nurture-sequence · Category: Lead Capture & Booking · Provisioning: Requires AgentLane staff approval
Follows up with a lead four times over roughly two weeks, alternating SMS and email, and stops as soon as there is a reason to. The failure it prevents is the most common one in the funnel: a single follow-up, sent once, to someone who was simply busy that afternoon.
Required credentials
| Provider | Used for |
|---|---|
anthropic | Drafts each touch, given the history of the previous ones |
twilio | Sends the SMS touches |
resend | Sends the email touches |
cal_com | Reads real open appointment slots so a touch never offers a time that isn’t free |
Industry fit
Aesthetics, Dental, Home Services, Legal, Healthcare, Veterinary, Fitness, Accounting, Insurance, Construction, Solar, Real Estate — the consultation-booking verticals, the same fit as the Lead Qualifier this agent is the other half of.
How to deploy
Request it like any non-instant agent — see Deploy your first agent. Unlike the single-shot agents, you do not call this one per touch: AgentLane creates a sequence for the lead and then triggers the flow once per scheduled touch, on its own.
Flow
Sequence trigger ──► Look up client config ──► Load sequence state ──► Check availability (Cal.com) ──► Decide touch (code) ──► Draft touch (Claude) ──► Send SMS ──► Send email ──► Report touchWhy the schedule lives in AgentLane
An Activepieces flow has one trigger type, no wait step, and no memory between runs, so a flow cannot be a multi-day sequence — it can only ever be one touch. AgentLane therefore owns the cadence: it records each touch, decides whether there is another, and schedules it. The flow reads that state back at the start of every run, which is the only reason touch 3 can avoid repeating touch 1’s wording.
When it stops
- The lead replies or books — the flow reports it and the sequence closes.
- The lead texts STOP — the opt-out is checked before the flow is triggered at all, so no execution is spent and nothing is sent.
- The last scheduled touch is sent — the sequence completes.
Known limitation
A provisioned flow is a strictly linear chain with no branching, so both the SMS and the email step are always present and the one not being used for a given touch is handed an empty recipient. Those two steps are marked to not abort the chain, so the touch is still reported and the sequence still advances. This goes away once flows can branch.