> 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/autonomous-dialer.md).

# Configure the Autonomous Dialer

Configure and validate the Autonomous Dialer for Dialogue Cloud Neo (Connect).

The Autonomous Dialer automatically calls telephone numbers from configured call-list records and plays the configured IVR flow.

{% 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 %}

## Before you begin

* Confirm that Autonomous Dialer is licensed and enabled for the customer environment.
* Confirm that the contact center, IVR flow, business hours, and holiday schedule are ready for the intended outbound use case.
* Confirm that administrators understand which call-list records are eligible to be processed.
* Prepare approved text-to-speech or audio messages before adding live records.

## Configure Autonomous Dialer settings

Configure the Autonomous Dialer settings for the environment.

| Setting                          | Purpose                                                             | Value or default                        |
| -------------------------------- | ------------------------------------------------------------------- | --------------------------------------- |
| `EnableAutonomousDialer`         | Enables or disables processing of Autonomous Dialer call records.   | `True` or `False`; default `False`.     |
| `StartAutonomousDialerOnStartup` | Starts the Autonomous Dialer engine during startup.                 | Default `False`.                        |
| `OutboundDialerDeclineRetry`     | Specifies the number of retry attempts.                             | Default `3`; configure per deployment.  |
| `OutboundDialerDeclineRetryTime` | Specifies the number of minutes between retry attempts.             | Default `15`; configure per deployment. |
| `MaxDialerSessions`              | Sets the maximum number of simultaneous Autonomous Dialer sessions. | Default `0`; `0` means no limit.        |

{% hint style="warning" %}
Changing startup behavior may require a service restart or planned change window. Confirm the operational procedure for the customer environment before applying the change.
{% endhint %}

## Activate or stop processing

Set `EnableAutonomousDialer` to `True` to allow the dialer to process eligible records. Set it to `False` to stop processing new records.

After changing the setting:

1. Confirm that the setting value is saved.
2. Confirm whether the change requires a restart or operational action in the customer environment.
3. Add or update only a controlled test record.
4. Validate that the dialer calls only during the intended business-hours and schedule window.

## Manage call-list records

Autonomous Dialer records contain the destination, optional pre-welcome message, schedule, priority, and processing state. Manage these records through the call-list location used by the customer environment.

For field-level guidance, see [Manage Autonomous Dialer call lists](/operate/maintain-and-change/autonomous-dialer-call-list.md).

## Example behavior

A typical Autonomous Dialer flow:

1. The dialer selects an eligible call-list record.
2. The dialer calls the configured telephone number or SIP identity.
3. When the customer answers, the configured IVR flow is played.
4. The customer's IVR path can be used for reporting.
5. If the call is not completed, retry handling follows the configured retry settings.

Do not rely on this page for full IVR design. Build and test the IVR flow in the applicable callflow tooling before enabling production dialing.

## Handle calls answered by voicemail

Autonomous Dialer cannot detect when a customer's voicemail greeting starts, ends, or reaches the recording beep. The dialer starts its configured announcements immediately, so the voicemail greeting and the IVR audio can overlap. Design the sequence so that its final audio fragment contains the most important information for the customer.

To finish the IVR with a standard closing message when no choice is received:

1. Create the IVR choices that the customer should be able to select.
2. Edit **Welcome Message** in the **IVR Questions** list.
3. Set **Action** to `Disconnect`.
4. Set **Choice Timeout** to the number of seconds customers should have to select an IVR choice. For example, use `5` seconds.
5. In **Answer** or **AudioAnswer**, configure a closing message that explains that no choice was received, the call may have reached voicemail, and another attempt may follow.
6. Save the item.

Increase **Choice Timeout** if customers need more time or the IVR messages should repeat additional times before the closing message. Test the complete audio sequence against voicemail greetings of different lengths; audio played before the recording beep is not stored in the customer's voicemail.

## Validate the configuration

* Verify that the dialer remains disabled until the list, IVR, business hours, and retry settings are ready.
* Test with one controlled record before adding a production batch.
* Confirm that priority and scheduling fields produce the expected call order.
* Confirm that results are recorded in the reporting or list location used by the environment.


---

# 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/autonomous-dialer.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.