# One message to the right leads, written for each.

Reach every lead who fits a brief with one message written for each of them. You see the exact recipients before it sends, and you can pause it mid-run.

Last updated: 2026-08-10

- Personalized per lead
- Window-aware delivery
- Pause anytime

## From brief to broadcast to conversations.

Pick the people, write the message, let SetLuca send, and watch the replies become conversations.

1. **Pick who's in** (you). Filter by channel, pipeline stage, campaign, or list. See the recipient count and preview the exact people before you write a word.
2. **Write the message in your voice** (you). One message, checked against your real offers and prices, and previewed before send. Every recipient gets a personalized version.
3. **It sends and honors the windows** (SetLuca). Delivery honors each channel's messaging window, and a large list goes to a small group first.
4. **Watch what comes back** (you). Per-recipient delivery and reply status on every run. Replies land in the leads' threads, get drafted in your voice, and flow through your queue like any other conversation.

## A campaign with the controls of a conversation.

The reason most people don't broadcast is the blast: no personalization, no preview, no way to stop it. Broadcasts fix all three without becoming cold outreach.

### One message, personalized per lead

Every recipient gets their own version, written from what SetLuca already knows about them (their name, their stage, what they asked about), instead of a group message with an @everyone energy. It reads like a coach who remembered each thread.

- Personalized from each lead's own snapshot
- Same message, per-lead tailoring
- Lands in the lead's normal conversation thread

### You choose who's in

A broadcast goes to the leads you pick: a channel, a pipeline stage, a campaign, or a specific list. You see the count and preview the exact recipients before anything sends, so nobody gets a message you didn't mean for them.

- Filter by channel, stage, campaign, or list
- Recipient preview before send
- Personalization per recipient

### Window-aware, pausable like a pro

Sends honor each channel's messaging window. A run can be paused at any moment, and paused sends hold until you resume them.

- Window-aware delivery
- Pause and resume a run at any moment
- One bad recipient never blocks the batch

### Know what came back, not just what went out

Each run shows per-recipient status (received, opened, replied) and the campaign's overall metrics. Replies land in the lead's normal thread and flow into your pipeline, so you measure a broadcast by the conversations it starts.

- Per-recipient delivery and reply status
- Run-level metrics on every campaign
- Replies become normal, drafted conversations

## Three campaigns worth running on purpose.

Each is a deliberate one-to-many send with a clear brief, the kind of thing a setter would do by hand if they had the afternoon.

### The launch announcement

A new cohort opens in three weeks and every lead who's asked about it this quarter should know.

One broadcast to that stage, personalized with each lead's question. The replies become drafted conversations in your queue by the evening.

### The deadline reminder

Early-bird pricing ends Friday and fifty qualified leads haven't booked.

A reminder to exactly those fifty, personalized with their name and the offer. The booked calls land on your calendar before the offer closes.

### The re-engagement campaign

Leads who went quiet last month, a channel's worth, deserve one real nudge, not a list-blast.

A broadcast to that channel's quiet leads, one nudge in your voice. The ones who answer re-enter the normal pipeline; the ones who don't stay untouched.

## A blast to your list vs. a broadcast to your leads.

Most broadcast tools send the same message to everyone, at once, with no way to take it back. Here's what that costs.

### A blast

- Same message to everyone, including the wrong people. The launch note goes to leads who already bought, already asked, and already ghosted, because there's no filter beyond the list.
- 500 messages in five seconds. An instant burst that reads as a bot to the platform and a spammer to the lead, and that burns the account's standing.
- Once it's sent, it's sent. A typo, a wrong deadline, a price mistake: no pause, no recall. The thread is out there and so is the damage.

### A SetLuca broadcast

- Only the leads you picked, each one personalized. The launch note reaches the stage you filtered for, and each version opens with what that lead actually asked about.
- Messaging windows honored. A lead whose channel window has closed is left out and listed with the reason, instead of getting a send that would fail.
- Pause anytime, and measure what comes back. Spot a mistake? Pause the run. See it working? Watch per-recipient replies turn into drafted conversations in your queue.

## Every stage a broadcast goes through.

A broadcast is not a send button. It moves through states, and each one is a place you can look at what is about to happen and change your mind.

