All ideas

Currently when replying to an EML file that is opened in Front it will do the following for selecting the reply channel: Available private channel First available shared channel, sorted by alphabetical order Please update it to add the users...

Current audit log only covers classic rules, but does not cover changes to branching rules.

If only a part of the company uses Front, the inbounds from "external" employees (technical, legal ...) will be considered no differently from the end customers' ones. As a result, all reply based metrics (and probably workflows) are off. We might...

​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.

Ability to hide the reading pane or conversation view to help users better focus.

Since merging of Topics can't be undone, it would be good to be able to restrict who can do this through a permission setting.

If a teammate is invited without specifying a workspace to add the teammate to (generally via SCIM), Front will add them to the "default" workspace, which is the workspace with the lowest ID. This can lead to teammates being added to a workspace t...

Long threads get refreshed and can’t find the old chat and plan. Especially if it something that is more complex and that might take a while to actually execute the plan.

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