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...
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.
This could help increase response rates on surveys by sending them only at times when people are more likely to respond. Ideally, we would like to keep the current Delay and be able to add additional criteria. For example, it would wait 24 hours a...
Create a real-time dashboard to showcase what's happening *now* in front so you can have a "captain of a ship" view of what's going on. Imagine a screen where you could see staffing, wait & response time, volume of requests, numbers of open/un...
Analytics based on info created after a segment is closed
At the moment, our Analytics paradigm is that you report based on context at event time (or events happening within the Analytics segment). After that segment is closed you cannot update that data anymore. For instance, you cannot add a tag and re...
Automatically remove CSAT Survey rule tags after a user defined amount of time
Merged
Currently customers don't have a way to automate the removal of tags used in CSAT rules that send survey templates in app. This causes issues when customers have a large amount of conversations that use a channel type that does not typically creat...
CSAT: Option to embed a survey link variable vs. CSAT 5 stars
This is helpful because many company email clients do not download images by default, therefore the 5 stars come through as alt text. Enabling an option to add a survey link will provide a better formatted option and more likely an end user might ...
Analytics - metric detail conversation count hard to understand
Context: Analytics is counting conversation segments When clicking to see the detail of a metric the number of conversation segment is displayed and the list of associated conversation is provided Problem: We can display 5 conversations for 6 segm...
Change aggregation so that:
if conversation A has two scores (5 and 3) and conversation B has one score (1)
then average is ((5 + 3) / 2) + 1) / 2 = 2.5
instead of (5 + 3 + 1) / 3 = 3