Prevent users from sending messages with shared channels
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...
Audit which teammates aren't using their inbox access
Some company admins want to keep shared inbox access controls to the minimum necessary. A teammate may have been granted access but rarely views conversations in the inbox, which means their access can be revoked. How can we help company admins to...
Allow admins to design shared signatures where the image is individualised to the teammate. The image may be personal like a headshot or signature, or could be dependent on the team they belong to. This could be achieved through a new "image type"...
Allow contact data clean-up to be activated independently of auto-trash feature
Our current data retention policy feature allows conversations to be automatically hard-deleted after a period of time, and then associated contact data is cleaned up when all related conversation data has been deleted. This improvement would allo...
Does Front have a plan to integrate an automatic QA or review system such that reviews can be posted on Fronts platform only? Workflow idea: Front creates different access levels for Conversation reviewers Those reviewers are the only ones authori...
Define whether a shared channel can be used for outbound messages
In some cases, teammates should never reply to or compose message from a particular shared channel. To ensure this happens, the admin can set the channel settings such that it cannot be used for outbound messages.
An admin can view which teammate Groups a given teammate belongs to, but it can only be edited from the teammate Groups. This means that I want to add a user to multiple teammate Groups I must navigate to each one.