> 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/changelog/2025/may-2025-6.md). # June 2025 ### New features and improvements * We have released a **brand new version of the alert detail view**, focussing on real-time collaboration and opening the doors for near future AI powered features like our AI Investigator * Call flows now support an "**accept on answer**" feature for the "Create alert node" (this was in particular request from legacy call routing users that were looking for a similar behaviour in their new call flows) * Call flow **voicemails** now automatically attach a **transcription** shortly after the call to any opened alerts * We have launched a **new schedule detail view design** that also allows you to overlay public holidays of multiple countries in the timeline * We have launched a **new on-call reports design** * We have introduced an option for users to configure notifications for new alert chat messages ### Integration updates * New inbound integration **Alibaba CloudMonitor** --- # 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/changelog/2025/may-2025-6.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.