Advanced rule conditions and actions

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...

Rep#1 is OOO, and the thread goes to Rep#2. But then Rep#2 is OOO, it would be ideal if the thread was then assigned to Rep#1 instead of Rep#3 and so on. Our team works 4/10s, so this is especially difficult because each rep is OOO at least 1 day ...

Ability to change the channel used when replying or forwarding with rules. This useful when a conversation moves around multiple inboxes with different channels. This applies to the CSAT rule template too.

The existing time criteria all exist as conditions to rules rather than triggers. For an overnight coverage use case it would be extremely helpful to have a time-based trigger be capable of taking action on a conversation. "When the clock strikes ...

We want to begin using the auto replies, but it only replies back to the actual sender. Not the email addresses within CC etc.

Right now, we're limited to only extracting a single item from an email, which makes it challenging when there might be a list of items that we'd like to extract in an unstructured way and pass that list into another system downstream. So, support...

Use the "reply-to" field for auto replies instead of the "from:" field.

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...

Extend PDF support in Workflows so the “Branch by Autopilot Answer” node can evaluate data extracted from PDF attachments and route accordingly. The primary use case is customers needing to branch workflow logic based on information contained in a...

Our company uses two resolved statuses: Resolved and No Action. When creating a ‘Requires Tag’ rule in Front, we’d like the rule to exclude conversations that have been resolved/archived with the No Action status.