# Describe your follow-up once. Luca runs it for every lead.

Describe the follow-up flow you already run in your head. Luca builds it, runs it for every lead who fits, and stops the moment they reply.

Last updated: 2026-08-10

- On every plan
- AI-drafted or templated
- Review before it sends

## From a sentence to a running flow.

The setup is describing what you want. Everything after that -- building, simulating, and running -- happens while you coach.

1. **Describe the flow** (you). Pick a template or type what you want in a sentence: 'after a lead asks about the cohort, wait three days, then send the early-bird note and book the call if they reply.'
2. **It builds the canvas** (Luca). Triggers, waits, branches, and actions appear as connected cards you can drag, reorder, and edit -- or leave exactly as drafted.
3. **Simulate and review** (you). Run a simulation to see which path each lead takes, preview every message, and check the drafts in your review queue before anything sends.
4. **It runs, adapts, and stops** (Luca). The flow runs for every lead who fits, branches on their replies, waits and reschedules, and stops the moment the thread resolves.

## The sequence you'd run by hand, running itself.

The difference between a setter and a follow-up schedule is that a setter remembers, adapts, and stops when the lead replies. Automations do the remembering and adapting; you keep the judgment.

### A canvas, not a coding project

Triggers, waits, branches, and actions are visual cards you connect by dragging. The shape of the flow is the shape of the conversation you'd run by hand: lead enters, wait, ask, branch, book, stop.

- Drag-and-drop cards, no syntax to learn
- Luca drafts the flow from one line of description
- Every step is editable after the fact

### Waits that read the room

A flow can wait days, until a set time, until the lead replies, until an event happens, or until a condition is met. A lead who answers early skips straight to the next step instead of getting an automation that forgot they replied.

- Wait for reply, for an event, or for a date
- Early replies move the flow forward immediately
- Branch on what the lead actually said

### Actions that close the deal, not just chat

Steps aren't limited to sending messages. An action can book a call into your calendar when a lead qualifies, update the lead's record, or fire a webhook to your CRM or spreadsheet. The automation runs the whole job, not just the copy.

- Booking actions offer real openings
- Webhook actions push to your stack
- Lead-update actions keep records current

### Built by Luca, tuned by you

Describe what you want in a sentence and Luca drafts the whole flow. Open the template campaigns, edit them to fit your business, and simulate a run before it ever touches a real lead. Your judgment on top of the speed.

- AI-drafted flows from a one-line brief
- Template campaigns for the sequences coaches run most
- Simulate before you ship, review before it sends

## Three flows a setter would run by hand.

Each one is a real sequence that takes a setter an afternoon to remember and a coach an evening to forget. An automation runs them on schedule.

### The launch sequence

A new cohort opens in three weeks and every lead who's asked about it should hear the right message at the right moment.

One flow: lead enters, wait a week, send the early-bird note, branch on reply, book the call when they're ready. It runs the whole launch without a single copied-paste message.

### The re-engagement nudge

A lead went quiet three weeks ago and the thread is sitting dead in your inbox.

A flow waits until the conversation's been silent for 21 days, sends one nudge in your voice, waits for a reply, and stops the moment they answer.

### The comment-to-DM follow-through

A comment on your post becomes a DM, but the commenter goes quiet after the opener.

The flow continues where comment-to-DM left off: a branch on their first reply, a wait, a gentle follow-up, and a booking action when they qualify.

## A reminder note to yourself vs. a flow that runs.

Most coaches' follow-up is a mental note and a copied-paste message. Here's what that leaves on the table.

### A note to follow up

- It lives in your head, and dies with your week. The follow-up you planned on Sunday is gone by Thursday, buried under three new conversations.
- It's the same message to everyone. The webinar lead, the price-asker, and the one who ghosted get the same copy, because writing five versions by hand is more work than one.
- It stops when you forget, not when the lead answers. A lead who replied at 11pm still gets the automated nudge at 9am, because nobody's watching the thread.

### An automation, running

- It runs on schedule, every time, for every lead. Three touches, spaced by days, generated once at the start so they build on each other -- not three copies of the same message.
- Different leads, different paths. A branch sends the price answer to the price-asker and the recap to the webinar lead, each on their own path.
- It stops when the conversation does. The lead's reply ends the wait, moves the flow on, and cancels every touch still scheduled -- no nudge to someone who just answered.

## Every block a flow is built from.

A flow is a canvas of connected cards. These are the cards, and what each one can be set to.

