All ideas

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

Our team uses branching rules to route conversations to the correct workflows, but once messages enter a branch, there is no option to distribute workload evenly. This creates uneven assignment, unassigned emails, and extra manual queue management...

It's hard to have a overview on low CSAT scores in the Customer Satisfaction report - especially in the account table. This would allow to quickly get a sense for customer health without digging in each account individually

The "Customer satisfaction details" table only contains details on traditional CSAT. This provides only a fraction of the knowledge about accounts

I'd like an endpoint to fetch a conversation via API using the Ticket ID. Use case is that we want to give information about a ticket to our customers and the people who help our customers in Discord. They know their inquiry by the Ticket ID. Thus...

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

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

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