# March 2025 ### New features and improvements * **Support hours** now support exceptions (absolute date-time ranges) and **holiday** calendar imports * The ROUTE\_CALL call flow node, now skips agent confirmation if the target is no responder but an external phone number; this helps with connecting your call flows to third-party call hotlines. Note: number targets are an enterprise plan feature * Alert report fetch times have been improved using a new approach to validating access permissions on large amount of entities * We have introduced 4 new templates for alert source customization: **alert key extraction** and **event type (3) condition matching** (for now these are only active on types: API and EMAIL2) * **ITL** now supports 2 **new regex functions** (this is helpful for less complex event payloads e.g. emails with subject and body text fields, to help extract specific information) * We continue to improve default templates for alert source content customization * We have introduced a new call option for the ROUTE\_CALL call flow node: "simultaneous calling", you may use this to call all targets at once, instead of escalating through them * Whatsapp notifications have been moved to a new infrastructure, making their delivery more stable (while still lying under the good will of Meta though ;) ) ### Integration updates * We have **reworked our email alert source** (EMAIL2) to enable the same features that our API based event integrations provide, you may now use AI similarity grouping, content templating and other features like the event explorer. Old (EMAIL) alert sources will keep working as usual and may be updated through the old UI, new email alert sources will no longer show the "Advanced settings" menu tab, instead you can use the general templating mechanism to customize behaviour. * New inbound integration [Dash0](/integrations/inbound-integrations/dash0.md) * New inbound integration [Apica](/integrations/inbound-integrations/apica.md) --- # 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/2025/march-2025.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.