Outbound campaigns

What a deployment is

A deployment is one campaign instance: a Finn, an audience, a from-number, and a schedule bound together.

Finn + Audience + Phone Number + Schedule = Deployment

The same Finn can run several deployments at once against different audiences or schedules. They are independent and do not share pacing.

In the dashboard, open Dynamic Deployments in the sidebar, or click Deploy from a Finn's page. You can also launch an outbound deployment through the API with POST /deployments: one number, 1 to 5 parallel calls, starting immediately (scheduling isn't supported there). See api-deployments.

Where deployments live

A scheduled deployment moves to Live automatically at its start time.

Batch types

Standard dials contacts one at a time, or in small concurrent batches depending on your plan. Use it for moderate volume, up to a few thousand contacts, and for cases where gentle pacing matters.

Parallel is an enterprise type that dials thousands of contacts at once. Use it for time-sensitive sweeps where the whole audience must be reached in a tight window.

Parallel fails without enough phone-number capacity. You cannot dial thousands of calls from a single number, so provision a number pool first. Each number in the pool carries at most 5 concurrent calls, so max parallel calls cannot exceed the pool size times 5. See phone numbers and concurrency.

Required and schedule fields

Retries and follow-up

A deployment has no retry cap or retry interval setting. For follow-up logic such as retrying a no-answer, branching on the call result, or sending a text after a pickup, use Sequences.

Recording is set per deployment with Save recordings in the deploy dialog. It starts switched on; through the API, recording_enabled defaults to false. For recording notices and do-not-call obligations, see compliance and recording-consent.

Monitoring, pausing, stopping

Live Deployments shows call counts (completed and failed), active calls, a success rate (completed calls over calls dialled), average duration, and a live per-call table with status, duration, from and to numbers, end reason, and voicemail.

Pause stops new dials. Active calls finish normally, no new cost accrues, and you can resume. Stop does the same and marks the deployment completed, which cannot be reversed. Calls in progress are never cut off mid-conversation.

Before you launch

• Test the Finn on yourself with Test → Phone call.
• Validate the audience. Remove invalid numbers and leftover test numbers from earlier imports.
• Check the from-number's Health score in Settings → Phone numbers. See spam-labeling.
• Check the scheduled start time and time zone against your contacts' local time.
• Define your post-call analysis fields. Without them you cannot measure the run. See post-call-analysis.
• Read the cost estimate in the launch confirmation, and start with a small audience on early runs.

What goes wrong

Costs are per-call telephony plus per-minute AI cost, rolled up nightly. The confirmation modal estimate is based on average call duration and will differ from the actual charge.