Campaigns

Upload a list of numbers, point one workflow at it, and let Woise work through the list as a paced batch of outbound calls.

A campaign is the outbound counterpart to Inbound: a workflow either answers calls or a campaign places them. Four terms carry the page:

Source — the file your list comes from. Each row becomes one call.
Queued run — one row, waiting to be dialled. It becomes a run once the call is placed.
State — where the campaign as a whole has got to: created, syncing, running, paused, completed, or failed.
Telephony configuration — the carrier connection the calls go out on, optionally with a number pool behind it.

Creating a campaign

A campaign is created against one existing workflow, one telephony configuration, and one source file. Upload the file, and Woise validates it before the campaign can start.

Your file has to satisfy three rules:

A phone_number column must be present.
Every number must be in E.164 form, leading + included.
No duplicates. A repeated number rejects the file rather than being called twice.

Every other column becomes a variable available to the workflow on that call, so the same workflow can greet each person by name or quote their own account detail. If your workflow's prompts reference a template variable, that variable must exist as a column and be filled in on every row — an empty cell fails validation rather than producing a call with a blank in it.

The source is imported once

When you start a campaign it moves to syncing, reads the file, and creates one queued run per row. That import happens once.

Don't treat the source as live

Starting the campaign and then editing the file — adding contacts, fixing numbers, removing people already reached — changes nothing. There is no re-sync, and a running campaign cannot be pointed at a fresh file.

Do settle the list, then start

Get the file right before you start, because the import is the only read. To make a second pass over some of the same people, use Redial, which clones a campaign from the calls that ended in dispositions you choose.

Batching and pacing

A campaign never dials its whole list at once. It works through queued runs in batches, bounded by two limits:

Your organization's concurrent-call limit — the ceiling across everything your organization is running.
The campaign's own Max Concurrent Calls — a lower ceiling for this campaign alone, capped by the organization limit and by how many numbers are actually available to call from.

A campaign can be paused and resumed at any point, and both limits are re-read when it resumes.

Why this matters

The two limits are a floor on how long a list takes, not a preference. A ten-thousand-row list at a concurrency of five is a multi-day campaign however urgent it is, so set concurrency against the number of lines you actually hold rather than against the deadline you would like to hit.

Retries

A dial that fails is retried on a schedule, never immediately. Retries are configured per campaign:

Enable retries — off means one attempt per row.
Max retries and Retry delay — how many further attempts, and how long to wait between them.
Retry on — which failures qualify: busy signal, no answer, voicemail.

Each retry is a fresh queued run rather than a re-run of the original, so every attempt keeps its own record.

Calling windows

A campaign can carry its own schedule: a timezone, and time slots per day of the week. Outside those slots, Woise stops scheduling new batches. It does not cut off a call already in progress.

What holds a call back

Some checks stop a call before it is placed, and it matters which kind you have hit, because they end differently:

Failed outright — the number is on your do-not-call list, is an emergency number, or the account is suspended from outbound calling. The queued run is marked failed with a reason, and is not retried.
Deferred — your concurrency cap is full, the number pool has no active member, or a daily cap has been reached. The queued run goes back in the queue with a later time and is picked up again.

A campaign that appears stalled is usually deferring, not failing. Check the campaign's log before concluding the list is bad.

Where results appear

Progress, pacing, and per-call outcomes are tracked on the campaign's own page while it runs, alongside an append-only log of what the campaign did and why. Once calls complete, the same runs appear in Reports and in the run history on Usage, alongside inbound and test-call activity, with their audio and transcript attached — see Recordings.