Insights

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

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 the ability to exclude snoozed time from the Response Time Analytics. Ex: a customer emails us at 8am asking us to send an update at 2pm of the transit of their shipment. If I snooze the conversation until 2 my response time is 6 hours pl...

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

Exposing new API endpoints for extracting CSAT Scores would be very useful. For example, provide a `GET /analytics/csat` endpoint to list CSAT scores. Provide the response data in a structured way with the score, reviewer, reviewee (teammate), com...

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

When an inbound message is received from a customer, and the message requires internal collaboration on the backend, an admin wants to track how much time is spent on that specific internal task. Example: As tasks and discussions are assigned to t...