All ideas

Currently, a user can customize the fields they see when creating a Jira ticket via the plugin. This allows them to select the fields that are appropriate for that project and ticket type. However, for large organizations, this requires every sing...

With popups to review old tags and old rules, Front should also have a function/feature asking to delete/review old/unused contacts.

From admin perspective I do not extend permissions to permanently delete emails to end users, since often they ask me to restore thing deleted in error or move to trash by spam filtering. All users have permission to delete/mark as spam, however, ...

Certain customers want to link to multiple systems from a single pattern. This feature would allow a user add more than one link to a context link / dynamic object.

When a CSR uses a template, there are often fill in details or instructions like "attach the receipt" that I have tried to include in the text in bold colors but even my best CSRs have shot off the email without removing my instructions during bus...

Be able to have reusable components (Eg headers and footers) that can be referenced within templates - so it's easy to maintain a constant look and feel and easy to make one change that will be reflected across all templates.

I want to be able to click one button to Archive/Unassign/Unsubscribe from a convo. We use SMS a lot and all out of the same threads. Getting these convos out of our "my inbox" is a multi-faceted headache. We made a rule to link together "archive"...

I just accidently removed a context link instead of opening it because I clicked slightly too quickly. Definitely human error but since there is A) no confirmation to remove and B) no way that I know of to manually re-add a context link, the one I...