All ideas

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

Allow admins to" FIELD EDITING: choose who can edit fields on a conversation, teammate, account, contact. If disabled, user cannot edit the field. FIELD DISPLAY: choose which fields apply on objects (contacts, accounts, convo, app objects) bas...

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

Must be able to have an easy way to notify the team of changes.

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