> 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/2022/february-2022.md). # February 2022 ### New features * We have launched the [ilert developer platform](broken://spaces/-M76ygPnS4HUcFSX8ulm/pages/17TPrJkoTNVU5S2on2Ac), which enables you to create your own applications on top of ilert's uptime platform and share them with other ilert users. * [Incident Communications 2.0](https://github.com/iLert/docs/blob/master/changelog/broken-reference/README.md) is now in public BETA for all Premium users. * Support for WhatsApp as a notification channel ### Improvements * Event API: routingKey may now be used to re-assign alerts during ALERT events * Alerts API: escalationPolicy attribute is now included in the response payload * Services of teams can now be managed in the teams admin UI ### New and updated integrations * Our ServiceNow bidirectional integration now supports dynamic mapping of assignmentGroups and escalation policies (as well as re-assignment) --- # 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/2022/february-2022.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.