Feature Suggestion

Importance of This Feature: The ability to restrict email communication to specific domains is vital for our organization. There are several reasons for this request: Data Security: Allowing emails to be sent to public domains such as Yahoo, Gmail, and Zoho etc. (full list of domains can be provided by our IT team) increases the risk of client data leakage. By implementing domain restrictions, we can safeguard sensitive information and reduce the likelihood of unintentional breaches. Client Expectations: Some of our clients, have explicitly requested the implementation of certain domain restrictions (list of domain restrictions is unique to each client). They expect us to take proactive measures in protecting their data, and this feature would demonstrate our commitment to their security needs. Compliance and Trust: Implementing such restrictions aligns with best practices in data privacy and security. It would not only enhance our compliance posture but also build greater trust with our clients, who are increasingly concerned about data integrity and confidentiality. Implementation Requirements: We propose that Enate implements these restrictions at the mailbox level within Enate.

We are very excited to share that, as part of feature waves, we are refreshing the Work Manager user experience to improve the look and feel of the website while keeping existing capabilities intact. This new user experience will be released in stages through an alpha/beta program. A select few of you are invited to participate in this program to help shape the new version of Work Manager. We will continue to share updates here, so please stay tuned.

Hi, to select same process type we need to go through filters and it is an extra click. Can this be moved to the select process screen while cloning

1.) Enable users to bulk categorise from the main dashboard inbox views where you can currently reassign or unassign multiple tickets at once a. To then subsequently resolve & add a note if required b. Or the ability to bulk reject or bulk reject as spam & add a note if required It might be a good idea to have this as a user access setting in builder user management, as some teams may only want team leaders/super users doing this. Use cases: 1.) For dealing teams, they may receive 200 to 400 end of month statements individually at the same time. It is very time consuming to categorise all tickets and resolve if they were just for information purposes for example 2.) If you get spammed or you end up with 1000s of tickets due to a ping pong match with auto responses… it would be handy for users to be able to bulk reject instead of the developers/BAs having to find/terminate the tickets in the Monitor

Currently, the Locations, Departments, Extension Properties API are not public. Need these APIs to be available in swagger with the product support as the Locations, Departments and Extension Properties API Data output can be utilised in the subsequent APIs of Contract, Users etc. To start with GET and maybe POST can be added later

As a user, I would not want any global contacts to be suggested when drafting emails. only suggestions should come from contacts which has been tagged under that entity only. This will help me as a user to make sure, i am sending emails only to right contacts and also restrict the contacts which I do not want to see and additionally prevent a huge data breach. If i still want to go ahead and send emails to global contacts - I can manually type the full address or copy paste it from outside - so not a blocker. This feature is needed as an option in system setting, so we can enable it if other Enate clients do not intend to have this feature

As a user, I would like the ability to copy or drag emails from the "To" field to the "CC" field and vice versa. Copy button copies entire entry and not just one address.

As an end user, I would like a contact to be made visible based on customer they are part of - when I type to search the contact This control is needed at email section, when drafting the emails on any packet with a warning in case they still want to send to emails not under the customer contact

If emails are sent out by the service agent requesting for additional information/clarifications to the requestor and if a response is not received for the same, an option to send out any number of reminders automatically is required. On not receiving any response, the ticket should close automatically after a certain number of days. reminders data should be exported to WH so we can build a report on reminder volume in WM.

As a user, I would like to be able to figure out if and when the changes were made on Custom Card. What are the changes done? Who made the changes? When was it done? Last 2 are mostly available