> 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 campaign

## Campaign List

The **Campaigns** page shows all campaigns in your workspace with their name, start date, end date, and current status.

<figure><img src="/files/9SE2CFVSAcwcazUNJtcJ" alt=""><figcaption></figcaption></figure>

* Use the **Search campaigns** bar to filter by name.
* Click **Order** to sort by any column.
* Click any row to open the campaign detail page.

### Row actions

Click the **⋮** icon at the end of any row to access quick actions:

<figure><img src="/files/ivMuNBVfWVmuE8Jl2uDE" alt=""><figcaption></figcaption></figure>

| Action        | Description                                           |
| ------------- | ----------------------------------------------------- |
| **Edit**      | Re-open the creation wizard to change any setting.    |
| **Pause**     | Pause an active campaign. Dispatch stops immediately. |
| **Duplicate** | Create a copy of the campaign with the same settings. |

***

## Campaign Detail Page

Click a campaign row to open its detail page. The page header shows the campaign name, its current status badge, and an activation toggle.

<figure><img src="/files/hgcWK009c6zSK4RNJTyj" alt=""><figcaption></figcaption></figure>

The detail page has two tabs: **Settings** and **Conversations**.

***

## Settings Tab

The Settings tab lets you view and edit all campaign configuration.

<figure><img src="/files/5GJpqHtyXz0VjvCct7Yp" alt=""><figcaption></figcaption></figure>

**Create your campaign** section:

* **Campaign Name** — editable at any time.
* **Campaign Objective** — optional internal description (up to 500 characters).
* **Channel** — the WhatsApp number sending messages.
* **Template** — the approved WhatsApp template being used.

**Schedule your campaign** section:

* **Start date / End date** — campaign date boundaries.
* **Contact days** — Every day, Weekdays, or Custom.
* **Time zone** — all send windows are evaluated in this zone.
* **Time slots per day** — the hours during which messages can be dispatched.

A **Campaign summary** at the bottom of the form confirms the schedule in plain language before you save.

Click **Save changes** to apply any edits.

***

## Conversations Tab

The Conversations tab shows every contact in the campaign alongside their delivery status and inbox conversation.

<figure><img src="/files/pqeQLJeR3g7nVO5yKjeO" alt=""><figcaption></figcaption></figure>

| Column                   | Description                                               |
| ------------------------ | --------------------------------------------------------- |
| **Phone number**         | The recipient's phone number.                             |
| **From number**          | The WhatsApp channel number that sent the message.        |
| **Contact**              | Contact name from your file.                              |
| **Delivery**             | Whether the template message was sent successfully.       |
| **Conversation**         | Status of the inbox conversation started by a reply.      |
| **Last message**         | Timestamp of the most recent message in the conversation. |
| **Last message preview** | A preview of the last message content.                    |

Use the **Search by phone number** bar to find a specific contact. Click any row to open the linked conversation in the inbox.

***

## Campaign Controls

### Activation toggle

The toggle in the page header enables or disables the campaign. When the campaign is active and within a scheduled window, dispatch runs automatically.

### Status badge

The status badge next to the campaign name shows the current lifecycle state. See [Message Logic & Limits](/ai-text-agents/campaigns/message-logic-and-limits.md) for a full description of each status.

| Status                   | What it means                                                     |
| ------------------------ | ----------------------------------------------------------------- |
| **Waiting for schedule** | Campaign is configured but the start date has not arrived yet.    |
| **Running**              | Actively dispatching messages to contacts.                        |
| **Waiting — Schedule**   | Outside send windows; resumes automatically at the next window.   |
| **Waiting — Tier**       | Daily Meta messaging limit reached; resumes when limit resets.    |
| **Paused**               | Manually paused. Click **Resume** to continue.                    |
| **Completed**            | All contacts processed or end date reached.                       |
| **Cancelled**            | Manually cancelled. Remaining contacts will not receive messages. |

{% hint style="info" %}
**Waiting — Tier** is a normal operating state. Your campaign resumes automatically once your WhatsApp account's 24-hour dispatch window resets with Meta.
{% endhint %}


---

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