> ## Documentation Index
> Fetch the complete documentation index at: https://developer.salesforge.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sequence (V1)

> Understand legacy V1 sequence behavior, data model, and lifecycle in Salesforge public API.

<Warning>
  Sequence V1 is deprecated for new builds. For new orchestration work, prefer [Multichannel Sequence (V2)](/salesforge-api/concepts/multichannel-sequence).
</Warning>

V1 is the legacy Salesforge sequencing engine and is primarily email-oriented.

Use V1 when you need compatibility with existing V1 workflows and payloads.

## Steps

In V1, a sequence is a series of emails sent over time.

Each step is usually one email in that series.

Example of steps:

Step 1: Usually an initial email. A sequence must have at least one step.

Subject: `Quick intro for {{company}}`

Body:

```text theme={null}
Hi {{first_name}} {{last_name}},

I noticed your team at {{company}} is scaling outbound.
Would it help if I share a short playbook we use to improve reply rates?

Best,
Alex
```

Step 2: Next steps after Step 1 are usually follow-up emails.

Subject: `Following up on my previous note`

Body:

```text theme={null}
Hi {{first_name}} {{last_name}},

Just following up in case my last email got buried.
If this is relevant, I can send 2-3 ideas tailored for {{company}} around {{priority_goal}}.

Best,
Alex
```

### Step variants

A step variant is an alternative version of the same email step.

Variants let you run message experiments while keeping the same timing position in the sequence.

Good variant design keeps intent consistent and changes only the messaging hypothesis.

Example conceptual variants for one step:

* Variant A: direct, outcome-first framing.
* Variant B: problem-first framing with a softer CTA.

### Custom variables in step content

V1 supports variable-based personalization in step content.

Variables inject recipient or account context at send time, which helps keep messages relevant without writing one-off copy per contact.

Use built-in variables such as `{{first_name}}`, `{{last_name}}`, and `{{company}}` for core personalization, and add custom variables for business-specific context.

Custom variable syntax in message content uses `{{var_name}}`.

Example placeholders in copy:

* Subject: `Quick question for {{company}}`
* Body: `Hi {{first_name}} {{last_name}}, I noticed {{company}} is focused on {{priority_goal}}.`

<Warning>
  Custom variables used in a message must exist for the enrolled lead/contact. If a referenced variable is missing, the email send will fail.
</Warning>

## Schedules

Schedules define when a sequence is allowed to send. Conceptually, schedules are delivery windows that gates execution.

In practice, teams align schedule windows with recipient time zones, expected reply behavior, and deliverability goals.

## Status model

V1 uses a two-level status model: sequence lifecycle and contact lifecycle.

### Sequence lifecycle

A sequence moves through planning, active execution, pause, and completion-oriented phases.

Example lifecycle path: `draft` -> `active` -> `paused` -> `active` -> `completed`.

### Contact lifecycle

Each contact also moves through a lifecycle model that captures progress, pauses, failures, replies, and completion.

Common contact statuses include `active`, `paused`, `failed`, `replied`, and `finished`, plus outcome-specific statuses such as `bounced` and `unsubscribed`.

Example: one contact can finish normally while another is paused or moved into retry handling.

## Practical usage patterns

1. Design sequence intent first, then map steps and variants to that intent.
2. Keep variant differences deliberate and measurable.
3. Use variables for personalization and always provide fallback wording.
4. Operate with lifecycle-state discipline for monitoring.
5. **Use V2 for net-new multichannel orchestration work.**

## Minimum requirements for a sequence

Before a V1 sequence can run, it must include all of the following:

* At least one step with at least one variant.
* At least one enrolled lead/contact.
* At least one mailbox assigned for sending.
* At least one valid schedule.

Example readiness checklist:

1. Create Step 1 with one variant.
2. Enroll at least one lead/contact.
3. Assign at least one active mailbox.
4. Add at least one schedule window.
5. Activate the sequence.

## Related resources

* [Multichannel Sequence (V2)](/salesforge-api/concepts/multichannel-sequence)
* [Create a multichannel sequence](/products/salesforge/create-multichannel-sequence)