All ideas

Currently, when a macro uses an action that creates a new draft (like applying a message template or canned response), it generates a clean, blank message. It does not automatically include the previous conversation history, similar to how hitting...

Add recipient fields to message templates so they can be used repeatedly as well.

Some conversations don't need to be answered (newsletters, automations etc.). They are archived/resolved very fast and therefore skew analytics' metrics. Conversation stages offered a "no action needed" status, but are now deprecated. The "archive...

The Front integration of Grammarly does not support other languages. Add integrations with tools like "Language Tool" that support other languages

Suggestion to be able to forward an email as an attachment in another email

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

When moving a conversation to a new team inbox, it is currently unassigned, even if the assignee is part of that team inbox. This is not ideal in situations where either it just needs to be moved, but not reassigned to another person, or more spec...

Add the ability to turn on/off the new(ish) feature that automatically shares a draft with all participants. That way a user can decide if they want to have control over when a draft is ready to be shared.