Improve the Imported Conversations Experience for Rules
While Front rules engine isn't currently set up to solve for imported conversations, this is something that comes up a lot with customers. This impacts rules in various ways. This idea is to look into how we can improve this experience for custome...
Looking for the ability to select all inboxes when creating a view so that the view captures a single tag across all current inboxes and any future inboxes that I have in the future. Currently, I would have to scroll through and manually select al...
Availability status (Available, Out of Office, Do Not Disturb, etc) shown next to assignee name when a conversation is already assigned
When assigning to another Front user, their availability status is listed next to their name in the drop down assignment window. However, there is no availability status shown for the assignee once it has been assigned to them - a coloured circle ...
Template to rule (building workflows off each template)
When you create a template, ability to create a rule off this template. Today you have to copy some of the template body to create a rule but it would be great if you could: Create rule If this template is used Then do X
We are aware that we have conversation codes. But it would be nice and organized to have an internal ticketing system that queues the incoming emails and provides a ticket number to the customers and a portal our customers could access to track pr...
When calling the fetch rule API endpoint, you are returned with minimal information (name and actions). It would be more ideal if there was reusable information fields such as which inbox is being impacted (inbox ID) and which tags are being appli...
Currenly, we have rules to autoreply to emails. When we are on annual leave and our vacation reponser is set, it still sends the 'rules', so they get our usual autoreponser, in addition to the vacation responser.