Ability to generate contact lists dynamically based on custom fields
Instead of having static contact lists, they should be dynamically updated based on contact lists. This will ensure that the right people are getting emailed every time without having to remember to manually update organizational changes. For exam...
Currently large spam boxes in Front are impossible to handle. Front has taken the view that users should not be allowed to mass-delete spam and must select each message (not ctrl-A) but for a spam box with 1000s of messages that isn't practical. T...
It would be great to be able to add team roles as a dynamic variable within teammate groups, so they can be referenced in account custom fields for rule-based automations. A use case would be if you had clients that were assigned to a specific tea...
Add custom fields for more resources: Company, Workspace Add more custom fields types: Tag List, ... This can unlock many scenarios that need a centralised record of constants: incident management with IMs, advanced rules scenarios etc.
Allow non-company admins to create and manage custom fields
Today, only a company admin has the ability to create, edit and delete custom fields. This can prevent trusted Workspace admins from setting up the Workflows they need autonomously. How could we allow more users to set up custom fields?
Allow owners of individual inboxes or their company admins to transfer ownership of those inboxes to another user
Currently, users have to reach out to support to request an individual inbox's ownership transfer to another user. They can easily delegate their individual inboxes to users, and I feel like it'd make sense to grant the ability to fully transfer o...
We have more than 100 domains added and for each domain different signature, and now we have to create new signature for each domain, if we could add custom field to each mailbox we could have only one signature which would dynamically get image
As an admin, I’d like to set Send & Snooze as the default reply option for my company. Informing teammates about the ability to change this takes training overhead and friction.
Ability for Front users to disable Oauth in Settings
Right now, users have to write into our Support team in order to disable Oauth login. It would be helpful and reduce bottleneck for users to be able to toggle this in settings, and for admins to be able to do it on their behalf.
It's confusing + bad UX for users to have to follow these specific instructions when copy + pasting DNS settings. Ideally, the "copy" option would be able to grab only the parts of the record that are needed. The current setup adds additional work...