All ideas

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

Rules have the option to be enabled or disabled. having this Feature in Macros, allows me to start building exactly how I need it. Save, and come back to finish up the macro. Or test variations of the same macro to see which gives us best results.

Stop auto-archiving personal copies for teammates who are Participants when the conversation is moved from an individual's inbox to a shared inbox via the 'move to inbox' rule.

Ability to preview automatically collected information (via rules or AI extraction) before a macro submits data to a third-party system via a connector. This preview step would allow users to correct any inaccurate or unexpected information prior ...

Currently when replying to an EML file that is opened in Front it will do the following for selecting the reply channel: Available private channel First available shared channel, sorted by alphabetical order Please update it to add the users...

Update the "Unsubscribe on unassign" preference to include additonal options such as being unassigned due to being OOO or unassigned via a rule. Some companies wish to leverage the unsubscribe feature for teammates when they're away for vacation o...

Ability to snooze a conversation from rules.

Add a button that schedules a meeting with everyone that is on the email. It would be on the three-dot dropdown menu along with "Forward" and "Forward as a new conversation" - something like "Schedule meeting" - click that would pop open the calen...

Hello, I was testing the 'close conversation' functionality and it can be usefull although we would like to check if we can automate this. The idea is to close a conversation after we have send the CSAT email to the user.

Please consider adding a trigger for "being notified" (especially triggered by another rule). This would be incredibly powerful for daisy-chaining workflows. e.g., trigger rule when I have been notified by another rule. Use case: when an email is ...