> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vorel.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Outbound

> Outbound calling and campaigns: consent gates, quiet hours, pacing, retries, audiences and cost per booking.

Vorel can call customers, not just answer them. Outbound is gated more heavily than anything else in
the product, because the failure mode is calling someone who did not want to be called.

<Warning>
  Outbound calling is regulated, and the rules differ by jurisdiction. Consent, calling hours and
  do-not-call obligations are your responsibility as the business placing the call. The gates below
  help you comply; they do not make compliance automatic.
</Warning>

## 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.

| Gate               | What it checks                                                   |
| ------------------ | ---------------------------------------------------------------- |
| **Consent**        | Whether this contact may be called under your configured posture |
| **Do-not-call**    | Whether the number is on your suppression list                   |
| **Quiet hours**    | Whether it is an acceptable time in the contact's timezone       |
| **Frequency caps** | How often this person has already been contacted                 |
| **Cost caps**      | Your daily and per-campaign spend limits                         |

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](/automation/triggers) 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

| Source           | How it works                                                                  |
| ---------------- | ----------------------------------------------------------------------------- |
| **Contact list** | Upload a CSV. A consent attestation is required before the upload is accepted |
| **CRM segment**  | Pull a list from your CRM directly. Available where your CRM supports it      |

<Note>
  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.
</Note>

### 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:

```
Enqueued → Dialed → Connected → Conversed → Booked
```

Alongside spend, which gives you **cost per booking**, the number that decides whether outbound is
worth running at all.

"Booked" is derived from appointments actually created in the campaign's conversations, not from
what the agent claimed on the call.

## 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 emit
`call.completed` and `call.failed`, which are available as [webhooks](/integrations/webhooks) and as
[trigger sources](/automation/triggers), so a failed call can start a message.