> 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/2024/december-2024.md). # December 2024 ### New features and improvements * ilert now supports **Coverage Requests**, starting with the mobile app, you may now request a shift override from one of your on-call buddies, with the tap on a button your colleagues are notified immediately and can choose to accept or decline the request while you will receive another notificatin depending on their decision. * We have optimized the **call flow builder experience**, lots of internal and external feedback has been used to shape an even better UX when building flows, especially larger flows * Call flow "Route call" nodes now support a dedicated choice for **agent call timeout**s and the default has been reduced from 60 to 45 seconds (Note: the legacy call routing solution has always used 60 seconds) * There is a new call flow node **Agentic Concierge**, it has moved into closed BETA. It replaces your IVR menus and more; use a real-time AI agent to communicate with your caller to identify the callers intent and gather additional information, use the identified intent to decide your branch flow. Let us know if you would like to try it out, before it moves into GA. * We launched **ilert wrapped 2024, hope you had a great year with us** :) --- # 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/2024/december-2024.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.