All ideas

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

When an inbound message is received from a customer, and the message requires internal collaboration on the backend, an admin wants to track how much time is spent on that specific internal task. Example: As tasks and discussions are assigned to t...

Not all employees have a full Front license. Allow these employees a way to access internal Front knowledge base, perhaps with an add-on license just for KB since they don't need nay other Front access.

Out-of-Office (OOO) messages are currently reopening tickets in shared inboxes and triggering SLA rules. This forces support teams to constantly revisit tickets, and adds unnecessary workload and frustration The system should offer a native rule a...

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

It would be great to have a way to "mark conversations as distinct" or "keep separate" so that the option to merge disappears at the bottom of the conversation (if it's appearing to being with). We've noticed use cases where we need to keep conver...

Choose whether a metric breakdown should be represented as a table or a diagram. In the case of a diagram, choose the type of diagram.

Be able to create a test suite of conversations and the desired branch that was taken for them in a Front rule. If I had this capability, I could ensure that any new changes to a branch by Autopilot answer rule did not break backward compatibility...