> 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/operate/maintain-and-change/autonomous-dialer-call-list.md).

# Manage Autonomous Dialer call lists

Manage Autonomous Dialer call-list records for Dialogue Cloud Neo (Connect).

Use this page to manage the call-list records used by the Autonomous Dialer workflow.

For dialer configuration, see [Autonomous Dialer](/contact-center-configuration/manage-outbound-dialing/autonomous-dialer.md) in Contact center configuration.

{% 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, configured, and enabled.
* Confirm which administrators are allowed to create, edit, and delete call-list records.
* Confirm which text-to-speech messages and audio assets are approved.
* Confirm the business-hours, holiday, and schedule windows for the campaign.

{% hint style="warning" %}
Call-list changes can affect live outbound calling. An incorrect number, schedule, priority, or message can cause the dialer to call the wrong recipient or call at the wrong time.
{% endhint %}

## Call-list fields

| Field                       | Behavior                                                                                                                             |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| `Invite`                    | Telephone number or SIP identity to call.                                                                                            |
| `Processed`                 | Indicates whether the item has already been processed. Reset only when the same contact should be eligible for another call attempt. |
| `Order`                     | Controls the call order.                                                                                                             |
| `Prio`                      | Gives the entry priority over other records and can overrule `Order`.                                                                |
| `Pre-Welcome Message`       | Text-to-speech message played before the call continues into the IVR flow.                                                           |
| `Pre-Welcome Audio Message` | Audio message played instead of the text field when present.                                                                         |
| `Day`                       | Limits processing to a specific day. An empty value ignores the day filter.                                                          |
| `Date start`                | Earliest date when the record can be processed.                                                                                      |
| `Time start`                | Earliest time of day when the record can be processed.                                                                               |
| `Time end`                  | Latest time of day when the record can be processed.                                                                                 |
| `Date end`                  | Latest date when the record can be processed.                                                                                        |

## System-managed fields

| Field     | Behavior                                                                                                                  |
| --------- | ------------------------------------------------------------------------------------------------------------------------- |
| `Agent`   | SIP identity of the agent associated with the dialer call, when applicable.                                               |
| `Result`  | IVR path or result information from the latest processed attempt.                                                         |
| `Retries` | Retry count controlled by the configured retry settings. When the retry limit is reached, the record is marked processed. |

## Create a call-list record

1. Open the Autonomous Dialer call-list location for the customer environment.
2. Create a new Autonomous Dialer record.
3. Enter the destination in `Invite`.
4. Configure priority, schedule, and pre-welcome message fields as required.
5. Save the record.

## Edit a call-list record

1. Open the Autonomous Dialer call-list location.
2. Select the existing record.
3. Update only the fields required for the correction.
4. Save the record.

## Remove a call-list record

1. Open the Autonomous Dialer call-list location.
2. Select the record.
3. Delete the record only after confirming that it is no longer needed for reporting or operational follow-up.

## Operational guidance

* Review date and time windows before saving changes.
* Reset `Processed` only when a repeat attempt is intentional.
* Keep text-to-speech and audio-message content aligned.
* Test one controlled record before adding or importing a larger set.


---

# 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/operate/maintain-and-change/autonomous-dialer-call-list.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.