> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/knowledge-base/call-routing/does-the-voicemail-feature-automatically-transcribe-messages.md). # Does the voicemail feature automatically transcribe messages? Yes, voicemails are automatically attached to the alert in the form of an audio file and are transcribed. ## Voicemail transcription capabilities ### Automatic transcription When callers leave voicemails, ilert automatically: * **Records the audio**: Captures the complete voicemail message * **Transcribes the content**: Converts speech to text automatically * **Attaches both formats**: Provides both audio file and text transcription * **Includes in alerts**: Makes both formats available in the generated alert ### Transcription features The transcription service provides: * **High accuracy**: Reliable speech-to-text conversion * **Multiple languages**: Support for various languages and accents * **Real-time processing**: Transcriptions are available quickly * **Searchable text**: Text content can be searched and indexed ## Alert integration ### Voicemail alert content When a voicemail creates an alert, it includes: * **Audio file**: Original voicemail recording for playback * **Text transcription**: Searchable text version of the message * **Caller information**: Phone number and timestamp * **Metadata**: Duration, quality, and other call details ### Benefits of transcription Having both audio and text provides: * **Quick review**: Read transcriptions for faster message review * **Search capability**: Search through voicemail content * **Accessibility**: Text format for users who prefer reading * **Documentation**: Text can be copied into incident notes or reports * **Backup reference**: Text version if audio quality is poor --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ilert.com/knowledge-base/call-routing/does-the-voicemail-feature-automatically-transcribe-messages.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.