# Win back the coaching leads who ghost you.

Luca reopens a quiet thread days later, in your voice, with up to three touches. Then it stops. Every message waits in your queue for your approval.

Last updated: 2026-08-10

- Only people who messaged you first
- Three touches, then it stops
- Ends the moment they reply

## What happens after they go quiet.

You don't schedule anything or build a sequence. The cadence starts itself when a conversation stalls, and it ends itself either way.

1. **A conversation stalls** (the lead). A thread that was going somewhere and stopped without an answer. A story reaction or a passing thumbs up doesn't count.
2. **Luca plans all three touches** (Luca). Written once, as a set, around what the lead said. Each touch has a job the one before it didn't.
3. **Each touch waits for you** (you). It lands in your queue on its day, checked against the channel's messaging rules before it's offered at all.
4. **They reply, or it stops** (Luca). A reply cancels the rest right away, and you never have to hunt down leftover drafts to delete them.

## Why these land instead of getting you blocked.

Everyone knows they should follow up. The reason nobody does it well is that doing it badly is worse than not doing it, and doing it well takes memory nobody has.

### Follow-ups that read like you remembered them

Luca waits the right number of days, then picks the thread back up around what the lead said: their goal, their question, their timeline. It reads like you remembered them, because Luca did.

- Spaced days apart, timed to feel calm
- Built around what that lead told you
- Written in your voice, like everything else

### It knows when to stop

A lead who says "not now" gets space. A lead who stays silent past a touch or two gets left alone. Luca follows up with the patience of a good setter, and stops with the same judgment.

- Backs off when a lead opts out
- Three touches, then it stops for good
- You can end any thread with one tap

### Runs while you coach

The leads most coaches lose are the ones from two weeks ago, buried under new messages and never followed up. Luca keeps every open conversation on its calendar, so a busy week doesn't cost you a client without you noticing.

- Every open conversation stays on the calendar
- Multi-day plans per conversation
- Drafts wait for your approval like always

### Three touches that build on each other

The whole cadence is written at the start, as a set, so the second touch says something the first one didn't and the third one is a clean last word rather than a fourth ask. If they reply at any point, the rest cancels.

- Each touch has a different job
- A reply cancels everything still queued
- No stale draft firing a week later

## Three ways a good lead goes quiet, and what reopens each one.

Three stalls every coach recognizes, and what a good follow-up does about each of them.

### "Let me think about it"

The most common way a good conversation ends. They meant it, and then life happened.

About a day and a half later, on the default cadence, the thread gets picked back up around what they were weighing, not your calendar. This is often the touch that turns a stall into a client.

### The price flinch

They asked the price, you gave it, and the conversation stopped dead in the same minute.

The follow-up doesn't repeat the number. It goes back to what they're trying to achieve and what the program does about it, which is what they were deciding in the first place.

### The lead from six weeks ago

A real conversation that stalled before you even signed up for Luca.

It surfaces in your first week with a touch drafted. Coaches often find their easiest close of the month sitting in a thread they'd forgotten about.

## The follow-up you've been sent before.

You know the difference from the receiving end. One of these makes you reply; the other makes you mute the thread.

### A follow-up sequence

- One canned line, sent to everyone who went quiet. "Just bumping this to the top of your inbox!" goes to the lead who asked about a payment plan and the one who never replied to anything, worded identically.
- Fires on a timer, no matter what the thread says. They replied yesterday about scheduling their first session, and the same nudge goes out this morning anyway because the clock hit day three.
- Manufactures urgency to force a reply. "Spots are filling up fast!" on a program that isn't capped and wasn't close to full. It reads as a lie the moment someone's coached before.
- One script for every stall, however different. The lead weighing a payment plan and the lead who never opened a real conversation get the same three messages in the same order.
- Keeps going until the lead mutes, blocks, or reports. A fourth and fifth message land after the third gets no reply, because nothing in the sequence was built to notice and stop.

### A Luca follow-up

- Picks up their actual goal, question, or timeline. "still the goal to be ready for June?", because that's what they said, not a generic check-in that could apply to anyone.
- Cancels the moment they reply, before it queues behind them. A reply on day two means the day six and day nine touches, on the default cadence, never get drafted, let alone sent.
- States a real deadline when there is one, invents nothing when there isn't. If there's a real deadline, like a cohort starting Monday, it says so. If there isn't, it doesn't invent one.
- Three touches, each with a different job. Pick the thread back up, answer what they were probably weighing, then close with a clean last word. Never the same message twice.
- Stops after the third touch and leaves them alone. No reply after day nine means Luca closes the cadence rather than sending a fourth message hoping this one lands.

