How to automate follow-up so cold leads become jobs

May 28, 2026 · 7 min read

A practical, two‑week SMS + email + AI-call follow-up sequence you can copy to turn unresponsive leads into booked jobs.

Your leads filled the form. Then… silence.

You called once and sent an email. Nothing back. Another day passes and that inbound goes cold. The fix isn’t charisma—it’s a cadence you can actually run, every time.

Minutes matter, and most teams are late

Teams wait too long. An audit summarized by Harvard Business Review found average first response times on the order of days (~42 hours) while earlier outreach correlates with much higher qualification odds. Build for speed:

• Instant SMS and email on submission: acknowledge, set expectations, and include a booking link.
• First human touch within business hours: quick call or SMS reply with a single next step.

Concrete move: trigger an SMS + email within minutes, then queue the rest of the programmatic touches below.

A two‑week, multi‑channel cadence that converts service leads

Practitioner guidance repeatedly recommends 5–7 total touches across about two weeks for high‑intent inbound leads, mixing SMS, email, and voice to maximize contact and bookings (Gleantap). Here’s a working pattern you can copy. Send fewer touches if they book; stop immediately on a stop/opt‑out.

Day 0 (immediately)

• SMS (very short): “Hi [Name], got your [service] request. Want [Day/Time] or pick a time here: [link]. Reply YES to book.”
• Email (short): Subject: “Quick scheduling for [service]” Body: “Thanks for reaching out about [service] at [address/area]. We can do [two time windows]. Or grab any time that works: [calendar link]. Reply with a time and I’ll confirm.”

Day 1

• Email (slightly richer): Subject: “Estimate availability this week” Body: “We have openings [days/times]. Here’s what to expect on the visit: [2 bullets]. Book here: [link]. Hit reply with questions.”

Day 2

• SMS (nudge): “Still want the [service] looked at? I can hold [time]. Say YES and I’ll lock it in.”

Day 4

• Email (proof + CTA): Subject: “Similar job near you” Body: “We just completed a [brief description] in [nearby area]. Photos/notes: [link if you have it]. We can do an estimate [time window]. Book: [link].”

Day 6

• Human call attempt: Call once during business hours. If voicemail: “Hi [Name], this is [Rep] about your [service] request. I can do [time window]. Text me ‘YES’ and I’ll confirm, or use [link].”

Day 7

• AI voice attempt only if you have prior express consent for artificial/prerecorded voice calls (see compliance below). If not, skip the AI voice and send a human SMS instead. Script (if compliant): “Hi [Name], automated scheduling line for [Company]. We can do [time]. Press 1 to confirm or visit [short link].”

Day 10

• SMS (check-in): “Still need help with [service]? If not, reply STOP and I’ll close this out. If yes, want [time]?”

Day 12

• Email (value + choice): Subject: “Do you still want an estimate?” Body: “Two quick options: 1) 10‑min phone estimate; 2) On‑site visit [time window]. Pick 1 or 2, or book here: [link].”

Day 14

• Email or SMS (polite break‑up): “Haven’t heard back—okay to close this request? If you still want [service], reply YES and I’ll prioritize a slot.”

Why it works:

• Cadence fits the 5–7 touch guidance for inbound leads (Gleantap).
• SMS is short with a single CTA, email carries context and light proof, and voice attempts catch those who prefer a call.
• The final “okay to close?” message often triggers a quick YES from serious but distracted leads. Practitioners report better response from brief, trigger‑referencing messages and break‑up notes (Call The Damn Leads).

Mix AI and human touch without sounding robotic

Use AI for what it’s good at: speed, coverage, and routine answers. Keep humans for judgment calls and price exceptions.

• AI handles: after‑hours triage, answering common questions, capturing missing details, proposing time windows, and booking into your calendar.
• Human handles: unusual job scopes, sensitive pricing conversations, and anything that smells like a bad fit or safety concern.
• Routing rule: if a lead asks anything outside your FAQs or pushes back on scope, tag “needs human,” pause automation, and call.

If you don’t have this plumbing yet, Fluxaro builds 24/7 AI receptionists and follow‑up automations that answer, book, and log everything in one place. See what we build on our Services page.

The message types that get replies from cold leads

Practitioners keep repeating the same patterns because they win replies (Call The Damn Leads):

• Reference the trigger immediately: “You requested a [service] estimate on our site.” Keeps relevance high.
• One CTA per SMS, under ~25 words: “Reply YES for [time], or pick another: [link].”
• Light social proof in email: a one‑line micro‑case (“Finished [service] near [area] last week; photos here: [link].”).
• The break‑up: “Okay to close this?” Either gets a “not now” (disqualify) or a quick confirmation.

