Create and schedule a Dialer campaign

Dialer campaigns call a defined audience with a published voice agent. A Standard campaign uses selected contacts or an imported list. An Auto-enroll campaign adds contacts as they match saved rules.

Outbound calling is currently gated in production. You can prepare a campaign, but launch requires account activation, usable credit where billing applies, a verified source number and permitted destinations. Saving a campaign does not authorize calls by itself.

Build the campaign

1. Open Dialer → Create new campaign and choose Standard or Auto-enroll.
2. Give the campaign a descriptive name. In Contacts, select the audience or import the supported spreadsheet/CSV list. Review phone numbers, preferred language, calling consent and do-not-call fields.
3. For Auto-enroll, choose whether all or any conditions must match. Filter on supported contact fields or configured custom fields. Preview the audience before activation.
4. In Sequence, select the Voice agent and Campaign language. Use a published agent and review its task, tools and escalation rules.
5. Set the attempts and retry rules. The first attempt starts at minute 0; later offsets must increase. Keep retries limited and meaningful for the request.
6. Set the fixed Timezone, Calling window and allowed days. Use an IANA timezone such as America/New_York.
7. In Numbers, select the source number and Maximum concurrent calls. Account, carrier and runtime limits can lower effective concurrency.
8. In Overview → Launch timing, choose immediate or scheduled launch. Check the date/time in the selected timezone.
9. Save, then review Review campaign launch before confirming Launch campaign when available.

Watch outcomes

Review contact-level status, attempt count, last outcome, next attempt and blocked reason. A queued contact has not been called. Do-not-call requests and consent changes should stop further outreach rather than being overridden by retry settings.

Pause a campaign while investigating unexpected behavior. For an uncertain carrier operation, check its status before attempting a replacement call. Do not assume every failed result means no call reached the recipient.

For workflows that branch on a call result and send an SMS or wait for a callback, use Deploy Flows. An agent’s conversation flow controls one conversation; a Deploy Flow coordinates work across events and sessions.