| Stage | What it means | What you can do |
| --- | --- | --- |
| Draft | You are writing the message and choosing who gets it | Change anything, including the audience rules |
| Previewed | The audience is locked to a snapshot, with sample messages and a safety check | Read real drafts, and see who was excluded and why |
| Approved | You have signed off on the message and the list | Start it, or go back to the draft |
| Running | Sending, a small test group first on a big list | Watch it land, or pause it |
| Paused | Sending stopped, and nothing pending has gone out | Resume where it left off, or cancel |
| Cancelled | Stopped for good | Nothing further sends. What already went out stays sent |
| Completed | Every recipient resolved as sent, skipped, or failed | Read the outcome per person, not just a total |
| Failed | Enough deliveries failed that SetLuca stopped the run | Retry only the ones that failed |

Replies arrive in the lead's normal thread and get drafted like any other message.

## The parts that stop a bad send.

The risk in a one-to-many message is that it is wrong for everyone at once. Four things exist to catch that before your whole list sees it.

### What is the test group for?

On a large list, SetLuca sends to a small group first and watches what comes back. If too many of those fail, the run stops before the rest of your leads are touched. A broken link or a dead template costs you a handful of sends, not a thousand.

### Who gets excluded, and can I see why?

You see the count and the reason before anything sends. A lead can be left out because they are blacklisted, because consent is missing, or because their channel's messaging window has closed. It is a list you can read, not a silent shortfall in the total.

### How personal can one message be?

There are three settings. The same words to everyone, the same words with their details filled in, or a message written for each lead from what SetLuca knows about them. The third costs more and reads like you wrote it, because the wording is theirs alone.

### What does the safety check look for?

It runs before you can approve, and it returns two kinds of finding. Warnings you can read and go ahead anyway, and blockers that stop the broadcast until you fix them. Each one names what it found and where, so the fix is obvious.

## The details, for people who want them.

Who's in, how it sends, what you can stop, and how you know it worked.

- **Audience.** Choose by channel, pipeline stage, campaign, or list. See the recipient count and preview the exact people before sending.
- **Personalization.** Each recipient gets a version written from their own lead snapshot: name, stage, and what they asked about.
- **Messaging windows.** Sends honor each channel's messaging window. Leads outside it are left out and listed with the reason.
- **Controls.** Pause and resume a run at any moment. Paused sends hold until you resume them.
- **Delivery.** Each recipient is sent independently, so one failure never blocks the rest of the batch.
- **Metrics.** Per-recipient status (received, opened, replied) plus run-level totals on every campaign.
- **Replies.** Replies land in the lead's normal thread and flow into the same pipeline as any other inbound.
- **Plans.** Included on every plan. What changes between plans is how many replies a month you get, plus what Starter leaves out: Writing style tuned weekly from your newest DMs and Follow-ups that win back ghosted leads. Channel availability is the same on every plan.

## Questions

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

Only if it's unsolicited, and a SetLuca broadcast never is. It goes to leads who already messaged you or are already in your pipeline (the same people a setter would reach out to), and you preview the recipients and approve the message before the run starts.

### Who actually gets it?

Whoever fits the brief you set: a channel, a stage in your pipeline, a campaign, or a specific list. You see the recipient count and a preview of the exact people before anything sends, and every one gets a personalized version, not a group message.

### Can I stop it once it's running?

Yes, any time. Pause a run and the sends that haven't gone out hold until you resume them. One bad recipient never blocks the rest either: each send happens independently, so a single failure doesn't stall the batch. On a large list, SetLuca also stops the run itself if too many of the first sends fail.

### Will a large campaign get my account flagged?

Broadcasts go only to leads who already messaged you, over the channels' official APIs, and messaging windows are honored on channels that require them. On a large list SetLuca sends to a small group first and stops the run if too many fail.

### How do I know if it actually worked?

Each run shows delivery and reply status per recipient (who received it, who opened the thread, who replied) next to the run's overall numbers. Replies land in the lead's normal conversation and flow into your pipeline, so you're measuring conversations started, not just messages sent.

### Which plans include broadcasts?

Included on every plan. What changes between plans is how many replies a month you get, plus what Starter leaves out: Writing style tuned weekly from your newest DMs and Follow-ups that win back ghosted leads. Channel availability is the same on every plan.

## Try it

Run a campaign where every lead gets their own message. Pick your recipients, write the message in your voice, and SetLuca handles the replies, and shows you what came back.

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

## Other features

- [Writing style](/features/voice.md): Replies written the way you write, learned from your own replies
- [Review queue](/features/review-queue.md): Read replies first on any channel you choose
- [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, and Messenger live; WhatsApp coming soon
- [Comment-to-DM](/features/comment-to-dm.md): Instagram comment-to-DM, live
- [Automations](/features/automations.md): Describe a rule once, then let it run
- [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): Calendars, webhooks, REST API, and MCP
- [Inbound](/features/inbound.md): Telegram, Instagram, and Messenger in one prioritized queue