Copy you can reuse

• SMS templates
  • “Hi [Name], got your [service] request. Can do [time]. Reply YES to confirm or pick here: [link].”
  • “Quick check—still need [service]? I can hold [time]. Reply YES.”
  • “Haven’t heard back. Want me to close this request? Reply YES to keep.”
• Email subject lines
  • “Quick scheduling for [service]”
  • “Estimate availability this week”
  • “Do you still want an estimate?”

Tooling that makes this reliable (and compliant)

You don’t need a massive tech stack, but the pieces need to fit.

• Sequencer/CRM: Any tool that can send timed emails, hand off to SMS, and log replies. Tag the cohort you’re testing so you can compare booked‑appointment rates.
• SMS provider with U.S. 10DLC registration: Register your brand and campaign before sending business SMS at scale so carriers don’t filter your messages (Iterable).
• Calendar link: Give every message a direct way to book.
• AI assist: Use an AI agent to draft SMS/email replies and propose time windows; many teams wire this together with messaging APIs and LLMs. Combining APIs for automated SMS and AI‑supported replies is a common pattern in developer guides (Twilio).
• Deliverability setup: Verify sender domains, monitor bounce/blocked logs, and keep opt‑out handling automatic. Twilio’s onboarding/best‑practice material is a solid checklist for standing up verified senders and monitoring delivery (Twilio).

Operational notes

• Don’t duplicate the same content in SMS and email. SMS is for the decision and link; email carries extra context.
• Use local presence or recognizable caller ID for voice attempts.
• Always log every touch and outcome to the contact record to prevent over‑messaging.

Compliance you can’t ignore (AI voice, SMS rules, opt‑outs)

• AI voice calls are regulated: The FCC clarified that synthesized or AI‑generated voices count as “artificial or prerecorded voice” under the TCPA. You generally need prior express consent for those calls, and they’re subject to DNC/opt‑out rules (FCC Declaratory Ruling). If you don’t have documented consent, don’t use AI voice calls.
• SMS in the U.S. needs 10DLC registration and clear consent: Register your brand and campaign to avoid filtering and ensure throughput (Iterable). Use only opted‑in numbers, include opt‑out language (“Reply STOP to opt out”), and monitor complaints. Platform best practices also call for verified senders and delivery monitoring (Twilio).
• Email: Authenticate your domain (SPF/DKIM/DMARC) and match content to expectations set at capture. Keep a working unsubscribe.

What follow-up cadence actually works for service leads?

• Fast start, then 5–7 touches across about two weeks: immediate SMS+email, early email nudge, a couple of short SMS reminders, a human call, optional compliant AI voice, and a final break‑up (Gleantap).
• Stop as soon as they book or opt out. Don’t keep multiple channels going after a clear reply.
• Re‑open the thread only if they re‑engage later or request a callback.

How to blend AI with humans in the sequence

• After‑hours: AI receptionist answers, qualifies with three simple questions (problem, address/area, timing), proposes slots, and books.
• Business hours: human monitors a “hot leads” inbox; if AI marks “needs human,” call within the hour.
• Rules of engagement: if a thread includes price negotiation, safety, or unusual scope, pause automation and call. If a thread is routine (reschedule, address confirmation), let the AI handle it and log the outcome.

Which messages pull responses from cold leads?

• SMS with a single, easy reply path: “Reply YES to confirm [time]” wins more than open‑ended asks (Call The Damn Leads).
• Emails that reference the trigger and include a calendar link in the first screen.
• Light proof beats fluff: one photo/set of notes from a similar job in their area.
• A polite break‑up often gets a fast yes/no so you can either book or close the file.

Implementation checklist you can finish this week

• Configure your form/CRM to trigger an immediate SMS + email with a calendar link.
• Register for 10DLC (brand + campaign) before sending any volume SMS (Iterable).
• Add the two‑week sequence above as a reusable program in your sequencer.
• Add consent checks: only route AI voice calls to contacts with prior express consent (FCC Declaratory Ruling).
• Instrument results: tag leads enrolled in the new cadence, track booked‑appointment rate and time‑to‑book.
• Review three reply templates per channel and save them as snippets.

Faster first touch = more bookings

Teams that respond within minutes and then run a simple, two‑week, multi‑channel cadence close more of the leads they already have. The HBR audit shows how much most teams are lagging on first touch, and practitioner cadences show a manageable 5–7 touch rhythm that fits a small shop’s day (Harvard Business Review; Gleantap).

Next step: block 45 minutes to drop the sequence into your CRM and wire the immediate SMS+email. If you want us to build the plumbing and a 24/7 AI receptionist that books jobs for you, book a free 15‑minute call.