All ideas

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

Minimize room for error and noise when assigning or mentioning someone. Only teammates with access to the conversation's Workspace should be possible to select.

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

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.

We want to begin using the auto replies, but it only replies back to the actual sender. Not the email addresses within CC etc.

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.

As the title suggests, getting this information is helpful to display it in external systems, feed it into LLMs for account insights, and more.

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

Hello, I was testing the 'close conversation' functionality and it can be usefull although we would like to check if we can automate this. The idea is to close a conversation after we have send the CSAT email to the user.