Feature Suggestion

should able to identify if work item has attachment or not in grids without opening the work item.

As a work manager user I should be able to preset the contact tag for a known contact in Enate so that when a contact is added contact tag is preselected.

We should be able to: Make data fields mandatory based on action names and status changes. For example, if a user is putting a work item on wait, they should fill a data field mandatorily like "reason". Show/hide data fields based on action names and status changes. For example, the reason field should come up only when users change the status to wait and should be mandatory. Another example, only certain fields should be visible on an action such as Review or Approve so the user sees only what they are supposed to see.

As an agent, I want to have the option to “bulk update” the created contact details in the work manager.

We need Enate system emails (password resets, notifications, etc.) to be sent using Enate‑managed email infrastructure, rather than routing through our own email gateways. This will improve reliability, reduce configuration overhead on our side, and ensure system emails are consistently delivered without depending on our internal SMTP/M365 setup.

We need Enate to prevent users from typing any “From” address when sending emails. Instead, users should only be able to select from a predefined, validates list of addresses. This will help us stay secure, prevent misuse of email identities, and ensure compatibility with our M365/Graph policies.

Please add native support for sending emails through the Microsoft Graph API within the platform. This would allow teams to leverage modern, secure, Microsoft‑recommended methods for email delivery instead of relying solely on SMTP or built‑in email mechanisms.

We’re introducing a new report to provide visibility into AI-driven Ticket Categorization. The report will show: AI predicted category Confidence score Final category Manual changes (including who updated it) This will help measure AI accuracy, confidence trends, and user adoption. Applicable to Tickets only.

An Enate system should allow multiple SSO providers to be configured in the builder. Then, at login time, end users should only see the relevant SSO provider options for them instead of seeing all SSO options, which creates a lot of confusion.

This feature introduces effective start and end dates for user membership within a user group. The intent is to enable accurate historical utilization and capacity reporting by determining when a user belonged to a specific user group. Currently, user groups are primarily used for permission management but are also leveraged for utilization reporting. The absence of time-bound membership creates inaccuracies when users move between groups, as historical capacity and utilization data are retroactively reassigned.