Audio library
One shared list of recordings for voicemail drops and IVR prompts.
The audio library is the workspace list of recordings that voicemail drops and IVR prompts point to. In the app, an owner or admin registers a clip by its web address and can preview it in the browser. An API upload route stores the file itself instead, checking its opening bytes against its declared type and capping it at 10 MB.
- ·Register a hosted clip by web address from the Audio tab
- ·Play and pause a preview on every row, in the browser
- ·Search the library by clip name
- ·API upload for MP3, WAV, OGG, MP4/M4A and AAC, up to 10 MB
- ·Uploads checked by their opening bytes, not just the declared type
- ·Every add, upload, rename and delete written to the audit log
- ·Not built yet: in-app upload, usage badges, bulk delete
Voice prompts scattered across drives and inboxes
Calling needs the same few recordings over and over: a greeting, a menu prompt, a voicemail message. When each file sits in a different shared drive or email thread, nobody is sure which take is current, and whoever exported a file last decides what callers hear. The audio library gives the workspace one named list of clips, with a record of who added each one, that voicemail drops and IVR prompts refer to by id.
- The same greeting saved under three file names
- No quick way to hear a prompt before it is used
- No record of who added or removed a recording
The detail.
Checked by content, not just by label
The upload route first requires an allowed audio type, then reads the file's opening bytes: ID3 or a frame-sync header for MP3, RIFF followed by WAVE for WAV, OggS for OGG, and an ftyp box or ADTS header for MP4 and AAC. A file whose bytes contradict its declared type is refused before anything is written to disk, and so is an empty file or one larger than 10 MB. The check applies to uploads only; a clip registered by web address is stored as that address and its contents are never inspected.
Where the audio actually lives
An uploaded file is written to a directory on the API server, chosen by the AUTOCLOZ_AUDIO_DIR environment variable, and its library row records the size, type, original file name and a SHA-256 hash of the contents. The hash is stored for reference; it is not used to block a duplicate. A clip registered by web address keeps only that address, so the file has to stay reachable there. Direct upload to object storage such as S3 is not built.
Specific to this feature.
Can I upload an audio file from the app?
+
Not from the Audio tab yet. The in-app form registers a clip by the web address where it is hosted. File upload exists as an API route that accepts MP3, WAV, OGG, MP4 or M4A, and AAC files up to 10 MB.
Does the library remove duplicate recordings?
+
No. An uploaded file has a SHA-256 hash of its contents stored with it, but the hash is not used to refuse or merge a duplicate, and a clip registered by web address has no hash unless one is supplied with it.
Which features read from the audio library?
+
Voicemail drops choose their recording from it, and IVR prompts and play-audio actions reference clips by id. AI voice agents do not use library clips.
Can an IVR menu play a clip registered by web address?
+
No. The IVR runtime serves audio to the carrier only from stored files, so a clip that exists only as an address is refused when the carrier requests it. Upload the file through the API for any prompt a live menu needs.
Who can add or delete clips?
+
Registering a clip in the app needs an owner or admin, and deleting one needs delete permission on the Call channel. Every change is written to the audit log, and the Audio tab can be hidden for a role.
The full story.
To add a clip in the app, open the Audio tab of the Call console and enter a display name of up to 160 characters, the web address where the file is hosted and, optionally, its length in seconds. The address must begin with http:// or https://. The clip then appears with its length shown in minutes and seconds, a play button, and a link to the source file. The list refreshes itself every minute, so a clip a colleague adds shows up without reloading the page.
Teams that would rather Autocloz hold the file can use the upload route, POST /voice/audio/upload. It accepts MP3, WAV, OGG, MP4 or M4A, and AAC files up to 10 MB, and it refuses an empty file, a type outside that list, or a file whose opening bytes contradict its declared type. Each refusal comes back with a plain-language cause and a suggested fix. A stored file can be streamed back by any signed-in member of the same workspace, and renamed by anyone with edit permission on the Call channel.
When a live IVR call reaches a prompt or a play-audio action, Autocloz gives the carrier a signed link instead of a public file address. The link expires after one hour and is bound to one workspace and one file, so it cannot be reused to fetch a different recording. That route only serves clips stored as uploaded files, which is why any recording an IVR menu depends on should be uploaded rather than registered by address.
Registering a clip in the app is limited to workspace owners and admins, and each add, upload, rename and delete is written to the audit log with the person who made it. Every library query is filtered to your own workspace, and an IVR prompt can never play a clip that belongs to another workspace. Deleting a clip also deletes any voicemail drop built on it. The library does not yet show where a clip is used and has no bulk delete, so check your voicemail drops and IVR menus before removing a recording.
Try it free.
No credit card. Every feature on this page included.