Advanced rule conditions and actions

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

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

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

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

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.

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

Currently selecting "Keep assignments when teammate is out of office or busy" is an all or nothing decision. Currently selecting this option changes all of the following when teammates are set to Out of office or Busy: New conversations can be a...

The current options for dealing with unwanted messages like OOO replies are limited to archiving/resolving the conversation or merely tagging the message. For shared inboxes with ticket statuses enabled, the "Archive conversation" action inappropr...

Being able to see triggered (but not yet run) rules inline with actions would be great so we can know (at a glance) if something may happen to a ticket, both for just general knowledge sake, but also debugging purposes. Even better if there was a ...

Disable field editing to keep single source of truth in CRM as native sync from Hubspot or Salesforce for example are only one way batches. So if a user edits a contact field this wont be reflected in hubspot and when the next batch syncs, their c...