> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/outbound-calls.md).

# Outbound calls

Understand how Voice Gateway originates individual and campaign-based outbound calls.

Outbound calls let Voice Gateway reach people without waiting for an incoming call. Choose a direct call for a one-off task, or build a Campaign when many contacts need the same coordinated approach.

### Choose the right calling model

Use **Single dialing** to place one call now. It is useful for testing a destination or Route, validating an Application, or handling a call outside a Mailing.

Use **Campaign-based dialing** when the work has a schedule and a contact list. A Campaign controls timing, capacity, retries, and the conditions that determine whether a contact can be called.

### Build a campaign-based operation

A Campaign-based operation moves from broad rules to an individual call. First, define the operation. Then set its calling schedule. Finally, add the contacts and the Route that connects them.

#### Campaign

The Campaign is the operating plan. It defines the Service Application, validity period, status, channel capacity, retry limit, and redial intervals.

#### Dialing Rule

Dialing Rules define when the Campaign may dial. Select the allowed days, start and end times, and whether dialing is enabled.

#### Mailing

A Mailing connects the operation to its contacts. Select the Campaign and Route, define the Mailing dialing window, add contacts, and set its status to Active or Inactive.

#### Route

The Route determines how Voice Gateway originates the call. Create it before configuring the Mailing.

#### Do Not Disturb

Do Not Disturb protects registered numbers. A protected number is never selected for an outbound call.

```
Campaign
   │
   │ sets the operating rules
   ▼
Dialing Rules
   │
   │ sets the allowed days and times
   ▼
Mailing
   │
   │ connects contacts, Route, and dialing window
   ▼
Contact eligibility
   ▼
Outbound dialing
```

Single dialing follows a separate manual path. It does not require a Campaign or Mailing.

<figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2FRsg2T0682yz0IsLIPcIi%2Fimage.png?alt=media&amp;token=a4194aa0-9413-4fd7-b529-9494b66e0207" alt=""><figcaption><p>Outbound call administration workflow.</p></figcaption></figure>

### Understand when a contact can be called

A contact in a Mailing is not automatically ready to call. Voice Gateway checks every relevant condition before selecting a contact.

| Check          | What must be true                                                          |
| -------------- | -------------------------------------------------------------------------- |
| Campaign       | It is operational, within its validity period, and has available capacity. |
| Mailing        | It is Active and within its Dialing Window.                                |
| Dialing Rule   | It is enabled for the current day and time.                                |
| Do Not Disturb | The phone number is not protected.                                         |
| Retry policy   | A new attempt is allowed when a retry applies.                             |

The contact becomes available only when every applicable check passes.

### Set up a Campaign

Build the operation in this order:

1. Create the **Campaign** and select its Service Application
2. Add **Dialing Rules** for the permitted calling days and times
3. Create a **Mailing**, then select the Campaign and Route
4. Set the Mailing Dialing Window
5. Open **Import Contacts**, select the CSV, and validate the contacts
6. Correct any validation errors and import the valid contacts
7. Activate the Mailing.

Voice Gateway begins selecting contacts when the Mailing is active and the eligibility checks pass.

### Example: Customer Recovery

This example calls customers on weekdays during business hours. The Campaign limits concurrent calls and defines different retry intervals for busy and unanswered calls.

```
Campaign:          Customer Recovery
Period:            2026-11-01 to 2026-11-30
Allowed dialing:   Monday-Friday, 09:00-18:00
Max channels:      20
Busy retry:        300 seconds
No Answer retry:   1800 seconds
```

Create the Campaign:

```
Campaign Name:                Customer Recovery
Start Date:                   2026-11-01
End Date:                     2026-11-30
Max Channels:                 20
Busy Redial Interval:         300
No Answer Redial Interval:    1800
```

Select the corresponding **Service Application**, then save the Campaign.

Add the Dialing Rule:

```
Days:             Mon Tue Wed Thu Fri
Start Time:       09:00
End Time:         18:00
Enable dialing:   Yes
```

Create the Mailing:

```
Campaign:         Customer Recovery
Route:            previously available Route
Mailing Name:     Customer Recovery - November
Dialing Start:    2026-11-01 09:00
Dialing End:      2026-11-30 18:00
Active:           Yes
```

Prepare the contact file:

```csv
phone_number,dnis,call_data
5511999999999,1000,"customer_id=10001"
5511888888888,1000,"customer_id=10002"
```

Validate the CSV, correct any errors, and import the valid contacts. Activate the Mailing when it is ready to run.

{% hint style="info" %}
Add any protected numbers in [**Do Not Disturb**](https://docs-conversational-ai.syntphony.com/scai-voice-gateway/outbound-calls/do-not-disturb.md) before outbound dialing begins.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/scai-voice-gateway/outbound-calls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
