All ideas

I have a Front Chat widget with a single chatbot installed over a couple of different web properties (support.example.com, dev.example.com, community.example.com, etc) - In my Chatbot Analytics dashboard, it would be helpful to filter and segregat...

Refresh the Smart QA setup flow to improve usability

Summary: I’d love to have a dedicated report or filter in Front that shows all conversations archived or closed by automation rules — including which specific rule and branch performed the action. Problem: Right now, the full events export only le...

We’d like the ability to programmatically close conversations using the Front API. Right now, the API allows updating a conversation’s status to archived, but there’s no way to mark it as closed. This creates a challenge for teams like ours who re...

Allow admins to configure audiences on individual articles based on user segments. Not just based on knowledge base but instead, based on the actual article or category itself. Ensure that AI autopilot or copilot replies reference the correct know...

Would be based on the open-archived status, and replace the old "archived" metrics

Currently the inbox filter looks at the inbox at activity time This is expected behaviour but can lead to issues with some metrics such as "new conversations". In this particular case, if the conversation did not start in the filtered inbox, it is...

Enhance the filtering functionality in the schedule so that the inbox filter and teammate filter are more integrated: ensure that when an inbox is filtered, only those teammates with access to that specific inbox are displayed, thereby reducing co...

Being able to delegate an inbox to teammates via mobile phone in case we don't have access to the desktop.