Outbound
Work a calling list from a pool of numbers
Upload the list, set the cadence, and let it run. Every row ends in an outcome you can filter on, with the recording attached.
Incoming call
What this is for
Outbound work is bounded by seats. Four thousand rows against six people means the bottom of the list gets called three weeks after the top, by which point the reason for the campaign has gone stale. Prioritising the list does not make it shorter. Calling it does.
How a campaign runs
- 01
Takes the list as it is
Upload the rows with whatever fields they carry. Those fields are available during the call, so the agent can open with the actual service due or the actual policy number.
- 02
Calls in parallel from your numbers
Calls run concurrently from a pool of numbers rather than one at a time down a single line. The length of the list sets the duration, not the size of the team.
- 03
Follows your cadence and calling rules
Retries, gaps between attempts, permitted hours, do-not-call handling. All settings on the campaign, applied identically to every row.
- 04
Ends every row in an outcome
Booked, not interested, wrong number, no answer, callback requested. Each one filterable, each one with the recording and transcript attached.
Related
- AI lead qualificationIt calls people who have already raised their hand, asks what they are trying to do, and records the answers as fields rather than notes.
- Appointment remindersIt calls ahead of the appointment, confirms or rebooks on the spot, and updates the calendar either way.
- Phone surveysA short set of questions asked out loud, with the answers captured as structured fields instead of free text.
- Missed-call callbackA call that goes unanswered gets returned within minutes, while the person still remembers why they rang.
Outbound campaigns: common questions
How many calls can run at once?
Concurrency is a property of the campaign, not a headcount. The practical ceiling is the capacity provisioned on your account rather than how many people are logged in.
Can it leave a voicemail?
Yes, if you build that branch. You can also have it hang up silently and retry later, which usually works better on lists where a voicemail burns the attempt.
How does it handle do-not-call requests?
A request on the call is captured as an outcome and suppressed from further attempts. You remain responsible for the calling rules in your jurisdiction. The agent applies the settings you configure.
Can the script differ per row?
The row's fields are available in the conversation, so one flow can open differently for a service reminder and a renewal. You do not maintain two campaigns to do it.
What do I get at the end?
A row-level result set: outcome, the structured fields collected on the call, recording, transcript. A filterable list rather than a summary.
Still stuck? Talk to our team.