Feature Suggestion

Notifications sent to group email or users that have builder access, when any email connectors go down "disabled" automatically by the system for whatever reason. No notification if a user has disabled them manually.

I would like to have a multifactor authentication in place when login to Enate Production environment in order to avoid unauthorized users to access the production environment besides having the proper link and credentials. This provides an additional layer of security that ensures no authorized user can access the app.

I’d like to request the introduction of gamification elements in the Enate platform to improve engagement among operations users. Features like achievement pop-ups badges, can help boost motivation, recognize performance, and encourage consistent usage. (e.g., • 🏅 “Well done! You’ve successfully resolved 100 service requests!” • 🎉Congratulations! You’ve logged 100 productive hours on Enate!” • 📈 “Achievement unlocked: Maintained SLA for 30 consecutive days!”) Similar strategies are widely adopted by platforms like Salesforce and Microsoft Teams to drive user satisfaction and productivity. Please check the feasibility of implementing such features and let us know if a pilot can be considered.

I’d like to propose an enhancement related to how alert notifications for critical events are currently handled within the product. Currently, such alerts (e.g., failures, errors, or other critical events) are visible only within the product, requiring users to log in to view them. This setup limits real-time visibility and may delay timely action, especially if the responsible stakeholders are not actively monitoring the system. Request: Please check the feasibility of implementing a monitoring and alerting mechanism that can send real-time notifications (e.g., via email) to specific stakeholders. This will ensure the right people are informed promptly and can take immediate action when required. Happy to share more details or specific scenarios if needed.

Defects are recorded in detail including fields not currently available in Defects card such as RCA, Who made the error, Who acted on it, Custom time stamps, etc. Extension properties would allow to record defects more comprehensively and get a better reporting.

“Using PMingLiU for a Chinese company name is important, particularly when dealing with Traditional Chinese characters. We have had cases in the past where the font used has changed the Chinese name to an incorrect character. When the client tried to incorporated the BVI company under HK Registry, the application got rejected” Currently in Outlook they can use "PMingLiu" When using Enate, we do not have this option and this can cause risks especially because within the rolled out teams they are dealing with Chinese clients and names and require to have the accurate font.

Cuurently when approving: To confirm you approval, please hit submit. Feel free to add any comments when decline: To confirm declining this request, please selcet a reson and hit submit. Feel free to add any comments Expected: or if it can be customisable as per company needs when approving: Please provide justification for approval and raise any concerns, if applicable. when decline: Please provide justification for rejection and advise the next course of action for appeal.

As a user, I would like to manually creating a ticket directly from the Create Work Item directly on the search bar (home screen) so that it is easier for me to create a ticket instead only creating on the Contact page

As a user i can use my own font and size on my email when i am drafting it completely, however when I use a template and make minor changes in the template - my font and size should be defaulted to the same as the template I am using.

We require the ability to be able to easily select/tick/tag emails which we require to be passed to our DMS system automatically at the end of a request (i.e. on Hard Close of work item). Currently email simply treats all emails the same, and there is no way to differentiate between ones which are of enough significance to warrant longer term storage in our Document Management System. Give there are hundreds of thousands of emails passing through the system it would be hugely beneficial to be able to select which ones are critical to the business. right now we have to store all emails as there is no ability to highlight the key ones. The ability to mark the email a critical should be possible when reading the email and also when in the process of sending an email. This data then must be available via Enate APIs for email data so that it can be utilised within automations.