# October 2023 ### New features and improvemens * **Support hours** have been moved out of alert sources into their **own entity**, you can now share a support hour across multiple sources and use team ownerships to controll access * We have added a new **Mute notifications** feature in web and mobile app, responders can now mute their notifications for specified or customized time periods * The **AI assisted incident postmortems** feature has reached closed BETA, reach out if you are interested in using before its GA * We have introduced a feature that autmatically archives historical layers of large repeating on-call schedules, to keep performance steady no matter the use-case * Integration icon and logo generation has been reworked for web and mobile to improve performance of the UI * **Reworked SMS notifications** to allow for a better focus on alert summary content * Alerts in state ACCEPTED may now be accepted by responders that are not yet added to the responder list of the alert ### New and updated integrations * Auvik alert creation has been improved (new fields) * The Grafana inbound integration now supports custom priority mapping based on label values ### ChatOps * The Microsoft Teams bot now supports a new who is on call command (**@iLert oncall**) that can be customized for teams and channels using a Microsoft Teams alert source * The Microsoft Teams Activity Feed display information for the bot's cards has been improved ### Terraform * New alert action filter types have been added * Alert source templates (text form) are now available in Terraform * delayMin field for escalation policies * New alert source time based grouping options are now available in Terraform --- # 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/2023/october-2023.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.