> 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/march-2024.md). # March 2024 ### New features and improvements * We have launched Call Flows aka **Call Routing 2.0** as closed BETA for selected customers, offering a completely new way to build and configure your call routing experience, reach out if you wish to join the BETA * **AI assisted schedule creation** is now in open BETA * We have added a new UI for Account owners and Admins to get information on the current plan, quota and usage of the account (find it via: Navigation -> Cog -> Usage and limits) * Public status pages now remind subscribers of their missing opt-in up to 1 week * Public status page subscriptions can now apply a filter to choose to subscribe to specific services only * We have added a new inbound integration: HaloITSM * We have added a new inbound integration: Kibana * We have reworked the Elastic Watcher integration --- # 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/march-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.