Insights

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

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

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

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

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

Value: Allow managers to understand how the volume of work in their team's backlog is fluctuating. Implementation: replace the "open at start" and "open at end" metric to: Allow custom statuses and status categories (open and waiting) Reflect accu...

I have some existing automations which run when a comment is added with "CSAT Received" type content. Trouble is, I can't tell when it's submitted by a human or AI CSAT. I'd love a new rule trigger - CSAT Score. So I can start running a rule when ...