# April 2026 Feature Wave The April 2026 Feature Wave brings with it a number of changes and improvements to email configuration as well other enhancements. {% embed url="" %} You can check out an overview of these enhancements in this page, or alternatively jump to the feature-specific articles from the links below for a more in-depth view. ### April 2026 Feature Wave Updates * [Enabling Outbound Emails via Microsoft Graph API](/whats-new/april-2026-feature-wave/april-2026-feature-wave/enabling-outbound-emails-via-microsoft-graph-api.md) * [Changes to Outgoing Email Configuration - Routes & Connectors](/whats-new/april-2026-feature-wave/april-2026-feature-wave/changes-to-outgoing-email-configuration-routes-and-connectors.md) * [New AI Email Classification Performance Report](/whats-new/april-2026-feature-wave/april-2026-feature-wave/new-ai-email-classification-performance-report.md) * [Improvements to Login Options](/whats-new/april-2026-feature-wave/april-2026-feature-wave/improvements-to-login-options.md) * [Changes to System-Generated Email setup](/whats-new/april-2026-feature-wave/april-2026-feature-wave/changes-to-system-generated-email-setup.md) * [Email Routes Page - New Filters](/whats-new/april-2026-feature-wave/april-2026-feature-wave/change-email-routes-page-new-filters.md) * [New: Option to pause Due Date clock when in a Feedback Window](/whats-new/april-2026-feature-wave/april-2026-feature-wave/new-option-to-pause-due-date-clock-when-in-a-feedback-window.md) * [New: Times when in User Group now recorded](/whats-new/april-2026-feature-wave/april-2026-feature-wave/new-times-when-in-user-group-now-recorded.md) *** ### Enabling Outbound Emails via Microsoft Graph API We have added the ability to [send Outbound Emails from Enate via Microsoft Graph API](/whats-new/april-2026-feature-wave/april-2026-feature-wave/enabling-outbound-emails-via-microsoft-graph-api.md). This feature is designed for organizations that want to align their communication workflows directly with Microsoft’s preferred, high-security API protocols for improved security, compliance, and governance standards. Main advantages of using Microsoft Graph API: * **Sent Items folder of the sending mailbox on your Exchange/Microsoft 365 server**, giving you a proper server-side record of all outbound Enate correspondence. * **Modern authentication replaces legacy credentials.** Graph API uses OAuth 2.0 via an Azure AD app registration, rather than the username/password or app-password approach. * **Outbound mail flows through the full M365 stack.** Emails sent this way pass through Exchange Online transport rules, DLP policies, and message tracking logs just like any other mail from your organisation.
### Changes to Outgoing Email Configuration - Routes & Configuration A new option with the April Feature wave is the ability to [configure additional Outbound Routes (Aliases)](/whats-new/april-2026-feature-wave/april-2026-feature-wave/changes-to-outgoing-email-configuration-routes-and-connectors.md) for your outbound email connectors, for both normal and Graph API Connectors. Previously, only Inbound Email Connectors had the option for additional configurable Routes.
As part of this move to explicit outbound email addresses and configurable outbound Routes/Aliases, we are changing the way that the standard system outbound connector approach works. Previously, some email routing happened behind the scenes via the "System Default SMTP Gateway”. To give Builder users a greater visibility of outgoing email configuration, Enate is retiring the 'hidden' system default and replacing it with a fully visible, manageable connector called ‘**Outgoing Connector’**. This will be visible on the Connectors page in Builder and will be fully configurable. Additionally, the Outgoing Connector will be visible on the Email Routes page, where users will be able to see and interact with all the email routes that previously fell under the old ‘System Default SMTP Gateway’. Builder users will be able to add, delete and edit these outgoing routes. ### New AI Email Classification Performance Report We are introducing the new [**AI Email Classification Performance Report**](/whats-new/april-2026-feature-wave/april-2026-feature-wave/new-ai-email-classification-performance-report.md). The report displays information relating to EnateAI Email Classification, specifically showing how well this AI is performing in assessing and accurately classifying incoming emails which launch Tickets. You can use this information as input into deciding if any adjustments should be made to AI settings, e.g. confidence levels set for deciding on manual review.
### Improvement to User Login As part of the April 2026 Feature Wave, users will now be able to login with their **Email Address as well as their Username.** ### Changes to System-Generated Email setup We are [changing the way in which admin emails are sent out from Enate, (i.e. system-generated emails)](/whats-new/april-2026-feature-wave/april-2026-feature-wave/changes-to-system-generated-email-setup.md). As part of this, the ‘Unmonitored Email Address’ setting in the General Settings section of Builder will no longer be used and is being removed. \ \ A standard Enate email address of '**'** will now be used for all such system-generated emails for Admin activities, e.g. password change confirmations. ’Ticket Reject’ emails will also follow this same approach for their From email address. Standard Enate-defined Email Templates will also now be used for system-generated admin emails as part of this change. ### Email Routes Page - New Filters To help further with managing large volumes of Email Route configuration, we've introduced some [new dropdown filters to the Email Routes page](/whats-new/april-2026-feature-wave/april-2026-feature-wave/change-email-routes-page-new-filters.md). The three new dropdown filters reflect additional settings that can be defined for Email Routes: * Send Automated Emails - (yes/no/all) * Only create work in test mode - (yes/no/all) * Enabled - (yes/no/all)
### New: Option to pause Due Date clock when in a Feedback Window As part of the April 2026 Feature Wave we have added a new setting for Due Date configuration: ‘[**Add Resolved Time to Due Date**](/whats-new/april-2026-feature-wave/april-2026-feature-wave/new-option-to-pause-due-date-clock-when-in-a-feedback-window.md)’. This new setting gives the option to pause the clock for work items which have been Resolved but have not yet been fully set to Closed (because a Feedback Window has been configured).
If this setting is set to ON, the time that a Work Item spends waiting in the Feedback Window will not be added to the SLA clock's used time. Then, if the Work Item is reopened, the SLA clock will start up again with the amount of time that was left when it was paused still available to the team before the SLA would be breached (e.g. if the work item was resolved with 4 hours 57 mins still remaining on the SLA clock, it will start up again at ‘4 hours 57 mins still remaining on SLA clock’).
Work Items in this situation will present to Agent users with the remaining SLA time available showing in the 'Due' label. ### New: Times when in User Group now recorded As part of of this Feature Wave, we are improving the [recording of a user’s times spent in a given User Group](/whats-new/april-2026-feature-wave/april-2026-feature-wave/new-times-when-in-user-group-now-recorded.md). This ensures that reporting isn't just a reflection of which User Group a user is in *right now*, but a more accurate record showing also which Groups they *were* in, and when. This will help any report builders with more accurate information. Previously, when a User was moved from one group to another, the data of their time spent in the first group was not carried over, resulting in user utilization and capacity reporting becoming historically inaccurate. Now, by introducing effective dating, this historic data is not lost if a user is moved between User Groups: that capacity is always attributed to the correct team for the correct period. --- # 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.enate.net/whats-new/april-2026-feature-wave/april-2026-feature-wave.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.