# March 2026 {% hint style="success" %} **Please note** that the release notes usually receive updates in the second week of the following month (*e.g. March gets published in mid April*), hence this document is not yet showing all released features and improvements. {% endhint %} ### New features and improvements * We added support for **multiple routing keys per escalation policy and event**, enabling more flexible routing setups * We released new **API endpoints for escalation policies** to `/resolve` by routing key and to set `/level` to overwrite a specific escalation level, this also allows `ilagent` now to automatically sync policies based on Kafka or MQTT streams * We rebuilt the **Call flow Voicemail node** to support multilanguage transcriptions (this previously only supported english) * We enhanced the **Maintenance window API** with additional filters for services, sources, from, until, and state, these also enhance the UI options now * We launched a new **Clickhouse backend for alert-reports**, heavily reducing loading times, and added label filters for alert-reports * We expanded **ManagedBy** Terraform tracking and export to Call flows and Event flows * AI-SRE (beta): we retired the legacy AlertInvestigation and rewired **RcaPolicy to RootCauseInvestigation** for a cleaner root cause analysis experience * We added **self-service payment via invoice** as an additional payment option * We added custom **HTTP header** handling for more flexible webhook outbound integrations * The **mobile app** now supports bulk accept and resolve operations for alerts — long-press a list item to enter multi-select ### Integration updates * We have introduced a new **Google Chat alert source** to customize ChatOps alert creation * We have introduced a new **Pulsetic** inbound integration * We added **severity support** to the ServiceNow, PRTG, Prometheus, Autotask and Jira event converters * We added **event tags to ilert label conversion** in the Zabbix integration --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ilert.com/changelog/2026/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.