All ideas

Unfortunately, there isn't currently a way to merge conversations when one is started as a form submission, and the other was started via email. The conversations have different "types" and are not compatible for merge, and we'd like to be able ...

Custom fields are currently limited to just 50. We would like to increase this to store additional customer data to trigger workflows and surface relevant context to our team

Currently in Outlook, I have the ability to highlight non-contiguous text, copy those items, and paste into an outside application.

A native importer for Confluence so that admins can directly import content from Confluence as opposed to using the CSV import or the API.

As other dates in conversation, you can click on it to switch from timestamp (May 30 9:29) to duration (6m) We want to be able to do the same for SLA timer.

Currently, choosing Gmail threading will thread messages according to Gmail's logic in addition to regular threading

At the moment, Front’s unread counter is only visible when the browser tab isn’t pinned or shrunk, which is a bit different from Gmail’s dedicated notification badge feature. I would like to see a feature like this in Front for easeier use of tabs.

In order to connect FRONT with AI agents, an MCP Server would make this incredibly more easy than handling all the APi tasks.

Many customers ask for the full conversation in an analytics export. This is not possible as conversations can be very long, and the infrastructure cannot handle it. However, we could think about adding conversation-level metrics in the Get conver...