The VICIdial soundboard Audio Store requirement

Every play button on a VICIdial Soundboard points at an audio clip, and there is one hard requirement behind it: the clip has to live in the Audio Store. Miss this and the button looks completely fine, it just plays nothing when clicked, which is the single most common reason a freshly built soundboard fails for an Agent. The board configuration and the audio files are two separate things, and this requirement is what connects them.

The Audio Filename field and the Audio Store

The Audio Filename field is where you enter the name of the file you want a button to play, written without a file extension. That filename must be present in the Audio Store to work properly. The Audio Store is the system's library of uploaded audio, and the soundboard simply references a file by name; it does not hold the audio itself. So the chain is straightforward: upload the clip into the Audio Store first, then type its name, minus the extension, into the Audio Filename on the soundboard entry. The order matters, because the soundboard has nothing to point at until the file already exists in the store. If FILE is included in the Audio Display setting, that same filename can also be shown to the agent right on the button, which is handy for spotting mistakes.

This is separate from the Audio Name field, which is just a descriptive label for the agent. The filename is the technical pointer that finds the actual audio; the name is the friendly text that helps a person recognize the button. They serve completely different jobs, and only the filename has to match something in the store, so you can write whatever readable Audio Name you like without affecting whether the clip plays. For the full set of fields you fill in per entry, the agent screen configuration guide walks through the whole soundboard screen.

How a button finds its audio

flowchart TD
  A[Agent clicks a button] --> B[Read the Audio Filename]
  B --> C{File in the Audio Store}
  C -->|Yes| D[Audio plays for the customer]
  C -->|No| E[Nothing plays the button fails]
  E --> F[Upload the file then retry]

The diagram shows the lookup that happens on every click. The system takes the Audio Filename, looks for a matching file in the Audio Store, and only plays audio when it finds one. No match means a silent button.

Avoiding the silent-button trap

Three things trip people up most often: typos between the filename and the stored file, leaving the extension on in the Audio Filename field when it should be omitted, and forgetting to upload the clip into the store at all. Any one of them produces the same symptom, a button that does nothing, so when a button is silent these are the first places to look. Confirm each name matches the Audio Store entry exactly, character for character. If you also turn on FILE in the display settings, agents and admins alike can see the filename on the button itself, which makes mismatches obvious at a glance; see the soundboard Audio Display field for how that works. Since the board lives inside an Agent script, always do a test click in the agent screen before going live, so you catch a missing file in testing rather than on a real customer call.

If you would rather not manage audio uploads and filename matching by hand, a managed VICIdial handles the Audio Store for you. See VICIfast pricing to get a dialer that just works.