The gates
Every dial passes through all of these, and each one fails closed. If a gate cannot determine the answer, the call does not happen.
The do-not-call list is the hard stop. A number on it is never dialled, by any campaign or rule.
Settings
Under Settings, then Outbound you control channels, sequences, quiet hours, consent posture, voicemail policy, caps, caller ID strategy and the retry ladder.How a call gets placed
Outbound calls come from two places: Trigger rules. A rule matches an event and places a call. This is the one-off, event-driven path: a call rang out, a CRM stage changed, a booking is tomorrow. Campaigns. A list of people called over time at a controlled rate.Campaigns
A campaign has an audience, a pace and an objective.Audiences
The CSV upload requires you to attest that the contacts consented to be called. This is a required
checkbox, not a dismissible warning, and the attestation is recorded.
Pacing
Calls are spread over time rather than dialled all at once. Concurrency is limited per number and per workspace, priority lanes let an urgent call jump a bulk campaign, and one workspace’s volume cannot affect another’s.Retries
A call that does not connect can be retried on a ladder you configure: how many attempts, how long to wait, and which outcomes are worth retrying (no answer, busy, failed). Retries respect every gate again, including frequency caps.Objectives
A campaign call opens with its purpose rather than a generic greeting, then converses normally. It states the objective once. It does not repeat it every turn.Measuring a campaign
The funnel, per campaign:Voicemail
Answering-machine detection is available, and your voicemail policy decides whether to leave a message, hang up, or retry later.Reporting
Every attempt is recorded with its outcome, its cost and its conversation. Call outcomes emitcall.completed and call.failed, which are available as webhooks and as
trigger sources, so a failed call can start a message.