Build a sequence

Build a sequence in chat, then edit it on its page. Sending starts after you publish, enroll and activate.

Who can use it

Owners, admins and members on a plan with sequences (see Sequences). LinkedIn steps need a plan with LinkedIn steps; on Pro, build email-only sequences.

Build and launch a sequence

Set up your senders in Settings → Sequences first. You can draft without them, but you can’t activate.

1. Open Sequences under Demand in the sidebar and click Create sequence. A chat opens.
2. Name your contact list, audience, offer, reason to reach out and ask.
3. Review the agent’s plan and choose whether messages wait for approval.
4. The agent saves a draft with its messaging, steps and send window.
5. Ask for a Test run. It writes drafts for one contact without waiting or sending. Repeat with at least five contacts across different groups to check personalization.
6. Click Create in the sequence’s header to publish it. The first publish leaves the sequence paused.
7. Ask the agent to enroll contacts (see Enroll contacts).
8. Click Activate. This starts sending to enrolled contacts, within the send window and sending limits.

The sequence shows Active, and Enrollments lists your contacts. Click Pause to stop sending and Resume to continue.

Test before you publish

Test runs use your current draft and appear on the Test runs tab. They never send or add anything to For review.

Edit on the sequence’s page

Page edits save automatically to the draft shared with your agent and teammates.

• From a step’s menu, choose Add above or Add below, move the step, or remove it. Or drag a step by its handle; its wait moves with it.
• Set waits in days or minutes.
• A new sequence’s footer offers Delete sequence. Deleting a sequence that was never published removes it for everyone and can’t be undone.
• A published sequence you’ve edited shows Unpublished changes. Publish changes makes the draft live; Discard throws it away.

When publishing is blocked, Lightfield highlights the problems, counts the affected steps in a banner and scrolls to the first one. Use the arrows to move through multiple affected steps. For a single affected step, click its count to return to it:

• A step has no name, an agent step has no instructions, or a wait has no length.
• A template has a variable with no fallback, or text in braces that isn’t a variable.
• There’s no email sender for the email steps, or no LinkedIn account for the LinkedIn steps.
• A sender or reviewer is no longer in the workspace.

Steps and waits

Each step is one message: an Email, a LinkedIn invite or a LinkedIn message. Waits, such as Wait 3 days, sit between steps.

• A sequence can start with a wait, but must end on a step.
• It can have at most 10 email steps.
• Follow-up emails reply in the first email’s thread, so only the first email’s subject is sent.

LinkedIn steps covers the order invites and DMs need.

Review manually or send automatically

Each step has a delivery mode:

• Review manually (the default): the message waits in For review until someone approves it. Approving doesn’t skip the send window or sending limits.
• Send automatically: the message sends without review.

The sequence’s creator and its senders are reviewers for messages that wait in For review; add others in the Reviewers row. Start with Review manually, and switch to Send automatically once you trust a step’s copy.

Agent or template steps

Each email, LinkedIn message and connection note is Agent or Template. Pick from the menu at the top of the step. One sequence can mix both.

	Agent	Template
You write	Instructions for the agent	The message itself
Each contact gets	A message written for them from the instructions, their record and the steps already sent	Your copy, with variables filled in
Quality checks	Applied before sending	Not applied; your copy sends as written
Email formatting	Plain text; bullet lines starting with - are allowed	Bold, links and lists keep their formatting

Use agent steps when the reason to reply is specific to the person, and template steps when the wording must be exact.

Agent steps write from the sequence’s five messaging fields (Persona, Value proposition, Trigger, Call to action and Description), the contact’s CRM record, and your workspace Knowledge.

Quality checks on agent-written messages

Lightfield blocks an agent-written message that contains an em dash, an unfilled placeholder such as [Your Name], internal markup or record IDs, markdown formatting, or HTML tags, and an email with an empty body or a line break in its subject. Bullet lines starting with - or • are allowed.

When a check fails, the agent rewrites the message and tries again. If it still can’t pass, the step fails and the contact shows Needs attention. Your own edits to a draft in For review aren’t checked, so read them before you approve.

For links in agent-written emails, use plain URLs.

Variables and fallbacks

Type { in a template’s subject, message or note to add a variable from the Contact, their Account or the Sender. Every variable needs a fallback, the text used when that contact’s field is empty. Click a variable to set it. A blank fallback inserts nothing; a missing one blocks publishing.

Choose senders

In Senders, click each designated sender to choose their mailboxes and LinkedIn account, or ask the agent. The sequence uses only these senders.

For each contact’s first email, Lightfield picks the designated mailbox used least recently that has room under its daily limit, preferring the contact’s mail provider (Google or Microsoft). Every later message to that contact comes from the same sender. If your list spans both providers, designate senders on both.

Enroll contacts

Enroll contacts by asking the agent in chat, or through the API. The sequence must be published; it can be paused, and sending waits until you activate it.

Before you enroll, ask the agent to check your list against existing customers, open opportunities and other active sequences. A contact is skipped when they’re already active or paused in this sequence, have no email and the sequence has email steps, or have no LinkedIn URL and it has LinkedIn steps. A contact can have only one live enrollment in a sequence; once it ends, you can enroll them again.

Edit a live sequence

You don’t need to pause first. Once you publish a change, enrolled contacts pick it up at their next step. Most changes only affect messages not yet written, and messages waiting in For review are rewritten unless someone edited them.

These changes also move contacts already enrolled:

Change	Effect on enrolled contacts
Remove a sender	Their contacts stop at the next step until the sender is added back and the step is retried.
Add a step	Contacts who haven’t passed that point may receive it.
Remove a step	Contacts who haven’t reached it skip it. A message waiting for review there is withdrawn.
Reorder steps	Contacts may move to a different next step.
Shorten a wait	Counted from when each wait began, so some contacts may be due at once.
Switch a step to Send automatically	Future messages send without review. Messages already waiting still need a decision.
Change the send window or timezone	Scheduled sends may move. Sends already queued or waiting for review keep their timing.

The agent tells you how a change affects enrolled contacts before it publishes. If you’re replacing most of the steps, build a new sequence instead.

Common questions

How do I test a sequence before it sends anything? Ask the agent or click Test run. It drafts each step for one contact without sending.

Can I enroll contacts from the sequence’s page? No. Ask the agent in chat, or use the API. The sequence must be published first.

Do I need to pause a sequence before I edit it? No. Publish the change and enrolled contacts pick it up at their next step.

I asked for bold text or a link in an email and it didn’t work. Why? Agent-written emails are plain text by design. Paste the raw URL, or switch the step to a template, which keeps bold, links and lists.

Can I add call or SMS steps? No. Sequences support email, waits and eligible LinkedIn steps. Ask the agent to create a separate call task instead; it is not a sequence step.