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.
For many third-party channels, messages and call logs tied to one contact thread in one long conversation, which can be messy for users. The ability to split these messages into new conversations will help to organize their communications better i...
[accuracy] Similar conversation based on a more specific entity (inquriy, ticket, order, shipment ...)
Situation: The current “similar conversation” feature in Front is based on semantic proximity. This approach can be inefficient, especially when users need to find conversations related to specific entities like a ticket number, order number, ship...
Some admins want to invite colleagues to Front to be able to view or comment on conversations, but don't want to purchase a full Front license for them. Could we introduce a new category of cheaper license that allows more users to have view-only ...
Give customer the choice between multiple 3rd party spell checkers
Currently Front supports spell checking using Grammarly. However, some customers would prefer to have the choice the use other spell checkers, like Microsoft spell checker, as there are cases where they can provide better suggestions.
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.
Merge conversations with mixed types (eg. email and Front forms)
Unfortunately, there isn't currently a way to merge conversations when one is started as a form submission, and the other was started via email.
The conversations have different "types" and are not compatible for merge, and we'd like to be able ...