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

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.

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

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

Allow managers to understand how the volume of work in their team's backlog is fluctuating. Implementation: how many conversations were in each status (custom ticketing status or open/snoozed) at a certain point in time.This would replace the "ope...

Ability to filter in analytics by conversation custom field (similarly to tags)

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

Right now we have up to 10 different authors creating content. We would love the ability to report on details like number of articles created by author, status, creator/author and last updated across the KB. It's possible to view some of this info...

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