Outbound
Point an agent at a list and let it work through it. Every call keeps its recording, its transcript and an outcome you can filter on.

The size of an outbound programme is usually set by how many people you can put on phones, not by how many rows are worth calling. So lists get prioritised, the bottom never gets rung, and nobody finds out whether the bottom was any good.
Rows with whatever fields they carry. Those fields are available in the conversation, so the agent opens with the actual renewal date or the actual registration.
Retries, the gap between attempts, the hours calling is allowed, and how do-not-call requests are handled. Applied identically to every row.
Calls go out concurrently from a pool of numbers. The length of the list drives how long it takes, not the size of the team.
Every row ends in a result you can filter on, with the recording and transcript attached to each one.
Concurrency is a property of the campaign rather than a headcount. The ceiling is the capacity provisioned on your account.
If you build that branch, yes. You can also have it hang up and retry later, which usually works better on lists where a voicemail burns the attempt.
A request on the call is recorded and suppressed from further attempts. You stay responsible for the calling rules in your jurisdiction, and the agent applies the settings you configure.
The row's own fields are available in the conversation, so a service reminder and a renewal can share one flow and still open differently.
A row-level result set: the outcome, the structured fields collected on the call, the recording and the transcript. A list you can filter, not a summary.
Still stuck? Talk to our team.