> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/contact-center-configuration/manage-outbound-dialing.md).

# Configure outbound dialing

Configure Connect-only outbound dialing features for Dialogue Cloud Neo.

Use this section to configure outbound dialing features for Dialogue Cloud Neo (Connect).

Configuration guidance stays in Contact center configuration. For live call-list work, go to:

* [Manage Autonomous Dialer call lists](/operate/maintain-and-change/autonomous-dialer-call-list.md)
* [Manage outbound dialer call lists](/operate/maintain-and-change/outbound-dialer-call-list.md)

{% hint style="info" %}
This guidance applies to Dialogue Cloud Neo (Connect). Dialers are not available for Dialogue Cloud Neo (Unify). For the deployment-model differences, see [Connect vs Unify](/set-up-dialogue-cloud-neo/connect-vs-unify.md).
{% endhint %}

Outbound dialing is license-gated. Confirm that the customer environment is entitled to use the required dialer before enabling it or adding call-list records.

## Dialer types

| Dialer                                                                                          | Use it for                                                              | Administrator focus                                                                                 |
| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| [Autonomous Dialer](/contact-center-configuration/manage-outbound-dialing/autonomous-dialer.md) | Automatically call numbers and play the configured IVR flow.            | Enable the dialer, manage autonomous call-list records, and validate IVR/reporting behavior.        |
| [Campaign Dialer](/contact-center-configuration/manage-outbound-dialing/campaign-dialer.md)     | Find an available agent first, then call the customer into the session. | Configure the dialer, manage outbound call-list records, and validate retry and voicemail handling. |
| [Voicemail Dialer](/contact-center-configuration/manage-outbound-dialing/voicemail-dialer.md)   | Distribute stored voicemail messages to agents for handling.            | Configure queue behavior, prompts, and delivery handling for voicemail sessions.                    |

## Before you begin

* Confirm that the service uses Dialogue Cloud Neo (Connect), not Dialogue Cloud Neo (Unify).
* Confirm that outbound dialing is licensed and enabled for the customer environment.
* Confirm who is allowed to change dialer settings and live call-list records.
* Plan a change window for startup-related setting changes that may require a service restart.
* Test the callflow, routing, skill, and business-hours behavior in a non-production or controlled production window before adding production records.

## Operational safety

{% hint style="warning" %}
Dialer settings and call-list records can trigger live outbound calls. Validate destination numbers, skill selection, scheduling windows, audio prompts, and retry behavior before enabling processing.
{% endhint %}

Keep callback phone-number validation and normalization with the callback or callflow guidance for the environment. This section describes the dialer behavior and list records, not the full callback callflow design.

## Live call-list operations

After configuring a dialer, manage its live call-list records in Operate & support:

* [Manage Autonomous Dialer call lists](/operate/maintain-and-change/autonomous-dialer-call-list.md)
* [Manage outbound dialer call lists](/operate/maintain-and-change/outbound-dialer-call-list.md)


---

# 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://atlas.anywhere.now/contact-center-configuration/manage-outbound-dialing.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.