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

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

Some auto-created contacts have their name as "last name, first name" Front's dynamic variables will identify the name listed first as the contact's first name and won't take the comma into consideration when identifying the correct first/last nam...

Be able to extract and transform attachement content data to use in dynamic variables in workflows. For example: extract attachment info > use in API request to create order request in TMS

I have a use case where I match text patterns in a message body (like ORDER-{digits}) and want to convert all matches to markdown links ( `[ORDER-123](https://example.com/orders/ORDER-123)` ) Right now this is not supported - as there's no way to ...

It would be very helpful if there was a condition in rules that allowed you to trigger a rule based on what Front user performed the originating trigger/action. For example, we have an SLA set up but we have a tag that will exclude a message from ...

I think it would be beneficial for rule sets to support dropdown menu custom fields

We use custom ticket numbers for client-facing communication, and related billing, which we really appreciate for the clarity. However, these ticket numbers can't be used to create dynamic fields. This limits the functionality of the numbers.It wo...

Have a new [Is out-of-office] Teammate property to use in Dynamic Variables, in addition to [Is available] which returns false whether the status is Busy or Out-of-office.