# Bulk Uploading Audio Prompts

## Introduction

The Audio Manager allows you to upload your own human-recorded audio files for any or all prompts in an application. While you can upload your recorded audio files one-by-one to the desired prompts, you may want to upload files for multiple prompts all at once.

This guide describes how to bulk upload audio prompts in the Audio Manager. In summary, you will complete the following steps:

1. Exporting all prompt filenames
2. Renaming your audio files to match your target prompts
3. Adding these renamed audio files to a `.zip` archive
4. Uploading the `.zip` archive to apply the renamed audio files
5. Testing your new audio prompts

{% hint style="info" %}
**Note:** Bulk uploading is meant to make multi-file uploads of audio prompts efficient. However, this will work even if you are uploading for only one.

This guide assumes that your Fuse application has at least two or more prompts.
{% endhint %}

### Prerequisite(s)

1. **All of your intended custom audio prompts, recorded in a compatible file format.** \
   See the [Prompt Table](https://docs.plumvoice.com/fuse/application-editor/audio-manager/prompt-table) in the Audio Manager to decide for which prompts you'd like to record an audio file. See [Audio Formats](https://docs.plumvoice.com/fuse/application-editor/audio-manager/audio-formats) for more information.
2. **A spreadsheet application.** \
   Examples include Microsoft Excel and Google Sheets. You will use this to view a `.csv` spreadsheet.
3. **A `.zip` application.** \
   Many current operating systems have built-in `.zip` utilities. A free alternative is 7-Zip. You should be familiar with how to create a `.zip` archive using your chosen application.
4. [**Review the docs on the Prompt Table**](https://docs.plumvoice.com/fuse/application-editor/audio-manager/prompt-table)**.** Terms and user interface elements discussed here are similarly covered in this documentation.

### Recommendation(s)

1. **Finish building your Fuse application first.** \
   Once finished, you will likely have a finalized list of prompts in the Prompt Table. This would allow you to bulk upload for all prompts in one effort – or as few efforts as possible.
2. **Give unique, identifiable names to each module you use.** \
   Your modules' names will be used in the filenames given to their audio prompts. A good module name will help make these filenames easier to identify at a glance.

## Step 1: Export a spreadsheet of prompt filenames

[Log in to Fuse](https://fuse.plumvoice.com/account/login). In the Application Manager, select the desired application. In the Application Editor, select the <img src="/files/vZ1wXdsVHRWFvXOjENsO" alt="" data-size="line"> **Audio Manager** tab. The Audio Manager will be displayed as shown in Figure 1.

<figure><img src="/files/zyvfP8edUTd6kUXmc8YN" alt=""><figcaption><p><em>Figure 1: Audio prompts in the Audio Manager.</em></p></figcaption></figure>

Select the tab for the desired language, then select <img src="/files/D1D4FyRJHAAXPQzwrrYW" alt="" data-size="line"> **Export CSV**. Save the `.csv` spreadsheet in a memorable location, and open it in your chosen spreadsheet application. The spreadsheet should contain a **filename** column and a **prompt** column as shown in Figure 2.

<figure><img src="/files/jRbkMCjrfa90TV8K47Pw" alt=""><figcaption><p><em>Figure 2: The exported list of audio prompt filenames.</em></p></figcaption></figure>

These filenames correspond to each prompt in your application. **Your audio file must use the same filename as its intended prompt.**

## Step 2: Rename your audio files

Read the spreadsheet to locate each prompt that will receive an audio file. Figure 3 provides an example of how the prompts listed in the Audio Manager and the spreadsheet compare.

<figure><img src="/files/jh3gSMpSt9AtnCrhVunN" alt=""><figcaption><p>Figure <em>3: Prompts in the Audio Manager compared with the exported .csv spreadsheet.</em><br><em>Select this image to zoom in.</em></p></figcaption></figure>

Confirm the prompt's filename, and rename the desired audio file to match it exactl&#x79;**\***. This allows the Audio Manager to identify which prompt should receive that audio file from your bulk upload.

{% hint style="info" %}
**\*Note:** The file type does not have to match, but it must be compatible with Fuse. \
See [Audio Formats](https://docs.plumvoice.com/fuse/application-editor/audio-manager/audio-formats) for more information.
{% endhint %}

## Step 3: Add your audio files to a ZIP archive

Add the renamed audio files to the same folder or directory, then add them to a `.zip` archive. Save the `.zip` archive in a memorable location.

## Step 4: Upload the ZIP archive

Select <img src="/files/tjy1LXWjkv9yHvG9bDUa" alt="" data-size="line"> **Upload Zip**. In the File Upload window, navigate to the folder or directory containing the `.zip` archive, select it, then select **Open**.

The `.zip` archive will be uploaded, and the Audio Manager will apply each renamed audio file within to the prompt with a matching filename. All other prompts will remain unchanged.

{% hint style="info" %}
**How do I know the upload(s) worked?**

Look for the following icons to distinguish them:

* **TTS**: Default prompt type; no audio file attached. Displays <img src="/files/rxnmmmnRxlgUulcpeJ9c" alt="" data-size="line"> **Upload** only.
* **Audio**: These prompts have an uploaded audio file attached. **Look for these:** they display the ![](/files/JbRfGBG48iks1RTkX0cR) **Play**, <img src="/files/1vVJ0AKi9yfPHrIdGD0J" alt="" data-size="line"> **Download**, ![](/files/dl057t70nQ4vfX31mdMv) **Upload**, and ![](/files/wSDNbfvf9Vw4RprIZP1A) **Delete** buttons.
  {% endhint %}

{% hint style="warning" %}
**Note:** Any uploaded audio files **will override** any text entered for text-to-speech.
{% endhint %}

## Step 5: Test the prompts

In the Prompt Table, review the list of audio prompts. Select the <img src="/files/JbRfGBG48iks1RTkX0cR" alt="" data-size="line"> **Play** button on each one, and listen to the entire playback to confirm that each prompt uses the correct audio file and that the audio plays as desired. Figure 4 provides an example.

<figure><img src="/files/9X19TR2xnO552PDGimcJ" alt=""><figcaption><p><em>Figure 4: Select the Play button for each prompt that has it.</em> <br><em>Listen to the playback to ensure that each prompt works as intended.</em></p></figcaption></figure>

Finally, create a deployment with the application and dial the number of your deployment to test it. During your test calls, select each option connected to your prompts and ensure that each audio prompt plays back as intended.

### Troubleshooting

If any audio prompts fail, open the application in the Application Editor, go to the Audio Manager, and check the following in order:

1. **Was an audio file uploaded to the correct prompt?** Carefully check the filenames you used for each audio file. They must be entered exactly as given in the `.cvs` spreadsheet, and each filename is linked to a specific prompt in your application.
2. **Is the audio file in a compatible format and file size?** Review the guidelines set in [Audio Formats](https://docs.plumvoice.com/fuse/application-editor/audio-manager/audio-formats) and verify that your audio files match them.
3. **Does a failing prompt play any audio at all when you select the Play button?** If not, try reuploading the desired audio file. File damage could also prevent playback.

## Conclusion

If no issues are found, you've successfully bulk uploaded audio prompts for your application.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.plumvoice.com/fuse/application-editor/audio-manager/bulk-uploading-audio-prompts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
