Restrict conversation actions for a specific inbox i.e. View-only inbox access
Today, teammates can be given different sets of conversation permissions (e.g. ability to send a reply) between different Workspaces. However, creating a dedicated Workspace just for this purpose can be over-the-top and have undesired side effects...
Separate KBs for different workspaces or teammate groups
We have several different departments using Front. Each department handles different things and may handle things differently than other departments. For instance, I lead the Contact Center WFM team and we have several procedures in place for how ...
We have clients who own multiple businesses. It would be very useful if a single Contact could be associated with multiple Accounts. This would allow our Contacts organization in Front to better match reality.
Limit who can add, edit and delete contacts and accounts. This could also include limitations on freely browsing through contact data in the contact manager, although, we cannot restrict the ability to view contact data entirely.
Would it be possible to add a feature for Snoozing? Ideally it would be great to automatically add the same date that you last snoozed an item to the list. For example, if I have a follow up call on a certain day, I like to snooze prior emails to ...
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.
Our workflow is that we: Press "Compose" The default email address is an email from a shared inbox. It’s configured here: Preferences / Personal / Preferences / Default channel We add participants Then the draft is in the shared inbox and we see t...