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

# Launch multichannel outreach

> From a contact list to a running multichannel sequence — accounts checked, contacts enrolled, start confirmed.

**Outcome:** a running sequence with assigned mailboxes, a schedule, and enrolled contacts — started
only after explicit confirmation.

## Best interface

<Note>
  **The [`campaign-launch` skill](/skills/catalog#campaign-launch)** runs the whole checklist and
  gates the start on your explicit confirmation. **In an MCP client**, follow the
  [Launch a sequence safely recipe](/mcp/recipes#launch-a-sequence-safely) — same checklist as MCP
  tool calls.
</Note>

## Steps

<Steps>
  <Step title="Check sending accounts">
    Email steps need a connected mailbox; LinkedIn steps need a linked LinkedIn account.
    API: `GET /v3/email-accounts`, `GET /v3/linkedin-accounts` (`reply api /v3/email-accounts`).
    MCP: `reply_list_email_accounts`, `reply_list_linkedin_accounts`.
  </Step>

  <Step title="Create or select the sequence">
    API: `POST /v3/sequences` to create, `GET /v3/sequences` to pick an existing one.
    MCP: `reply_search_sequences`. For LinkedIn-first cadences, lead with LinkedIn steps and fall
    back to email for prospects who don't accept.
  </Step>

  <Step title="Assign mailboxes and a schedule">
    MCP: `reply_assign_email_account_to_sequence`, `reply_assign_schedule_to_sequence` — a
    sequence without a mailbox fails to start with `NoEmailAccounts`.
  </Step>

  <Step title="Enroll the contacts">
    Add contacts by id, in bulk. Resolve the ids first — never guess them.

    ```bash theme={null}
    reply api /v3/sequences/12345/contact-links/bulk \
      --body '{"contactIds":[101,102],"removeFromExisting":false}' --json
    ```

    Per-contact skips (already in sequence, blacklisted) are reported, not failures — read them
    and report exact counts.
  </Step>

  <Step title="Confirm, then start">
    Starting begins real outreach — a [high-stakes action](/agents/safety) on every surface. Nothing
    below asks for confirmation, so ask the user yourself before you run it.

    ```bash theme={null}
    reply api /v3/sequences/12345/start --method POST --json
    ```

    MCP: confirm with the user, then `reply_start_sequence`.
  </Step>

  <Step title="Verify it's running">
    API: `reply api /v3/sequences/12345 --json` · MCP: `reply_get_sequence_stats` or
    `reply_search_sequences` to confirm the status is Active.
  </Step>
</Steps>

## Availability notes

* Everything in this guide is **available today**, including LinkedIn steps (with a linked
  LinkedIn account).
* Complex step editing (A/B variants on live sequences, LinkedIn step authoring) is handed off to
  the Reply app in Skill v1.

## Related

* [Improve sequences every cycle](/guides/improve-sequences) — optimize what's now running
* [Convert replies into meetings](/guides/convert-replies-to-meetings) — handle the responses
* [MCP recipe: Launch a sequence safely](/mcp/recipes#launch-a-sequence-safely)