Rule management

When a rule is created, the end user should be given the option to apply this rule to conversations in the open state in the inbox if they meet the conditions.

When deleting a resource like a teammate, tag, or inbox, Front should flag all the rules and macros currently using that resource so that admin can update these workflows accordingly.

Add a "description" field to rules to explain what they do, why they were created, who is responsible for their maintenance, etc.

Ability to organise rules into folders so that they are easy to find.

Instead of using the arrows, or typing in the order number you want a rule to fall into, having the ability to drag and drop rules in different order could be a better experience for customers who have cascading rules.

This will help with transparency as to how/why messages are getting assigned to them or not. This could be managed with a view-only permission for custom roles.

Be able to create a test suite of conversations and the desired branch that was taken for them in a Front rule. If I had this capability, I could ensure that any new changes to a branch by Autopilot answer rule did not break backward compatibility...

When I put specific filters on the Rules I'm looking at – for example, Rule Contains, or Inboxes – these are not saved when I leave and return. That means if I create a large group of these as an admin doing some work, it's really cumbersome to co...

As a Front user setting up a branch by autopilot rule, I want the ability to test the rule on a specific message in the conversation. Otherwise, if I test on the conversation as a whole, the context may be different than what I hope to test. As is...