Feature Suggestion

Timezone input fields in various modules, including Service Agent creation, Contact creation, and Context creation, currently require scrolling to select a specific timezone. Instead, they should be searchable for easier selection.

Can the Email subject be configured to include the Name of Entity automatically instead of having the use to add the Name of Entity manually?

When trigger external api flavoured action is triggered, there is no parameter in the received JSON body to identify if the action is from Test mode or Live mode. Due to this clients are not able to use the test mode feature.

As a user on work manager, I want to create a checklist with multiple bullet points so I can combine minor checks which do not need an individual status, into a single checkpoint. The checklist would also need hyperlinks for the user to click and open to the relevant page when carrying out the task.

As an user remembering connector name when we have hundreds of aliases linked to it is not a feasible option, so search logic to be enhanced to search both alias and connector

If we use a template for Bulk creation of tickets, we would want the tickets to send out the emails and then pause the ticket automatically on Waiting for More Information. This would pause the Due Dates on all such tickets and we will not have to pause each tickets manually.

On boarding teams with a large volume of cases due to be kicked off using triggers. It would be better to have these triggers built and ready to go and tested in test mode before setting the team live.

It would be great to be able to link/check the dependencies used by a process in builder to ease migration/maintenance. This would also reduce manual validation error.

It would be great to have the ability to check the references of data fields to custom cards. It allows us to manage/delete unused data fields easily.

As a user, I want to have the possibility to edit a period in a schedule once the case triggered is canceled so that I could correct the due dates and trigger the case manually once again. That is a way better user experience than uploading a duplicate period once again in the Enate schedule.