All ideas

Currently, when a shared inbox owner assigns a conversation from the team inbox to a teammate, the message is moved to the assignee and is auto-archived for the inbox owner (though they are still subscribed). Afew inbox owners prefer to have these...

Situation Description: Currently, AI translation for inbound and outbound messages requires users to manually trigger the translation. This adds extra steps and actions that slow down their workflow, especially for users handling conversations in ...

​It would be helpful to enable rules to be re-triggered by edited comments not just new comments, as users frequently update comments to include crucial information that may have been initially overlooked.

We're often using user-email-accounts for shared inboxes / channels. However, we cannot use the calendar function as a "shared calendar". A support of this would be much appreciated because it also happens that we are using Gmail for user inboxes ...

Ability to assign a discussion while composing one, instead of having to do it after sending it.

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

Many KB articles and conversations contain images and other file types with critical content. We'd like to have them used as important context for resolution and be added to the draft.

This would allow teams to prevent overlapping automation triggers and ensure that branching rules execute exclusively and efficiently, improving rule logic control and workflow accuracy, and maintaining feature parity with linear rules.