Split count of "waiting" conversations between snoozed and not snoozed
Currently, the Live Dashboard allows to count the snoozed conversations only for non-ticketing inboxes. For ticketing inboxes, there's no way to distinguish waiting conversations that are snoozed or not.
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...
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 ...
Front needs comprehensive email deliverability monitoring to help teams maintain good sender reputation and ensure customer communications reach their intended recipients. Currently, there's no visibility into whether emails are being delivered, b...
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...
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...
Instead of "From 9 to 5 from Mon to Fri", be able to say "From 9 to 5 from Mon to Fri, except on Dec 25, Jan 1, etc". This allows to take plan for holidays, teammate PTOs, company events, etc.
Tables in Analytics report are limited to a certain number of rows, for example the details table in the CSAT report is limited to 500 rows. Although it may make sense to limit the number of rows to load in the app, it would be great if we could d...