Provide visibility on actions taken by admins, to help teams work cohesively together. View historical activity when resources have been created, edited or deleted Rules Contacts Channels Inboxes Roles Teammates Teammate Groups Company settings Fe...
Specify fields to receive in Application Webhook events
My team uses Application Webhooks to ingest data from Front. We generally only need to access certain fields in an event payload, with most of the data in the payload being discarded. To help save on our ingress bandwidth costs (and Front's egress...
Please consider adding a native To-do function based on David Allen's Getting Things Done workflow. The integrations in Front do not allow for prioritizing today, and we resort to going to Asana or ToDoist directly, which is not convenient.
Currently, the only tag types are Private tags (that only the individual can see) or Public tags (that everyone with access to the conversation can see). It would be a cool feature to have "Private public tags," which would be public tags that onl...
The ability to pin an email at the top of an inbox
The ability to pin an email at the top of an inbox, similar to how you can "pin" an @mention comment. We have an employee working around this and snoozing an important email for a couple of minutes, so it appears at the top of his inbox. This can ...
Select channel when replying or forwarding with rules
Ability to change the channel used when replying or forwarding with rules. This useful when a conversation moves around multiple inboxes with different channels.
keep actions in this inbox seperate for workspace level
Extend the current setting to "Keep actions in this inbox separate from other inboxes" to the workspace level to be able to have a live conversation between inboxes in a workspace but not affected by conversations in other workspaces - and keep re...
Front Chat - Support sites with Cross-Origin-Embedder-Policy (COEP) header
I want to embed Front Chat on my site, however I have a Cross-Origin-Embedder-Policy (COEP) header, which requires all embedded content provides a Cross-Origin-Resource-Policy (CORP) header.
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 ...