Today we can only insert message template variables in the body. The goal here is to be able to use variables in the subject field (optional field) of message templates.
Prevent users from sending messages with shared channels
Admins may want teammates using an inbox to only send messages with their own individual channel. This could be because they want a consistent customer experience or in some cases to avoid sending an email to customer A from the customer_b@mycompa...
Add a new custom field type: Link. It is a clickable text with a URL. Customers using dynamic objects asked for it and it can also be used for other objects like contacts and accounts.
The ability to create message templates that are accessible across multiple workspaces, when it's not feasible for all who need access to also have access to the same workspace.
Please consider adding a native To-do function based on David Allen's Getting Things Done workflow. The integrations in Front do not allow for prioritizing today, and we resort to going to Asana or ToDoist directly, which is not convenient.
Different signature on reply emails than on initial email
Option (perhaps a setting or a rule) to have a different email signature on reply emails than on initial emails. This is available on other platforms. My signature is quite lengthy on purpose, but it doesn’t need to appear on every subsequent repl...
Custom message order so that the most recent email in a conversation thread is shown at the top
Ability to change the order in which new messages are displayed in a thread. Today, the oldest message is at the top, and the most recent is at the bottom.
New [Is out-of-office] Teammate property for Dynamic Variables
Have a new [Is out-of-office] Teammate property to use in Dynamic Variables, in addition to [Is available] which returns false whether the status is Busy or Out-of-office.