Rule actions

Problem Rule-triggered replies and forwards always use the default channel, which may be wrong when a conversation has moved across inboxes with different channels. Request Allow specifying which channel to use when a rule replies to or forwards a...

Problem Rules cannot snooze conversations, so automating timed follow-ups requires manual intervention. Request Add snooze as a rule action so conversations can be automatically snoozed for a specified duration based on rule conditions.

Problem Rules cannot merge related conversations automatically, so teams must manually identify and combine them. Request Add a rule action that merges conversations matching specified conditions.

Problem Front lacks automated tools to help teams identify phishing emails, especially as AI-generated phishing attempts become more sophisticated. Request Provide phishing detection capabilities such as rule actions triggered by first-contact ema...

Problem Conversations cannot be automatically closed based on workflow conditions, requiring manual closure for each conversation. Request Add a rule action to automatically close conversations when specific conditions are met (e.g., after a CSAT ...

Problem Rules can update conversation subject for internal visibility, but this doesn't change the message subject when replying. Request Add a rule action to update the message subject line when replying to a conversation. Context This allows rem...

Problem Currently, the Send to Slack rule action sends a default message format with no customization options. This limits the ability to tailor Slack notifications to specific workflows or provide relevant context. Request Enable customizing the ...

Problem Rules can only remove one tag at a time, requiring multiple rule actions to clear all tags from a conversation. Request Add a rule action to remove all tags from a conversation at once, without needing to specify individual tags.

Problem When forwarding messages between teams or routing to Slack, the full conversation context may not be necessary or relevant to the receiving team, creating information overload. Request Allow message content to be edited, filtered, or modif...

Problem There is no rule action to automatically classify messages as spam, limiting automated spam management capabilities. Request Add a "Send to Spam" action in the rules engine, so admins can automate spam handling based on rule conditions.