All ideas

Some conversations don't need to be answered (newsletters, automations etc.). They are archived/resolved very fast and therefore skew analytics' metrics. Conversation stages offered a "no action needed" status, but are now deprecated. The "archive...

Allow certain apps to be authorised at a workspace rather company wide level. For multi-department or multi-org companies using Front, are scenarios in which different teams use different instances or workspaces for the same application. E.g. Jira

​It would be helpful to enable rules to be re-triggered by edited comments not just new comments, as users frequently update comments to include crucial information that may have been initially overlooked.

It would be great if a teammate could assign a Due Date for when a reply needs to go out for a specific conversation. We could tie in the Due Date with existing SLA rules, or issues notifications if the Due Date passes without a response from the ...

Today, to start a discussion with a group of people, you need to type out each of their names to add them as participants. This can be cumbersome when the intention is to start a discussion with a large group of people. A possible solution custome...

Ability to preview attachments in an email without downloading.

Add recipient fields to message templates so they can be used repeatedly as well.

It would be great if we could add National Holiday closures as part of our company business hours.

We’d like the ability to programmatically close conversations using the Front API. Right now, the API allows updating a conversation’s status to archived, but there’s no way to mark it as closed. This creates a challenge for teams like ours who re...