# August 2020 ### New features * Ability to re-route alerts to escalation policies and on-call schedules * Suggested responders: when re-routing an alert, ilert now suggests you the best responder based on historic data ### New and updated integrations * [Autotask](/integrations/inbound-integrations/autotask.md) * [Zabbix](/integrations/inbound-integrations/zabbix/native.md) (updated): Starting Zabbix 4.4, ilert can be integrated as a media type into Zabbix. Zabbix 5.0.4+ includes ilert as a media type by default. See also Zabbix blog post: [Working with multiple on-call teams using Zabbix and ilert](https://blog.zabbix.com/working-with-multiple-on-call-teams-using-zabbix-and-ilert/11847/) * [Prometheus](/integrations/inbound-integrations/prometheus.md) (updated): improved readabiltiy of prometheus alerts ### Improvements * Alert source overview page now includes outbound connections * User profile: low priority notifications rules are entirely optional, i.e. a user can now chose to not receive any notification for low priority alerts --- # 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/2020/august-2020.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.