Campaign recipients
Add recipients to a campaign by hand or by CSV, then read their statuses, every call attempt and the exported results.
Recipients are the list an outbound campaign dials. Each one is a phone number, optionally a name, and optionally a note. They are typed in one at a time, imported by CSV, or taken from the contacts that match the campaign's audience when it launches. Australian mobiles and landlines are accepted in local or international form. Recipients can only be added, or removed, while the campaign is a draft. Once it launches you can stop a recipient instead.
Import a CSV
Upload a file with a header row. The importer asks you to map four columns.
| Mapping | Required | Notes |
|---|---|---|
| Phone column | Yes | The number to dial. Local or international form. |
| Name column | No | Used to address the person. |
| Notes column | No | Context the agent reads like memory of that person. |
| Time zone or state column | No | Where the person is, so they are called in their own local time. See Local time. |
A template is available from the import panel:
phone,name,state,notes
+61412345678,Alex Example,WA,Prefers mornings
0298765432,Sam Example,,Local time
Each recipient is called by their own local time, so one campaign can run across states. The dialer works out where a person is in this order:
- The time zone or state column. A state or territory code (
NSW,VIC,QLD,WA,SA,TAS,ACT,NT, in any case) or a time zone name such asAustralia/Perth. A state, or an Australian time zone, also means that state's public holidays are skipped for that person. A column headedstate,timezone,time zoneortzis mapped for you. - A landline's area code, where the code maps to one clock:
02is read as Sydney time,03as Melbourne time and07as Brisbane time.08covers Western Australia, South Australia and the Northern Territory, which keep different clocks, so it is never inferred. An area code gives a clock but not a state, so it adds no state holidays. - The campaign's time zone: the calling window's, or the agent's when the
campaign uses the standard hours. Mobiles always land here when the column
is blank. The state of that zone, such as WA for
Australia/Perth, sets the public holidays skipped.
A value that is neither a state code nor a time zone rejects the row, with the reason, rather than calling the person at the wrong hour. The mapped column also stays a variable, so the agent can read the state. With the column mapped, the import preview shows each person's time zone and where it came from.
Recipients added through the API or the assistant take the same value in their
timezone field.
Recipients become contacts
Every recipient added to a campaign is also added to the workspace's contacts, or updates the contact with that number: its name, and any column whose name matches a contact field. The recipient keeps its own variables, which are what the agent reads on the call.
Unmapped columns become variables
Every column you do not map becomes a per-lead variable, keyed on a
simplified version of its header, so a column headed Home Suburb arrives as
home_suburb. Blank cells are skipped. The import preview shows each variable
as a column.
The variables are saved with each recipient, whether you import them here or
add recipients through the API or the assistant. The agent is told them on
that recipient's call, and an opening line can use one, such as
{{home_suburb}}.
Under the preview, What … will hear shows the opening line and voicemail for the file's first row, with its columns filled in, and flags any column the line needs that is empty for that person. See Hear it before you launch.
What the importer rejects
Before the rows are saved:
- Invalid numbers are rejected and reported back row by row, with the reason.
- Duplicates are dropped, within the file, within the batch, and against recipients already on the campaign.
- Numbers on your do-not-call list are removed and never inserted.
The result is reported as a count of recipients added, skipped and suppressed.
Import limits
An import is capped at 5000 recipients at a time; import again to add more. A name is limited to 200 characters, a note to 2000, and any other variable value to 1000.
Recipient statuses
Each recipient carries one of eight statuses, and three more readings for a sequence with SMS steps.
| Status | Meaning |
|---|---|
| Pending | Not yet called, waiting for a retry or the next step of the sequence, or waiting for a callback the person asked for, with the outcome Callback scheduled. |
| Calling | A call is in flight. |
| Reading the call | The call connected and its outcome is decided once its analysis lands, usually within a minute or two. |
| Connected | The call was answered and the sequence ended on its outcome. |
| Not reached | Every attempt of the last step ended without reaching anyone. The outcome says which: no answer, busy or voicemail. |
| Failed | The call could not be completed. |
| Cancelled | Not called again, because the campaign was cancelled or the number was suppressed. The outcome says which: Campaign cancelled or Suppressed. |
| Stopped | You stopped them, so they are not called again. The Cancelled status filter includes them, and the Stopped outcome filter finds only them. A campaign that keeps adding contacts who match also stops a recipient its audience added who no longer matches, with the outcome Left audience. |
| Texting | Their SMS step's text has gone, and the next step waits for the carrier to confirm it, at most 15 minutes. The Reading the call filter includes them. |
| Replied | They replied to a campaign text, which ended their sequence with the outcome Replied. The Connected filter includes them. |
| Texted | Their sequence ended on a text. The Connected filter includes them. |
The recipients table also shows the attempt count, last attempt, outcome, summary and a link to the transcript. A pending recipient whose local calling hours are closed shows its next attempt at the time those hours next open. Search the table by name or phone, and filter it by status or outcome. Select a recipient to see every call attempt with its result, talk time, outcome, summary, and a link to the call's transcript and recording, along with their time zone and state when the import set them (see One recipient's calls).
Remove a recipient
On a draft, open the recipient's ⋯ menu in the recipients table and choose Remove from campaign, then confirm. They come off the list. Once the campaign has launched its list is fixed, and Remove gives way to Stop calling.
Stop a recipient
On a scheduled, running or paused campaign, open the recipient's ⋯ menu and choose Stop calling, then confirm. The menu appears on recipients who are waiting, on a call or having their call read.
- A recipient waiting to be called, or waiting for a retry, becomes Stopped at once.
- A recipient on a call keeps the call: nothing hangs up. If the call connects it is recorded as usual. If it doesn't, the recipient becomes Stopped, with no retry. Until the call ends the row says it will not be called again.
Either way the campaign never dials them again. Stopping a recipient does not put the number on the do-not-call list; add it there as well if they asked not to be called. Removals and stops are recorded in the workspace audit log.
Retries
A recipient that does not connect is retried after each attempt's wait until their step runs out of attempts. The step then ends as No response and moves on to the next step, or ends the sequence on the last one. A connected call's outcome and summary are copied onto the row once its analysis lands.
With double dial on, a call nobody picks up is rung once more straight away before the retry wait starts. The second ring uses no attempt.
A callback the person asks for replaces the retry: they are called at the time they chose instead, and the callback uses no attempt.
Two exceptions:
- A recipient whose number turns out not to be dialable fails immediately without a retry.
- A transient problem, such as the platform being briefly unavailable, puts the recipient back to pending without using an attempt. The sixth in a row fails them with the outcome Dial failed.
The attempts and the waits between them are set on each step of the sequence.
Where the calls show up
Campaign calls appear in Calls and analytics like any other call, with a transcript, analysis and recording (when enabled).
Export the results
Once any recipient has settled, Export CSV downloads the full list: phone,
name, status, attempts, last attempt, next attempt, outcome, summary, session
identifier, last result (connected, no answer, busy, voicemail, failed, calling,
stopped, cancelled, replied or texted), converted, cost, recipient identifier,
which matches the
campaign object in webhook events,
time zone, the callback time and note of a recipient waiting for a
callback, and for
SMS steps Texts (how many were sent),
Last text (sending, sent, delivered or not delivered) and
Text reply, the first reply the person sent. Converted is yes or no when the campaign tracks
conversion, and empty when it does not.
Cost (AUD) is what every call and text to the recipient was charged, in dollars, as
in Costs and spend caps; it is
0.00 for a recipient called without reaching anyone, and empty for one never
called.
Timezone holds the state or time zone the recipient was imported with, in
the form the import takes, so the file imports back the same; it is empty for a
recipient called in their area code's or the campaign's time zone.
Outbound campaigns
Dial an imported list of recipients, or the contacts that match a filter, through one of your agents, with a consent gate and a do-not-call list.
Contacts
The people your campaigns can call, with tags, your own fields and a do-not-call badge, kept apart from what your agents remember about callers.