> 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/2023/march-2023.md). # March 2023 ### New features * We have launched a new feature for notification preferences: **live test notification** status * We have added additional states to our alert notification timeline events, that now allow you to (live) **track the status of outbound alert notifications** and see if they have been delivered to or (e.g. Whatsapp) read be the responder, they work seemlessly for all notification channels * We have launched an overhowl of our escalation policy list and detail views * We added additional details to delete dialogs across the platform * We have introduced the new ilert Free billing plan * The user list search has been improved * Alert email notifications links now come with an additional confirmation step ### New and updated integrations * New Checkly inbound integration * Optimized Appdynamics inbound 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/2023/march-2023.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.