Description:
The REST API returns prompt details for Text-to-Speech IVR menus, but when an IVR menu uses an uploaded or recorded audio file (Audio mode), the API only provides audio metadata and binary content links, with no readable text representation of the prompt. We request adding a readable text field or transcription property for Audio mode IVR prompts in the API response.

Current Problem:
In our environment, 270 of our 331 IVR menus use Audio prompts. Because the API does not expose the prompt script or description text for audio recordings, automated audits, documentation exports, and configuration review scripts cannot inspect what callers are being told without manually downloading and listening to each audio file.

Proposed Solution:
Expose a text field (such as prompt description, transcript, or admin label) on the IVR prompt object in the API response when prompt mode is Audio, allowing API consumers to read the menu's spoken content programmatically.

Business Impact:
Programmatic access to prompt text across our 300+ IVRs would allow automated compliance reviews, call flow mapping, and configuration auditing without requiring hundreds of manual audio file downloads.