All ideas

Currently, the scope of the report is not taken into account when calculating the metrics, leading to multiple counts. Ex: conversation is moved from inbox A to B. It will increment the new workload by one (for B) and the closed workload by one (f...

The metric is confusing and does not fulfil the user's expectations. It is particularly wrong in the time breakdowns (heat map, time chart) Could also be solved by changing its definition (=> make sure it is not counted twice by tying it to a s...

Currently only the usage of public message template is used Allow to track the usage of private message template as well

Currently, you can define timezones on Workspace or shared mailbox level. This would be far easier if we could set timezones based on Teammate who all work within the same shared mailbox. Having to breakout by Workspace means you have to fragment ...

Typing "fee" in the search bar should return only or at least at the top, suggestions for "fee" and not more like "feedback". Should be the case for tags at least.

Customers can spend a lot of time putting together KB articles. Deletions can always happen by accident and right now we do not offer a method for easy recovery. It would be nice if customers had a grace period where they could reverse any deletio...

Front's chatbot does not recognize line breaks. This means that requests group into large blocks of text that can be difficult to decipher - and lead to errors. It also differs from how the customer intended to submit their request (since line bre...

Currently a date value that is imported assumes a time value (midnight?) and then converts that from my local time to UTC, so what is displayed in the field instead of say Jan 1/25 is Dec. 31/24 4PM. The ask is to add a date-only format option to ...