> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-text-agents/campaigns/managing-your-campaign.md).

# Managing your sequence

Monitor sequence status, edit schedules, pause sending, and investigate recipient outcomes.

Open **Text Agents → Sequences**, search for the sequence, and open it. Confirm the sending line and status before changing anything.

## Use the detail tabs

| Tab           | Use it for                                                                                                                      |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Settings      | Review the message configuration and schedule; configure optional call fallback. Click **Save changes** after edits.            |
| Conversations | Find recipients by phone number, inspect delivery and conversation status, and open available conversation history.             |
| Connections   | Review already-connected contact sources and their synchronization status. Source availability depends on the sequence's setup. |
| Metrics       | Review that sequence's results. Do not confuse sent/delivered counts with replies or successful conversations.                  |

A recipient with no conversation yet is not necessarily missing from the import. Inspect its delivery state and reason first.

## Pause, resume, and edit

Use the active switch or the available pause/resume action. Wait for the operation to succeed and confirm the status changed. A terminal sequence cannot be resumed with the active switch.

Pausing stops further processing; it does not retract messages already accepted by a provider. Before resuming, resolve template/line issues and recheck the sending schedule. Resuming does not bypass [message rules and limits](/ai-text-agents/campaigns/message-logic-and-limits.md).

To change a schedule, edit it in **Settings**, save, and verify the result. You can clear an existing end date to make the sequence open-ended. Existing queued work still follows the saved schedule and provider protections.

## Operate an open-ended sequence

**Waiting for contacts** is expected when there is nothing eligible to send. The sequence can process new recipients supplied through a supported route. It does not restart previously processed contacts just because the list is imported again.

If outreach is finished, use the available pause or cancellation workflow rather than leaving an open-ended sequence unintentionally active. Cancellation is not a resumable pause; if no cancellation action is available to your role, ask the workspace administrator/support.

## Investigate recipient results

1. Open **Conversations** and search the phone number.
2. Read delivery state and the accompanying failure/suppression reason.
3. Open its conversation, when available, to distinguish outbound initiation from an actual customer reply.
4. For **Awaiting first reply**, use that explicit filter in [Inbox](/ai-text-agents/inbox.md).
5. If call fallback is enabled, inspect its separate result. A call result does not change the WhatsApp delivery result.

Do not use duplication or re-import to bypass opt-outs, suppression, or provider limits. Review [importing contacts](/ai-text-agents/campaigns/importing-contacts.md) before adding another batch.

*Source review: September 17, 2026.*

{% content-ref url="/pages/3IUmiIqvNy2PCTCUH36g" %}
[Call fallback](/ai-text-agents/campaigns/call-fallback.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/ai-text-agents/campaigns/managing-your-campaign.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.