Browser-local target checker
Webex Contact Center Audio Prompt Checker
Webex Contact Center audio prompts are documented as WAV, mono, 8,000 Hz, 8-bit u-law; IVRReady identifies that encoding by WAV format ID 0x0007.
- Last verified 2026-08-28 · Webex Help — Manage audio files
IVRReady validates against documented file-format constraints. It is an independent third-party tool and does not verify contact-flow behavior, prompt wording, language, permissions, or subjective voice quality.
Prompt workspace
Add prompts to check against the Webex Contact Center profile.
Check Webex Contact Center prompts
Drop WAV files, folders, or ZIP packages
Quality checks
IVRReady QA preferences — these are not Amazon Connect requirements.
Off by default. Trimming modifies your audio, so enable it only when you intend to change the recordings.
Webex Contact Center audio requirements
Scope: Generic Webex Contact Center audio prompts. Numeric WAV format ID is authoritative in IVRReady’s validation.
| Requirement | Documented value |
|---|---|
| Container | WAV / RIFF |
| Vendor wording | 8-bit u-law |
| Encoding | G.711 μ-law (8-bit u-law) |
| WAV format ID | 0x0007 (IVRReady's numeric identity) |
| Sample size | 8-bit |
| Sample rate | 8,000 Hz |
| Channels | Mono |
| Maximum duration | No generic limit documented on the cited requirements page |
| Maximum file size | No generic limit documented on the cited requirements page |
Webex documents a separate 5 MB limit for personal agent greetings. IVRReady does not apply it to generic audio prompts.
What IVRReady checks
Structural inspection reads the actual RIFF/WAVE bytes and checks container, numeric codec identity, sample rate, channel count, and only the generic limits documented for this target.
What IVRReady can fix
Verified PCM, float, A-law, or μ-law source layouts can be downmixed, resampled, and encoded to canonical μ-law output using browser-local FFmpeg. Optional leading and trailing edge-silence trimming is an IVRReady preference, not a vendor requirement.
IVRReady QA warnings
The separate QA pass reports effectively silent audio, possible clipping, leading silence, and trailing silence. These are IVRReady signal-measurement policies—not platform requirements or speech-quality scores. Corrected output receives structural revalidation rather than second-pass audio QA.
What IVRReady does not verify
IVRReady does not verify contact-flow correctness, language, prompt wording, tenant permissions, upload authorization, vendor configuration, subjective voice quality, or vendor certification.
Common incompatible source audio
Common examples include 48 kHz stereo PCM WAV, 44.1 kHz PCM WAV, 16-bit PCM instead of μ-law, malformed RIFF/WAVE, and unsupported source encodings. IVRReady distinguishes files it can structurally recognize, QA-decode, automatically correct, and confirm as target-ready; those capabilities are not interchangeable.