> 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/can-voicemails-create-alerts-for-the-operations-center.md). # Can voicemails create alerts? Yes, voicemails can be configured to automatically generate alerts and notify the any designated teams, similar to standard alerts. ## Voicemail alert capabilities ### Automatic alert generation When callers leave voicemails, ilert can: * **Create alerts automatically**: Generate alerts from voicemail messages * **Notify designated teams**: Route voicemail alerts to specific teams or the Operations Center * **Include voicemail content**: Attach the voicemail audio and transcription to the alert * **Follow escalation policies**: Apply the same escalation rules as other alerts ### Configuration options You can configure voicemail alerts to: * **Route to specific teams**: Direct voicemails to the Operations Center or other teams * **Set priority levels**: Assign appropriate severity to voicemail alerts * **Include metadata**: Add caller information and timestamp to alerts * **Customize notifications**: Set up specific notification channels for voicemail alerts --- # 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/can-voicemails-create-alerts-for-the-operations-center.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.