All ideas

I wanted to share a usability concern regarding the layout of the Chat and Internal Comment boxes. Currently, the two fields are very similar in both appearance and placement, which increases the risk of accidentally sending internal comments to t...

The new tasking system is not easy to use - it takes multiple clicks to make a task. Allow auto creation via API or Front rules

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.

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

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 discussions are assigned to teammates o...

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

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.

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