# January 2022 ### New features * we have launched our Incident Communications 2.0 BETA, [reach out to us](broken://spaces/-M76ygPnS4HUcFSX8ulm/pages/-MA0haGzw_vocetU3uxE) to join during the testing phase * On-call schedules: we now allow you to create more complex recurring schedules with [schedule layers](/on-call-management-and-escalations/on-call-schedules/recurring-schedules.md#schedule-layers). * New alert view: as part of our new Incident Comms 2.0 feature, a brand new revamp of our Alert Detail View has been launched, including live updates for Alerts and Alert related information. * as part of our Incident Com 2 Feature, Stakeholder users may now use the web login (they were previously limitted to the Mobile App only) ### Improvements * the `GET /api/log-entries` [resource](broken://spaces/-M76ygPnS4HUcFSX8ulm/pages/-MG3FmfDt_1jh5_UR-f2#undefined) now supports `?include=vars` and `?filter-types=ALERT_UPDATES` parameters, as well as pagination for more advanced and detailed alert timeline access * Microsoft Teams Alert Actions have been rebuild to support a direct Teams query for enterprise customers with > 10k Teams. * the (Support) Live Chat has been made available to EU customers (see Account Settings --- # 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/2022/january-2022.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.