> 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/outbound-dialer-call-list.md). # Manage outbound dialer call lists Manage Campaign Dialer call-list records for Dialogue Cloud Neo (Connect). Use this page to manage the call-list records used by agent-assisted outbound dialing workflows, including Campaign Dialer records. For dialer configuration, see [Campaign Dialer](/contact-center-configuration/manage-outbound-dialing/campaign-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 Campaign Dialer is licensed, configured, and enabled. * Confirm which skill should be assigned to each call-list record. * Confirm which administrators are allowed to create, edit, and delete call-list records. * Confirm which voicemail text and audio content are approved. {% hint style="warning" %} Call-list changes can affect live outbound calling. A wrong target number, skill, schedule, or voicemail prompt can immediately affect production dialing. {% endhint %} ## Call-list fields The exact title of the underlying list can vary by environment. Use the outbound dialer call-list location configured for the customer environment. | Field | Behavior | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | `Title` or destination field | 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 attempt. | | `Skill` | Skill used to find an available agent before the customer is called. | | `Order` | Controls the call order. | | `Prio` | Gives the entry priority over other records and can overrule `Order`. | | `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. | | Voicemail text field | Text-to-speech content used when the workflow handles a voicemail outcome. | | Voicemail audio field | Audio content used instead of voicemail text when configured. | ## System-managed fields | Field | Behavior | | --------- | ------------------------------------------------------------------------------------------------------------------------- | | `Agent` | SIP identity of the agent who handled the dialer call. | | `Result` | Result of the most recent attempt. | | `Retries` | Retry count controlled by the configured retry settings. When the retry limit is reached, the record is marked processed. | ## Voicemail handling Agents can mark a customer call as voicemail by pressing `*` when that behavior is configured. The workflow can then play voicemail-specific messaging and apply voicemail retry or disconnect behavior. ## Create a call-list record 1. Open the outbound dialer call-list location for the customer environment. 2. Create a new record. 3. Enter the destination number or SIP identity. 4. Select the skill that should hunt the agent. 5. Configure schedule, priority, and voicemail fields as required. 6. Save the record. ## Edit a call-list record 1. Open the outbound 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 outbound 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 * Confirm the assigned skill can route the call to the correct agent group before activating a new record. * Review date and time limits before saving changes. * Keep voicemail text and audio content synchronized. * 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/outbound-dialer-call-list.md?ask=&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.