> 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/reusable-assets-routing-objects/audio-assets/manage-audio-assets-and-playlists.md).

# Manage Audio Assets and Playlists

Upload reusable audio files and group them into playlists for IVR, queue, and hold scenarios.

Audio files and playlists provide reusable voice assets for IVR prompts, queue messages, hold behavior, and quality-monitoring messages.

Follow the file-type, duration, and size limits shown in your administration UI when uploading audio.

## Prerequisites

Before you upload audio assets, make sure:

* you know which IVR, queue, or quality-monitoring flows will use them
* the audio files meet the requirements shown by the current upload UI
* you have permission to use the recordings you plan to upload

## Upload audio files

Upload local audio files, then select them in the IVR or quality-monitoring records that use them.

| Field                      | Use                                                        |
| -------------------------- | ---------------------------------------------------------- |
| `Name`                     | Lets the administrator browse to a local file              |
| `Title`                    | Stores the display name used when selecting the file later |
| `Overwrite existing files` | Replaces an older file with the same file name             |

<details>

<summary>Upload an audio file</summary>

1. Open the audio files list.
2. Select **Upload**.
3. Browse to the file.
4. Confirm the upload.
5. Enter the `Title` value.
6. Save the item.

</details>

<details>

<summary>Remove an audio file</summary>

1. Open the audio files list.
2. Select the existing file.
3. Choose **Delete Item**.

</details>

{% hint style="warning" %}
Before deleting an audio file, confirm that no IVR item, queue prompt, or quality-monitoring question still references it.
{% endhint %}

## Build playlists

Playlists let the contact center play several audio files in sequence for queue, hold, or break scenarios.

| Field        | Use                                    |
| ------------ | -------------------------------------- |
| `Playlists`  | Stores the playlist name               |
| `Audio File` | Selects the audio file to include      |
| `Order`      | Controls the play sequence             |
| `Active`     | Enables or disables that playlist item |

Queue and hold playback behavior is also affected by UCC settings:

| Setting                                | Use                                                                                              | Value guidance                                                      |
| -------------------------------------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- |
| `OnHoldPlayList`                       | Defines the playlist used when an agent puts the customer on hold.                               | Use a playlist prepared for the customer environment.               |
| `QueuePlayList`                        | Defines the playlist used while the caller waits in queue.                                       | Use a playlist prepared for the customer environment.               |
| `DisablePreviousPlayListPositionQueue` | Controls whether the queue playlist restarts from the first item or continues where it left off. | Default `False`; `True` always starts from the first playlist item. |
| `CombinedAudioFilePause`               | Adds a pause, in milliseconds, to the end of combined audio files.                               | Default `0`.                                                        |
| `EnableMusicOnHold`                    | Controls whether music plays when the customer is put on hold.                                   | Default `True`; set `False` for silence on hold.                    |

<details>

<summary>Create or edit a playlist item</summary>

1. Open the playlists list.
2. Add a new item or edit an existing one.
3. Enter the playlist name.
4. Select the audio file.
5. Set the order.
6. Mark the item active if it should be used.
7. Save the item.

</details>

## Copyright and content ownership

{% hint style="warning" %}
Uploaded recordings can be protected by copyright or other usage restrictions. Confirm that your organization is allowed to use each recording before uploading it.
{% endhint %}

## Verification

After preparing audio assets:

1. Attach one uploaded file to an IVR or quality-monitoring item.
2. Test playback from the contact-center flow that uses it.
3. Confirm playlists play in the intended order.
4. Confirm queue playback behaves as expected when a caller remains in queue for an extended period.


---

# 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/reusable-assets-routing-objects/audio-assets/manage-audio-assets-and-playlists.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.
