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.
Flag all rules and macros that break when deleting a resource (tag, teammate, etc.)
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.
Frontline users can see rule logic with view-only access
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. (read only access to rules)
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.
I have a few dynamic variables I use in multiple rules. Some are relatively complex to configure like "Support Team member is available (Boolean)" - made by fetching Support Teammate Group > Filter (Teammate.is_available == true) > TeammateL...
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...
Rule tester: test Autopilot on specific message / version of the conversation
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...