| Block | What it does | What you can set |
| --- | --- | --- |
| Trigger | Starts the flow when something happens | A comment, a DM on any channel, a story reply, a CSV import, a webhook, a CRM event, a booking change, or a lead going silent |
| Wait | Holds the lead where they are | A duration, a clock time in a timezone, until they reply, until an event, or until a condition is true |
| Branch | Splits the path on what the lead said or did | Equals, contains, in, greater or less than, before, after, exists, or missing |
| Message | Sends a reply in your voice | The channel, whether it is an opener, a follow-up, or a public reply, and the draft itself |
| Booking | Offers times and books the call | Your connected booking provider, and whether to send the link or offer slots |
| Lead update | Writes to the lead record | A tag, or a custom field and its value |
| Webhook | Tells the rest of your stack | A signed webhook to your own endpoint, a Zapier hook, or a Make hook |
| Control | Ends a path or holds it back | Goal reached, exit, cooldown, or merge back into the main path |

Every message a flow sends still lands in your review queue, unless you have turned auto-send on for that channel.

## The questions that decide whether you trust a flow.

Automation goes wrong in a handful of specific ways. These are the four, and what Luca does about each.

### What does a branch actually read?

The lead record and the conversation, through a plain comparison. A branch checks whether a field equals, contains, or is missing a value, whether a number sits above or below one, or whether a date falls before or after another. Each result routes the lead down its own path.

### Can one lead be in more than one flow?

Yes. Someone who comments on a launch post and then goes quiet can sit in the launch sequence and the re-engagement flow at the same time. Each flow tracks that lead separately, and each one stops on its own terms when the thread resolves or the goal is reached.

### How do I know a flow works before it runs?

Simulate it. The simulation walks a lead through the canvas and shows which path they take at every branch, with the message that would be sent at each step. You read the whole sequence before a single lead sees any of it, and edit any node you do not like.

### What makes a flow stop?

Four things end a path: the goal you set is reached, an exit node fires, a cooldown blocks another message for now, or the branch merges back and runs out of steps. A flow is finished with a lead the moment one of those hits. It does not loop back around.

## The details, for people who want them.

What a flow can trigger, wait on, branch on, and do -- and the guardrails around all of it.

- **Triggers.** A lead enters a flow from a channel, a comment, a list, or another automation. One lead can be in several flows.
- **Waits.** Pause for a duration, until a time, until the lead replies, until an event, or until a condition. Early replies end the wait.
- **Branches.** Route on what the lead said or did: interested, price question, not now -- each path with its own next steps.
- **Actions.** Send a message, book a call into a real calendar, update the lead record, or fire a webhook to your CRM or stack.
- **Webhook step.** An action step can call your URL and sign the payload with a stored secret, so your endpoint can verify the request came from Luca.
- **AI draft.** Describe the flow in a sentence and Luca drafts the whole canvas, ready to edit and simulate.
- **A/B testing.** Run one sales framework against another, or one objection strategy against another, on live conversations. Pick the metric (call booked, lead replied, lead qualified, or CRM deal won) and adopt the winner with one click.
- **Templates.** Ready-made flows for new-lead welcomes, comment-to-DM openers, and re-engagement nudges.
- **Review.** Every message the flow sends lands in your review queue unless you've turned auto-send on for that channel. Each automation can also require review or send on its own, independent of that global switch.
- **Safety.** Sends are paced at a human rhythm, honoring messaging windows, so a viral post never becomes a spam wave.
- **Plans.** Included on every plan. 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.

## Questions

### Do I need to know how to build this?

No. Every step -- trigger, wait, branch, action -- is a card you connect by dragging. Describe what you want in a sentence and Luca drafts the whole flow for you to edit, so building one is closer to writing a paragraph than writing code.

### How is this different from follow-ups?

Follow-ups is the ready-made version: three touches, spread over days, built in and automatic. Automations is the build-your-own version, for when you want a sequence that fits your exact business -- a webinar reminder, a launch sequence, a re-engagement campaign. Both feed the same review queue.

### Can it send messages without me approving them first?

Only if you turn auto-send on for that channel, and each automation can also require review on its own, independent of that switch. Off by default, same as everywhere else in Luca, and one tap to undo.

### What happens if a lead replies before the automation finishes?

The flow moves on. A wait like 'wait for a reply' ends the moment they answer, so a lead who replies isn't still getting messages meant for someone who stayed quiet. A branch can then route on what they actually said.

### Can I test different replies against each other?

Yes. Run one sales framework against another, or one objection strategy against another, on live conversations. Pick the metric you care about -- call booked, lead replied, lead qualified, or CRM deal won -- and adopt the winner with one click.

### Which plans include automations?

Included on every plan. 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

Draft your first automation in minutes. Connect a channel, pick a template or describe what you want, and Luca builds the flow. Simulate it, then let it run.

[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
- [Follow-ups](/features/follow-ups.md): Win back the leads who ghost
- [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
- [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