All ideas

When calling the fetch rule API endpoint, you are returned with minimal information (name and actions). It would be more ideal if there was reusable information fields such as which inbox is being impacted (inbox ID) and which tags are being appli...

Both: In app (could be in a conversation's details) And through the API (directly in the response, without having to request an export)

Emails in spam hide external images by default. Sadly, there is no button to block the sender and move the email to spam without first opening it, which loads all of the images per the user's preferences. Adding new buttons to the context menu wou...

It'd be great if we could add a blank field as a variable for the user to fill in, instead of a pre-generated field. This is something Yesware and Zendesk have

Twitter is pretty much a redundant platform and these default fields for a Contact are unnecessary clutter for the vast majority of Contacts.

Tracking the total number of message of a conversation

Would allow teams to use Microsoft Bookings within Front.

Ply.io is incredibly powerful and would supercharge Front! Users will be able to automate workflows and significantly reduce manual work and app switching and copy pasting. They could set up buttons, triggers, and actions to automatically create t...

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