My ideas

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

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

Add a workspace parameter in the API endpoint

When I put specific filters on the Rules I'm looking at – for example, Rule Contains, or Inboxes – these are not saved when I leave and return. That means if I create a large group of these as an admin doing some work, it's really cumbersome to co...

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

Currently, when a macro uses an action that creates a new draft (like applying a message template or canned response), it generates a clean, blank message. It does not automatically include the previous conversation history, similar to how hitting...