All ideas

(For internal knowledge base use case) - Allow us to update processes ahead of time and launch when ready

Only of tag from the list selected in the rule can be applied. This would be an option similar to required tagging rule (see attached file) The closed tag is the one to be applied (context shared with Robert live).

Remove '{{ }}' function from the composer so it can be used in the email body

We are a large organization where we have multiple teams working in parallel with multiple stakeholders, there are times when two individuals from two different teams have to be responsible and responding on the same ticket. Understand there is th...

We have more than 100 domains added and for each domain different signature, and now we have to create new signature for each domain, if we could add custom field to each mailbox we could have only one signature which would dynamically get image

When creating a view under analytics you have the ability to send yourself automated reports via email. When looking at the "tags" report you have the option to select "all tags" or "filtered tags". Currently the emailed reports always function as...

Situation: when I want to create an AI tagging rule for multiple inboxes, all using the same tag (e.g., VIP), I have to train the AI, by reviewing message samples, separately for each rule, even though it's the same tag. Request: Streamline the pr...

Admins can select a subset of teammates and update certain settings in bulk. Users are still free to update the preference after the bulk update.

It would be beneficial if Front could do a better job of keeping the most recently used emojis listed at the beginning of the emoji selection box. This would save users time and effort, as they wouldn't have to scroll through a long list of emojis...

List coversations endpoint is ordered by that field, but the field is not exposed