## The rules a cadence runs under.

What triggers it, what stops it, and what it will never do.

- **Plans.** Included on Pro and Scale. What changes between plans is how many messages a month you get, plus what Starter leaves out: Voice tuned weekly from your newest DMs and Follow-ups that win back ghosted leads. All four channels are on every plan.
- **Who gets followed up.** Only people who messaged you first and whose conversation stalled without an answer. Never cold outreach, never imported lists.
- **Cadence.** Three touches on the cadence you pick. The default spaces them across about eight days, then stops for good.
- **Cadence templates.** Light spaces touches 3, 5, and 5 days apart. Standard, the default, spaces them 36 hours, 4 days, and 3 days apart. Aggressive spaces them 18 hours, 2 days, and 2 days apart.
- **When copy is written.** Luca generates all three touches once, at the start of the cadence, so they build on each other rather than repeating.
- **Approval.** Every touch lands in your review queue like any other draft, unless you've opted that channel into auto-send.
- **Cancellation.** A reply from the lead ends the cadence at once and cancels every touch still waiting.
- **Messaging windows.** A touch that would fall outside a channel's messaging window is held rather than forced through.
- **Opt-outs.** Anything that reads as "not interested" ends the cadence, and Luca remembers it on that conversation.
- **History.** Conversations that stalled before you signed up are eligible, based on the history Luca reads when you connect a channel.

## Questions

### Isn't this just automated spam with extra steps?

What makes a follow-up read as spam is the same line sent to everyone on a timer, forever. Luca does the opposite on every count: each touch is written around what that specific lead said, there are exactly three and then it stops, and only people who messaged you first are ever in a cadence. Nobody who never contacted you gets one, and nobody who replies gets a fourth message.

### Does Luca message people who never DMed me?

No. It only talks to people who reached out to you first -- a DM, a story reply, a comment. It never does cold outreach and never buys, scrapes, or imports contact lists.

### How many times will it follow up before it gives up?

Three touches, on the cadence you pick -- light, standard, or aggressive -- then it stops for good. A lead who never answers gets left alone instead of chased into blocking you.

### What happens if the lead replies partway through?

The cadence stops right away and the conversation goes back to normal. Luca cancels the remaining touches instead of queuing them up behind a thread that's already moving again.

### What if I'd rather write the follow-ups myself?

Then use Luca as a reminder system. The value is knowing which of last month's conversations stalled and are worth reopening -- the drafts are there if you want them, and skippable if you don't.

### Which plans include follow-ups?

Follow-ups start on Pro. Every plan reads, qualifies, and drafts replies to leads who are still talking; reopening the ones who went quiet is what Pro adds. What changes between plans is how many messages a month you get, plus what Starter leaves out: Voice tuned weekly from your newest DMs and Follow-ups that win back ghosted leads. All four channels are on every plan.

## Try it

The leads who went quiet are still leads. Luca reopens them for you. Connect a channel and Luca shows you which conversations stalled and are worth reopening, with the first touch drafted and waiting for you.

[Start free for 7 days](https://app.setluca.com/signup). Plans and prices are on the [pricing page](/pricing.md). SetLuca is the company behind Luca.

## Other features

- [Your voice](/features/voice.md): Replies that sound like you, learned from your DMs
- [Review queue](/features/review-queue.md): You approve every send. Auto-send is opt-in
- [Booking](/features/booking.md): From DM to booked call on your calendar
- [Channels](/features/channels.md): Telegram, Instagram, Messenger, WhatsApp in one queue
- [Comment-to-DM](/features/comment-to-dm.md): Turn post comments into qualified DM conversations
- [Automations](/features/automations.md): Build the follow-up flow once, then let it run
- [Broadcasts](/features/broadcasts.md): One campaign to every lead who's a fit
- [Ask Luca](/features/ask-luca.md): Your business questions, answered from your own data
- [Lead memory](/features/lead-memory.md): Every lead's history, remembered across channels
- [Analytics](/features/analytics.md): Know what's working before your gut does
- [Integrations](/features/integrations.md): Your CRM stays current, synced both ways
- [Inbound](/features/inbound.md): Every channel, one prioritized queue
