All ideas

Also: notes without a conversation

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

Actions requests from the admin to improve the accuracy Guidance to write good tag description Suggest negative reinforcement for AI tagging (either raising it to the admin or training the AI) Let user flag good examples of conversations that shou...

A p4 integration or channel integration with Google Chat so I can communicate with non Front teammates from within Front itself.

3CX is a popular telephony solution, particularly in EMEA

Syncing our Front contacts with Dialpad would eliminate the need to update two systems. We could then focus on maintaining our Front contacts as our single source of truth. This will help our team focus on what matters most: interacting with our h...

We currently have all our IT staff listed as company admins to handle company rules, developer options, company tags, etc. However, I don't want to give them access for other resources like billing, financial info or company preferences. We need g...

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

Make sure admins can set up their instance properly, including teammate configuration, before sending out invitation notification.