> 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/2020/september-2020.md). # September 2020 ### New features * Alert Actions * Support for outbound connections in Call Routing Numbers * Support Hours for Call Routing Numbers ### New and updated integrations * [Email Outbound Integration](/integrations/outbound-integrations/email.md) * [Kentix AlarmManager](/integrations/inbound-integrations/kentix-am.md) * Datadog Outbound Integration now supports regions * Prometheus alert detail formatting has been updated * Slack channels (connections) can now be managed in ilert directly ### Improvements * Ability to select alert events in outbound integrations. Example: trigger webhooks for alert creation and resolution events, but ignore remaining alert event types. * Every call routing number is now referenced to an alert source, helping you connect incoming calls to e.g. Slack. You can now also manage support hours for your call routing number. * Optimized bulk alert actions like accept and resolve * Uptime monitor TCP and UDP modes now support first packet and expected packet * Further improvements on our API to optimize response time and delivery for our mobile app * New API endpoint /numbers --- # 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/2020/september-2020.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.