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

> ## Agent Instructions
> Use Gomobile customer-facing vocabulary.
> Do not infer support for internal, hidden, experimental, or unreleased features.

# Large audience campaigns

> Review enrollment and test the experience before reaching a larger audience.

## Before you begin

Import contacts and resolve invalid rows. Decide whether membership should be a fixed static list or a continuously matching live audience. No audience-size or throughput guarantee is established here.

**1. Prepare the audience**

[Create an audience](https://docs.gomobile.ma/quickstarts/create-audience.md) and review its membership and required contact data.

**2. Configure the experience**

Validate the complete flow on a small static test audience. Review required values, calling hours, timezone, available numbers, retries, and credits before configuring the intended campaign.

**3. Test the workflow**

[Save and test the flow](https://docs.gomobile.ma/getting-started/build-first-flow.md) with contacts and numbers you control. Check each relevant branch and required value.

**4. Review and launch**

Follow [Launch your first campaign](https://docs.gomobile.ma/getting-started/launch-first-campaign.md). Check audience, flow, schedule, calling policy, and channel resources in the summary before launch.

## Expected result and verification

Monitor enrolled contacts, tries, outcomes, and credits. A static launch uses its membership snapshot; a live audience can continue enrolling matching contacts while running.

## Troubleshooting

If work does not begin, check campaign state, schedule, calling hours, audience eligibility, saved flow validity, resources, and credits. For an individual failure, inspect the run path and associated call activity.

See [campaign lifecycle](https://docs.gomobile.ma/product/campaign-lifecycle.md) for enrollment, retries, pause, and stop behavior.


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