Feature Suggestion

We have examples of regular and ad hoc incoming emails .. both from internal and external sources where multiple team mailboxes (i.e. Enate connectors) are on the bcc line of the email. When this email comes into Enate a single ticket is created, for one connector which I believe is chosen alphabetically. This is down to how Enate processes the email and its visibility of the mailboxes in the bcc line. However, from a user perspective this is a degrading of service from when they used to operate directly from their mailbox e.g. Outlook and were standing independently. Here they would have received an email each and acted on it. Each team needs their own ticket created. In Enate the team that does not get a ticket have no knowledge of an email having arrived. The team that does get the ticket have no knowledge that other teams should also have had this ticket created for them. If they had, they could create linked tickets for other teams. When two or more mailboxes are on the To of an email it is recognised that they all need this email and a ticket is created for each. Can the email processing logic of bcc be looked at so that the independence of different connectors is recognised in Enate?

Current behaviour: When a client sends an email that creates a work item in Enate, the system automatically sends an acknowledgement email to confirm receipt. However, there is currently no option to automatically send a closing acknowledgement when the ticket has been completed. Expected behaviour: Provide the ability to configure an automatic closing acknowledgement email that is sent to the client when the work item or ticket is resolved. Impact: Sending a closing acknowledgement would help keep clients informed that their request has been completed, reduce follow-up emails requesting status updates, and provide a clear confirmation that the issue has been resolved.

There are several operational scenario where in we will need ability to search inside attachments for specific worlds. These attachments are usually PDF and Excels.

As a Super User of HRP in Poland, I would like to pass on the suggestion of local users that we would like to be able to choose whether we work on dark or light Enate mode. I wonder if such an idea has more supporters.

After disabling the trigger, the “Next Run” field still shows the value instead of clearing. This makes it unclear whether the trigger is truly stopped. The field should be cleared once the trigger is disabled to avoid confusion.

As a user, we would need an integration for emails going out of Enate to Microsoft Purview. As this is being used globally inside the company - Enate is not able to deliver this currently. Can you please help on generating any such feature integration to send out emails with Microsft Purview enabled

As a configurator, I should be able to view and use contact details extended properties within Email template fields section and in conditionality.

As a user, our company has enabled to have the capability to mark the emails with attachments with right category - so the documents are protected. However this is becoming a limitation with in Enate - as such these emails are not previewable for users Can we please request to check with Microsoft for any integrations which allows this via connectors and be made available in Enate

The current authentication mechanism used in Self Service is going to be soon retired. We need to replace it with the new Microsoft authentication to ensure continued login support.

When the ‘Hide Plus Address’ setting is enabled in exclusive mode, automatically generated reply emails—such as out‑of‑office responses, delivery failure notifications, and similar system‑generated emails—are currently creating new packets instead of attaching to the existing packet associated with the conversation. This breaks continuity and creates unnecessary fragmentation.