> 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-files.md).

# Manage audio files

Upload, replace, and remove reusable audio files that can be referenced from IVR, queue, hold, and quality-monitoring flows.

Use reusable audio files when a callflow needs recorded prompts instead of text-to-speech.

## Before you begin

* Confirm which IVR, queue, hold, or quality-monitoring flow will use the file.
* Confirm the file meets the upload requirements shown in the current administration UI.
* Confirm you are allowed to use the recording you plan to upload.

## Keep audio-file management simple

Good practice is to:

* upload only files you intend to use in a live flow
* use a clear display title so administrators can find the file later
* keep the naming pattern stable across related prompts
* replace an existing file carefully so you do not affect other live references unexpectedly

{% hint style="info" %}
Follow the current upload UI for supported file types, size limits, and any filename restrictions. Do not rely on older static format guidance if the live UI shows different limits.
{% endhint %}

## Upload an audio file

1. Open the audio-files area used by your deployment.
2. Select **Upload**.
3. Choose the local file.
4. Confirm the upload.
5. Enter the display title.
6. Save the item.

## Replace or remove an audio file

When you update an existing recording:

1. Confirm which IVR, queue, hold, or survey items still reference it.
2. Replace the file or upload the new version.
3. Test one live usage point before wider rollout.

When you remove a file:

1. Confirm no active callflow item still depends on it.
2. Delete the file from the audio-files area.
3. Remove or update any stale references.

{% hint style="warning" %}
Deleting or replacing a reusable audio file can affect multiple live callflows immediately. Check all active references before you change it.
{% endhint %}

## Verification

1. Attach one uploaded file to a callflow item that uses audio.
2. Test playback from the related IVR, queue, hold, or quality-monitoring path.
3. Confirm the file title is clear enough for later reuse by another administrator.

## Related topics

Go to **Where audio is referenced in call handling** for a reference map of the main callflow surfaces that can use uploaded audio.

{% content-ref url="/pages/MsOtr56fgYuuvwNjVRiX" %}
[Where audio is referenced in call handling](/contact-center-configuration/reusable-assets-routing-objects/audio-assets/where-audio-is-referenced-in-call-handling.md)
{% endcontent-ref %}


---

# 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-files.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.