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

# Outbound sequences introduction

> What an outbound sequence is, which channels its steps can use, what each channel needs first, and how a sequence moves from draft to finished.

A sequence reaches a list of people with a scheduled, multi-step message: emails, WhatsApp templates and phone calls, in the order and with the waits you choose. When someone replies, the AI handles the reply and that person leaves the sequence. Use a sequence for win-back campaigns, follow-ups, reminders and other outreach you start, rather than wait for.

> [!NOTE]
>
> **Outbound → Sequences** in your [OpenCX dashboard](https://platform.open.cx/outbound/sequences). In **Settings → Roles**, **Outbound sequences** read lets a member view sequences and write lets them change, launch and pause them. Creating one starts a Companion chat, which also needs **Companion** write. Mailboxes and sending domains need **Email sending fleet**; see [Senders and domains](https://docs.open.cx/outbound/senders-and-domains.md).

## What a sequence is made of

Every sequence opens on four tabs:

| Tab | What it holds |
| - | - |
| **Overview** | The plan (what the sequence is for and who qualifies) and, once it sends, its numbers and recent replies. |
| **People** | Everyone enrolled, with their status and, once it sends, what happened at each step. |
| **Steps** | The messages and calls, in order, with the wait before each one. |
| **Settings** | What it sends from, how the AI handles replies, business hours, and who to skip. |

Each person walks the steps in order on their own schedule. A sequence opens in the Companion, so you can ask it to change anything you see. See [Create a sequence](https://docs.open.cx/outbound/create-a-sequence.md).

## Channels a step can use

| Step | Who reaches the person | What you need first |
| - | - | - |
| **Email** | A mailbox on one of your outbound sending domains | At least one mailbox under [Outbound → Senders](https://docs.open.cx/outbound/senders-and-domains.md) |
| **WhatsApp** | Your connected WhatsApp number, with an approved message template | A [connected WhatsApp number](https://docs.open.cx/whatsapp/connect-whatsapp.md) and an approved template |
| **Phone, AI agent** | Your AI phone agent | A [phone agent](https://docs.open.cx/phone/agent-config.md) with a verified caller number, a number pool or a SIP trunk under **Calls out as** |
| **Phone, your team** | The free agents of one of your teams, through your own SIP trunk | A team and an [outbound SIP trunk](https://docs.open.cx/phone/sip-integration.md); see [Call from a sequence](https://docs.open.cx/phone/human-calling.md#call-from-a-sequence) |

A sequence can mix channels, for example an email, then a WhatsApp message two days later, then a call. It can't launch until every channel it uses has something to send from. WhatsApp numbers that can't send in bulk are shown greyed out with the reason.

## Life cycle

| Status | Meaning |
| - | - |
| **Draft** | Being built. People can be enrolled and reviewed; nothing is sent. |
| **Sending** | Launched. People are messaged as their steps come due, and people enrolled later start right away. |
| **Paused** | Nothing more sends. Everyone keeps their place. |
| **Finished** | Nothing is left to send. Enrolling more people starts it again. |

The button at the top right of a sequence follows its status: **Launch** on a draft, **Pause** while sending, **Resume** when paused. **Launch** is greyed out until the sequence has steps and a sender for every channel; hover it to see what is missing.

To delete a sequence, use **Delete** in its row menu on the Sequences list. A sequence that is still sending must be paused first. Deleting removes it from the list; the people in it and everything that already happened are kept.

## What OpenCX enforces

Sequences apply these checks for you. They help you honor people's choices; they are not legal advice, and you remain responsible for having consent to contact the people you enroll.

* **Opt-outs and the blocklist.** Every sequence email carries a one-click unsubscribe header. People who unsubscribe, opt out of WhatsApp marketing messages, or whose email address hard-bounces are added to your outbound blocklist, and a sequence never contacts a blocked address. See [Track results](https://docs.open.cx/outbound/track-results.md#the-outbound-blocklist).
* **Restricted channels.** A step on a channel the contact [restricted](https://docs.open.cx/contacts/manage-contacts.md#restricted-channels) is skipped.
* **Business hours.** By default a message that comes due outside your office hours waits for the next opening, in the person's own timezone when it's known.
* **Not messaging the same person twice.** By default, people already in another sequence, and anyone a past sequence already messaged, are skipped.
* **Sending limits.** Each mailbox sends at a measured pace that grows with its sending history. See [Sending limits](https://docs.open.cx/outbound/senders-and-domains.md#sending-limits).
* **Calling rules.** Before you launch a sequence that calls numbers in known countries, a **Quick check before launching** dialog summarizes each country's calling rules. Tick **I have read this and consent** to launch.

***

## Related Documentation

> [card] [Create a sequence](https://docs.open.cx/outbound/create-a-sequence.md)
>
> Audience, steps, settings and launch.

> [card] [Senders and domains](https://docs.open.cx/outbound/senders-and-domains.md)
>
> Mailboxes and sending domains for email steps.

> [card] [Track results](https://docs.open.cx/outbound/track-results.md)
>
> Numbers, statuses, replies and exits.

> [card] [Sequences API](https://docs.open.cx/api-reference/sequences/index.md)
>
> Run sequences from code.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.