All ideas

As an Admin, I want to create a View that includes inboxes from multiple different workspaces.

SLA rules work on "oldest unreplied message". This makes sense because that's how long the end customer has been waiting. But some use cases require it to work on "last unreplied message".

When moving a message to a new conversation, there is no base rule trigger to automate actions on the new conversation. This idea suggests adding a new item to rule triggers for when a conversation is created from a split.

If a teammate forgets to mark themselves OOO, then it will disrupt the team's workflows and assignment rules. Today, only a company admin or teammate with 'Teammate - Invite/Manage' permission can change another user's OOO status. By adding a new ...

When a Conversation or subset of teammates need management oversight, it would be nice to be able to automatically subscribe a Teammate to a Conversation with rules. Right now, notifications serve as partially good, but when the conversation is be...

If only a part of the company uses Front, the inbounds from "external" employees (technical, legal ...) will be considered no differently from the end customers' ones. As a result, all reply based metrics (and probably workflows) are off. We might...

Have the option to be notified/export audit logs. This can be via webhooks and/or a dedicated API endpoint. This is useful for: Monitor changes in workspace configuration on internal dashboards Add logs into SIEM platforms like Sentinel

If I click on the Send folder then go back to the Inbox, the inbox should not automatically select the newest email, it should remain on the last email that was selected in the Inbox