> ## 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.

# Track outbound sequence results

> Read a sequence’s numbers, what each person status and journey mark means, where replies and calls show up, how people exit, and how the outbound blocklist works.

Each sequence keeps a live record of what happened to every person in it. Use this page to read its numbers, find out why someone wasn't reached, and see where replies, calls and opt-outs end up.

> [!NOTE]
>
> Open a sequence from **Outbound → Sequences** in your [OpenCX dashboard](https://platform.open.cx/outbound/sequences). Viewing results needs **Outbound sequences** read; the text of replies also needs **Inbox** read. Taking people out or including them needs **Outbound sequences** write.

## The numbers

The **Sequences** list shows **People**, **Contacted** and **Replied** for each sequence, with the reply rate next to **Replied**. The cells stay blank until a sequence launches. A pulsing dot next to **People** means the Companion is working on that sequence's people.

Open a sequence to see the same numbers on **Overview**. Every number counts people, not messages.

| Number | What it counts |
| - | - |
| **People** | Everyone in the audience: enrolled and not held back by the plan's criteria. |
| **Contacted** | People at least one step went out to. |
| **Replied** | People who replied on WhatsApp or email, or answered a call. The reply rate is **Replied** out of **Contacted**. |
| **Won't reach** | People whose journey is over without any message going out. Hover to see who and why, for example *they were on the blocklist* or *no address for this step's channel*. |
| **Needs you** | People held at a step until someone fixes something. Hover to see who and why. |

**People** equals **Contacted** plus **Won't reach** plus the people still waiting for their first message. **Won't reach** and **Needs you** appear only when they are above zero.

Before launch, **Overview** shows the audience instead: **Enrolled**, and with criteria, **Will send to**, **Not judged yet** and **Didn't fit**.

## Replies

**Recent replies** on **Overview** lists the five latest replies, newest first. Click one to open its session in the inbox, or click **See all replies** to open the inbox filtered to this sequence. In the inbox, the **Sequence** filter does the same for any sequence. What happens when someone replies is described in [Create a sequence](https://docs.open.cx/outbound/create-a-sequence.md#when-someone-replies).

## Each person's status

The **People** tab lists everyone with their **Reach** (the channels you can reach them on), **Fit** when the plan has criteria, **Status**, **Journey** once the sequence has launched, and when they were **Added**.

| Status | Meaning |
| - | - |
| **Candidate** | Enrolled, not sending yet. Everyone is a candidate in a draft. On a sending sequence, a candidate was held back by the criteria or the blocklist. |
| **Sending** | Their steps go out as they come due. |
| **Needs data** | A step variable has no value and no fallback for them, or their own data can't be sent. Fix it and they continue from the same step. |
| **Template broken** | The step's template is missing or rejected. Switch the step to a working template. |
| **Replied** | They replied or answered a call. The sequence is done with them. |
| **Opted out** | Every channel the sequence could reach them on is blocked, for example after they unsubscribed or their email bounced. |
| **Finished** | They reached the end without replying. Skipped and failed steps count as reached. |

### The journey

**Journey** shows one mark per step: the icon is the channel and the color is what happened. Hover a mark for details; click it to open the session in the inbox.

| Color | States |
| - | - |
| Green | **Replied**, **Answered** |
| Solid | **Sent**, **Delivered**, **Read**. Delivered and read come from WhatsApp; email steps show **Sent**. |
| Amber | **No answer**, **Busy / declined** |
| Red | **Failed** |
| Faint | **Not reached yet**, **Waiting to send**, **Needs data**, **Rescheduled**, **Skipped** |

**Rescheduled** and **Skipped** carry a reason, such as *outside sending hours*, *a session was already open*, *they opted out* or *no way to reach them on this channel*. A skipped step isn't an exit: the person moves on to the next step.

## Calls

AI call steps show **Called**, **Answered**, **No answer**, **Busy / declined** or **Failed** in the journey. When the phone agent calls from a number pool, the mark shows the attempt, such as **Retry scheduled · Attempt 2 of 3**, with **Calling from** or **Last called from**. Viewing the person's steps on the **Steps** tab also shows the next retry time. An answered call ends the person's journey with **Replied**. See [Outbound calls](https://docs.open.cx/phone/outbound-calls.md).

For steps your team calls, every call and how it ended is in [List call attempts](https://docs.open.cx/api-reference/sequences/list-call-attempts.md): answered by an agent, missed because every agent was busy, no answer, busy or failed. The agent who took the call can mark it **Voicemail**, and the person continues, or **Wrong number**, which adds the number to the outbound blocklist and ends their journey.

## Change one person

Open the menu at the end of a person's row:

* **Details & channels** shows what the sequence knows about them and how they were scored. Their name, phone, email and WhatsApp ID can be corrected only while they are a **Candidate** or on **Needs data**.
* **Include anyway** appears for someone the criteria held back, and lets them send.
* **Take them out…** stops every remaining step. Enter why they don't belong, then confirm. They leave the list; what was already sent is kept. If you add them again later, they start from the first step.

## How people leave a sequence

| How | Result |
| - | - |
| They reply on WhatsApp or email, or answer a call | **Replied**. No more steps, even if they had finished. |
| Every channel the sequence uses is blocked for them | **Opted out**. A block on only one channel skips that channel's steps instead. |
| They reach the last step | **Finished**. A later reply still changes them to **Replied**. |
| You take them out | They leave the list. |

To react automatically, use the workflow triggers **Sequence Replied**, **Sequence Completed**, **Sequence Contact Suppressed**, **Sequence Parked** and **Sequence Step Failed**.

## The outbound blocklist

The outbound blocklist is your do-not-contact list for addresses: phone numbers, email addresses and WhatsApp accounts. A sequence never contacts a blocked address. It checks the list when people are enrolled, at launch, and again before every send, and holds the send if the list can't be read.

Entries are added for you when someone:

* unsubscribes from a sequence or template email,
* turns off marketing messages from your business in WhatsApp,
* has an email address that hard-bounces,
* is marked **Wrong number** after a team call.

Bounces, wrong numbers and entries you add also stop other messages and calls OpenCX starts to that address. Unsubscribes and WhatsApp marketing opt-outs stop sequences, but not transactional messages or satisfaction surveys. There is no dashboard page for the list: manage it with the **Add to Outbound Blocklist**, **Check Outbound Blocklist** and **Remove from Outbound Blocklist** workflow steps, or with the [outbound blocklist API](https://docs.open.cx/api-reference/outbound-blocklist/index.md). It is separate from the inbound blocklist, which stops the AI from replying to someone. To stop a whole channel for a contact instead of one address, [restrict the channel](https://docs.open.cx/contacts/manage-contacts.md#restricted-channels).

***

## Related Documentation

> [card] [Create a sequence](https://docs.open.cx/outbound/create-a-sequence.md)
>
> Steps, settings and reply handling.

> [card] [Outbound blocklist API](https://docs.open.cx/api-reference/outbound-blocklist/index.md)
>
> Block, check and unblock addresses.

> [card] [Follow-up workflows](https://docs.open.cx/phone/follow-up-workflows.md)
>
> Act on replies and call outcomes.

> [card] [Sequence stats API](https://docs.open.cx/api-reference/sequences/stats.md)
>
> The same numbers from code.


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