Currently, Front's custom fields only support single string values, which creates a significant limitation when managing conversations that need to reference multiple external identifiers. Our system frequently handles conversations that relate to...
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 ...
We have a team that prints out orders we recive from our customers and it would be very helpfull to add into fronts audit trail showing when something was actually printed to catch mistakes. This would be attachments or bodies of an email.
Use case 1 (general): To improve security, an admin can force users to set up 2FA the next time they log in, and block them from accessing Front until it has been completed. The admin would need to set up their own 2FA first as a prerequisite. Use...
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...
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...
Have the option to customize the vertical switcher. Some ideas are: show/hide workspaces in the vertical switcher and customize order in which they appear on the sidebar
Today we can only insert message template variables in the body. The goal here is to be able to use variables in the subject field (optional field) of message templates.