# Campaigns and personalization

A campaign turns an audience into outreach from a particular sender. It brings together the people to contact, the sender's LinkedIn account or sending mailbox, the messages, follow-up timing, and controls for sending and responses.

Distill supports LinkedIn-only, email-only, and LinkedIn-plus-email campaigns. Messages can combine your own wording with AI-written sections that use relevant professional context. The purpose can be starting a conversation, reconnecting, inviting people to an event, sharing an update, or asking someone for an introduction.

Matching the audience criteria does not give permission to send outreach. Account access, campaign status, channel setup, exclusions, and any outreach already underway also determine whether a message can be sent.

## What a campaign contains

| Part | What it contributes |
| --- | --- |
| Audience | People drawn from the campaign's source lists, connected to the project's targeting groups |
| Sender | The person represented in the outreach and the accounts available for sending |
| Message | Initial copy, connection-request options, and follow-up messages |
| Context | Relevant sender, company, recipient, relationship, and list information |
| Sending controls | Manual or Auto mode, channel choices, timing, and applicable limits |
| Response handling | Whether replies are handed to the sender or supported by the configured meeting-booking workflow |

A source list can change over time. Adding people can make them available to the connected campaign; removing people does not erase conversations that have already started. A company list is useful for discovering employees, but an ordinary campaign contacts people. An introduction campaign instead contacts a connector about a target person. [Lists](https://distill.com/guides/lists) and [Introductions](https://distill.com/guides/introductions) explain those distinctions.

## LinkedIn and email

LinkedIn connection requests and LinkedIn messages are separate steps. A request can have no note, an authored note, or an AI-written note. The short connection note is separate from the opener in the later message. A connect-only campaign sends requests without a subsequent campaign message, follow-ups, or email.

For a LinkedIn-first campaign, an existing connection and a person who has not accepted a request can follow different paths. Once a connection is accepted, the person may become eligible for the LinkedIn message. Acceptance alone is not a reply or a booked meeting.

With email fallback enabled, a campaign can move to email when its LinkedIn path does not reach the person. Separate settings control the wait for acceptance and the switch after an unanswered LinkedIn message.

LinkedIn-only campaigns disable email fallback. Email-only campaigns skip the LinkedIn request and message steps.

Email requires a sending mailbox available to the selected sender. A campaign configured for both channels can have working LinkedIn steps while its email steps are blocked by incomplete mailbox setup. Connecting an existing Gmail mailbox and using a separately provisioned outreach mailbox are different setup choices. A dedicated mailbox also needs setup and warmup; it is not ready merely because its address has been added.

## Your wording and AI-written sections

The message builder supports several ways to compose a message:

| Option | What it does |
| --- | --- |
| Exact Text | Uses wording you provide, with supported variables filled in for the recipient |
| Conditional Text | Uses different wording you provide for LinkedIn and email |
| AI-written blocks | Generates sections such as an opener, reason for reaching out, value proposition, social proof, custom text, call to action, or follow-up |
| Reusable custom blocks | Reuses writing instructions and selected information across messages |
| LinkedIn Pause | Splits a LinkedIn message into delayed parts, distinct from a later follow-up |

Exact Text is useful for a specific invitation, approved product description, or sentence that should not be freely drafted by AI. Distill still fills in variables and formats the text for LinkedIn or email. The delivered message may therefore differ from the text shown in the editor.

AI-written blocks can have instructions, constraints, and feedback. Company context and messaging guidance help describe the offer accurately. Sender context helps establish whose experience and perspective the message represents. Campaign Notes to AI can add further guidance when enabled. These inputs guide the writing, but the result can still get the tone or facts wrong.

Exact Text preserves the author's claims; their accuracy still needs review.

## What personalization can know

Available context can include the recipient's role and professional profile, their current employer, the sender's background, the sender's company, relevant relationship evidence, and supported list values. Each kind of writing block has its own inputs. A block does not automatically receive everything in the account.

Openers can use mutual connections, shared background, recent achievements, or location context when available and relevant. Those are different sources of evidence. A mutual connection does not prove friendship, endorsement, or a previous conversation. An event registration does not prove that the sender met the attendee.

The writing process includes checks intended to catch unsupported claims, inappropriate context, and unusable output. Depending on the block and failure, Distill can use configured fallback wording, omit a section, or hold the message for review. These checks reduce mistakes; they do not remove the need to inspect important messages.

List information reaches messages in two distinct ways:

- **Message variables** insert a particular value. Supported built-in variables include names, current company, and title. Custom-column variables are available from eligible columns shared across the campaign's source lists. Some recipients may have no value in that column.
- **AI writing context** supplies information the writing block may use. Supported text, status, and research values can come from lists containing the person or their current employer within the same project. The information can be available without being chosen for the final message.

Putting a note in a list is therefore different from requiring that note in a message. [Research](https://distill.com/guides/research) covers the underlying profile information and its limits.

## A fictional example

Suppose Maya leads partnerships at Northstar, which provides reporting software for partner teams. The campaign targets partnership leaders. Jordan's current role is confirmed as Head of Partnerships at Acme, and an imported event record says Jordan registered for a roundtable that Northstar is hosting.

A possible message is:

> Hi Jordan, I saw you registered for our partner roundtable. I lead partnerships at Northstar, and we're bringing a few partnership leaders together to compare how they measure partner-sourced pipeline. Would you be up for joining the discussion?

The registration reference depends on the supplied event record. The sender's role and event description depend on approved sender and company context. The invitation could use Exact Text, with recipient-specific fields added separately.

The example uses the supplied registration record without inventing a previous meeting, a mutual friend's recommendation, or an existing customer relationship.

## Review, publication, and sending

A draft, a preview, a published template, and an active campaign are different things.

A preview shows how a proposed message looks for a particular person and channel. Publishing makes a message template available to the campaign. Launching or resuming a campaign uses its existing sending mode and must pass readiness checks. Saving a campaign or publishing a template does not, by itself, mean a message was sent.

| Status | Meaning |
| --- | --- |
| Manual | New outreach requires approval. Outreach that has already started can continue, including follow-ups. |
| Auto | Distill can prepare and send eligible outreach automatically within the configured controls. |
| Paused | Automated sending is held until the campaign resumes. |
| Finished | The campaign has ended and cannot be restarted; its history remains. |

Manual does not stop all sending. Approving a LinkedIn request can also approve its prepared message to send after acceptance. Outreach already approved can move to email if the campaign's rules allow it, and outreach follow-ups can continue. Meeting-scheduling sequences created after a reply are different: they do not send automatically in Manual.

Pausing holds subsequent automated sending. It cannot recall delivered messages, and actions already underway at the provider may still complete. Ending one campaign leaves the sender's account and other campaigns in place.

On Agent, a new chargeable outreach automatically buys another pack when both included usage and purchased credits are exhausted. If its payment fails, the organization's live campaigns are paused by a background check, and launching or resuming is blocked. Work already underway may complete before the pause takes effect. Paying successfully makes the campaigns eligible to resume; it does not restart them automatically. [Plans and usage](https://distill.com/for-agents#plans-and-usage) explains the pack price and counting window.

## Follow-ups and changes to an active campaign

Follow-ups have their own copy, channel, and delay. A delayed part of the first LinkedIn message is not the same as a later unanswered-outreach follow-up. A scheduling reminder after someone has replied is different again.

Actual timing depends on the sequence, sending window, sender time zone, available capacity, and what has happened in that person's outreach so far. Connection problems, missing contact information, screening, and delivery failures can hold their outreach even while the campaign remains active.

Changing a template does not instantly replace every prepared message. Distill updates pending messages according to the type of edit and the message's status. Editing a follow-up can hold and regenerate queued steps, but messages edited individually or already being sent are handled differently. The published template, a recipient's prepared message, and the sent message can therefore contain different wording.

## Replies, handoff, and meetings

A detected reply changes the conversation's handling and stops or holds that person's unanswered-outreach sequence. Some responses, including automated replies, can leave the sequence paused for review rather than permanently cancelled. A connection acceptance, decline, substantive response, and confirmed booking are different events.

The **Sender handles replies** option passes the conversation to the customer. Other configured workflows support meeting-booking assistance and review of responses. Passing a conversation to someone is called a handoff. A completed handoff notifies the configured email recipients and can also appear in a connected project Slack channel. The customer's settings and service arrangement determine who responds next.

Distill can detect personal replies sent through connected LinkedIn or email accounts and adjust the conversation's ownership and follow-ups once that activity synchronizes.

A campaign can use a configured scheduling page and tracked booking links for individual recipients. A link visit and a booking are recorded separately. Distill records a booking when it receives a supported booking confirmation, then can match it to calendar details. A booking URL alone is insufficient for booking detection and stopping reminders.

Calendly and [Cal.com](https://cal.com/) have specific support for matching a recorded booking to a calendar entry synchronized with Distill. Calendly uses its booking details; [Cal.com](https://cal.com/) needs its Google Calendar event reference. A fallback can match an already recorded booking using the recipient's email and timing, within its matching limits. Other providers do not use the same identifiers.

## Reading conversations and replying

The campaign's activity view shows the person's conversation history and current state. Supported email and LinkedIn reply composers let a teammate respond through the campaign's sender account. A personal reply and a new campaign message are different actions. The current assistant connector does not provide a general tool for sending these personal replies.

Where a project has customer Slack replies configured, a handoff card can also offer a Reply form in the Slack channel connected to that project. The form accepts a reply while the conversation is still waiting on the customer. Submitting it queues the reply; it does not confirm delivery. If the conversation has already been answered when the form is submitted, Distill rejects the outdated reply and does not send it.

Distill tracks whether a conversation needs the customer, needs Distill, or is waiting for the recipient. A handoff changes who should act next. It does not mean that a response has been sent. Marking a conversation handled or closed likewise does not write or send a message.

A detected sender reply can move the conversation to waiting for the recipient. A reply sent outside Distill depends on synchronization with the connected account. Distill compares when the message was actually sent with the latest handoff, so an older reply arriving late in a sync should not clear a newer request for the customer's attention.

## Reminders and quiet conversations

A project can enable reminders and escalation for conversations waiting on the customer's team. The current setting reminds the customer after five business days and returns the conversation to Distill's review queue after ten business days. Business days here mean Monday through Friday; this is not a holiday-aware calendar or a promise of an exact delivery time.

The setting applies to eligible conversations handed to the customer after it was enabled. Switching it off and back on means only later eligible handoffs qualify; older waiting conversations are not automatically included. Conversations handed to the customer because of a recorded booking are excluded while that booking remains the reason they are waiting. A later incoming message can change that reason.

Returning a conversation to review does not itself send a message to the recipient. The customer's plan and service arrangement still determine who provides response handling; the setting does not add Managed service to an Agent subscription.

Separately, an eligible conversation waiting on the recipient can close after 30 calendar days without activity that keeps it open. This applies independently of the reminder setting, including eligible conversations in paused campaigns. Recorded activity such as a newer sender reply or accepted follow-up can restart the clock, and pending conversation work can prevent closure. Closing the conversation does not finish the whole campaign or send a final message. A later incoming reply is processed under the usual response rules.

## Resuming a held sequence

Resuming a campaign and resuming one person's held sequence are different actions. Making the campaign active does not necessarily restart every conversation that was paused for review.

A sequence can remain blocked because the person replied again, the sender already responded, a personal reply is pending, the person is excluded, no continuation remains, or the campaign or sender is not ready. These checks help prevent an old automatic follow-up from cutting across a conversation that has moved on.

The person resuming an eligible sequence can acknowledge newer incoming messages as part of that action. Resuming makes its remaining steps eligible to run again; it does not send a reply immediately. It also does not override a do-not-contact rule or evidence that the sender has already taken over. Actual sending still depends on campaign status and readiness. Resuming a person's sequence cannot restart a Finished campaign.

## Exclusions and pacing

Campaigns work with the project's do-not-contact rules and configured screening. Rules can concern a person, address, or company, and can use available CRM or recent-conversation information. Their coverage depends on the records, settings, and account access actually available. A list named “Do not contact” is not the same as an active exclusion rule. The project's [Screening History](https://distill.com/guides/reporting#activity-and-screening-history) can help explain recorded decisions and the rules behind them.

Sending limits coordinate activity across the sender's campaigns. Email warmup and channel-specific limits affect how much of the audience can be contacted each day. Pause other LinkedIn outreach automation on the same sender account before Distill starts. Personal LinkedIn activity shares that account's capacity, so leave room for it in the sending pace.

## What a connected assistant can do

The current connector supports reading campaigns and templates, creating campaigns from suitable People lists, drafting and previewing messages, publishing supported template changes, and changing supported campaign settings. It can also launch, pause, resume, or finish a campaign within the same readiness and access rules used by the app. Launch and resume preserve the current sending mode.

Supported settings include source lists, channels, sender and available mailbox, Notes to AI, connection-request options, and selected email details. The connector's current campaign controls do not change Automatic-send settings, the send window, or daily caps. Some sender or seat changes require confirmation in the app.

Personal replies use the app's reply composers or supported Slack reply flow described above. [Using an assistant](https://distill.com/guides/using-an-assistant) covers the connector's current capabilities.

## Frequently asked questions

### Can I use LinkedIn without email?

Yes. LinkedIn-only campaigns disable email fallback. They still need valid LinkedIn access. A missing email mailbox does not prevent that channel from being configured.

### Can I send only connection requests?

Yes. A connect-only campaign sends connection requests without a later campaign message, follow-ups, or email. It is different from a normal LinkedIn-only message campaign.

### Can I mix my own copy with AI personalization?

Yes. Exact Text and wording you provide separately for LinkedIn and email can sit alongside AI-written sections. The final preview shows the combination for a particular recipient.

### Does the connection note use the same opener as the later message?

They are separate parts of the outreach, with separate settings. An AI-written connection note can use relevant opener information, but editing one does not necessarily update every note or message already prepared.

### Does AI know that I met someone or that they are a customer?

Only when the available information supports it. A connection or list membership alone does not establish either fact. Relevant verified context can help the message reflect the actual relationship.

### Does Manual stop all automatic sending?

No. Manual controls the start of new outreach. Approved continuations and outreach follow-ups can still send. Paused is the campaign status for holding automated sending.

### Does publishing new copy replace every queued message?

No. Updates depend on the type of edit and the message's status. Messages edited individually or already being sent may keep their earlier wording. Messages already sent do not change.

### Can I handle replies myself?

Yes. **Sender handles replies** is a supported setting. Distill can detect replies made outside the app when they sync from the connected account. The current assistant tools cannot handle everything in the inbox.

### Does a reply reminder send another message to the prospect?

No. The reminder asks the customer to handle the conversation. Returning it to Distill's review queue also changes who needs to act. Neither sends a message to the prospect.

### Will resuming a campaign restart every paused conversation?

No. Individual sequences have separate checks. A new reply, manual takeover, exclusion, or missing continuation can keep a sequence held even when the campaign is active.

### If an inactive conversation closes, does that finish the campaign?

No. Closing one eligible conversation after inactivity and finishing an entire campaign are separate states.

### Why use a dedicated outreach mailbox?

It separates outreach from the everyday work mailbox. Deliverability still depends on setup, warmup, sending behavior, recipient data, and provider decisions.

### Can I use an existing booking link?

A configured booking page can be used for scheduling. Calendly and [Cal.com](https://cal.com/) have specific support for linking recorded bookings to synchronized calendar entries. Distill needs a supported booking confirmation to record the booking. Linking it to calendar details also requires the relevant calendar data. A URL that opens successfully does not prove those connections are working.

### Can I restart a campaign after marking it Finished?

No. Finished is permanent for that campaign. Paused is the temporary status.

### Can an assistant launch a campaign now?

Yes. The connector supports launch and resume when access and readiness checks pass, preserving the campaign's existing Manual or Auto mode.

## Related pages

- [Targeting groups](https://distill.com/guides/targeting-groups)
- [Lists](https://distill.com/guides/lists)
- [Research](https://distill.com/guides/research)
- [Introductions](https://distill.com/guides/introductions)
- [Using an assistant](https://distill.com/guides/using-an-assistant)
- [Reporting and results](https://distill.com/guides/reporting)
- [Integrations](https://distill.com/guides/integrations)
- [FAQ](https://distill.com/guides/faq)
