My votes: Smart rules

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.

Rule data sets are currently manually maintained or limited to 500 rows for a CSV import. API access to manage this would give an avenue to maintain this in a non manual way and reduces chances of errors occurring

When a request comes in from a known content it would be nice to extract the notes from a contact and paste them into the conversation as a comment so all context stored in a Contact is immediately viewable by the agent. It would save time clickin...

It would be nice to send a task to a client and have the dates due already populated using a variable within an email template. For example, "Please complete this by {{date.2 calendardays}}"