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

# Campaigns

> Build templates and Flows, define audiences, and operate campaigns.

Use these workflows when a project sends structured or high-volume communication.

<CardGroup cols={2}>
  <Card title="Send a campaign" icon="bullhorn" href="/guides/campaigns/send-a-campaign">
    Create a campaign with recipients, launch it, follow every recipient, and stop it.
  </Card>

  <Card title="Build an audience" icon="users" href="/guides/campaigns/audiences">
    Import members inline or from a CSV file, then keep the list up to date.
  </Card>

  <Card title="Opt-outs and STOP replies" icon="hand" href="/guides/campaigns/opt-outs">
    The suppression list, keyword capture, and the events that report it.
  </Card>

  <Card title="Campaign methods" icon="list" href="/api-reference/platform/campaigns/list-campaigns?playground=open">
    Every campaign, recipient, and audience method, with a live playground.
  </Card>

  <Card title="Message templates" icon="rectangle-list" href="/api-reference/messaging/templates/list-project-templates?playground=open">
    Draft, preview, submit, and manage reusable message templates.
  </Card>

  <Card title="Flows" icon="diagram-project" href="/console/flows">
    Build interactive WhatsApp Flows and manage their lifecycle.
  </Card>

  <Card title="Campaigns and number safety" icon="shield-check" href="/guides/campaigns/safety">
    The plan gate, the throughput ceilings, per-recipient holds, and the warm-up ramp.
  </Card>
</CardGroup>

Campaigns is the only bulk sending path. Every campaign send passes the plan,
throughput, opt-out, contact, and warm-up checks described in
[Campaigns and number safety](/guides/campaigns/safety).
A recipient one of those checks holds back is skipped or retried, never counted
as a delivery failure, and a check that no number in the campaign can clear
pauses the campaign instead of failing recipients one at a time.

## Work with collection tables

Campaigns, templates, Flows, audience lists, and opt-outs use the same table
controls in Console. Search across the visible properties, or open a column
heading to sort and filter by that property. Drag a heading edge to resize the
column. Console remembers column widths in that browser.

Open **More** for row actions. You can also right-click the row to open the
same menu. Campaign rows expose the campaign, status, delivery progress,
recipient count, failure count, and update time as separate columns.

The campaign methods use short public names such as “List campaigns.” Internal registry identifiers are not part of the customer contract.

## Campaign notifications

Team members receive a notification when a campaign completes or fails. Choose
email delivery for **Campaign completed** and **Campaign failed** in
[My Notifications](/console/teams-and-projects#personal-notification-settings).
Pausing or stopping a campaign does not send a completion or failure notice.


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