All ideas

the default (and only) option is to have the list of conversations on the left and the preview on the right. Although you can change the size of the columns, this is not as useful as being able to have a full-width preview all the time without hid...

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...

If only a part of the company uses Front, the inbounds from "external" employees (technical, legal ...) will be considered no differently from the end customers' ones. As a result, all reply based metrics (and probably workflows) are off. We might...

Currently, the Live Dashboard allows to count the snoozed conversations only for non-ticketing inboxes. For ticketing inboxes, there's no way to distinguish waiting conversations that are snoozed or not.

Currently the Get Message endpoint for Front's Core API does not allow lookup on the external ID field. It would be nice if we allowed lookup on the external_id as a resource alias much like the GET Account endpoint.

In Gmail, the integration allows the sender to not only log the email in Hubspot with one click, but it also tracks activity of the recipient like when they've read it, when they've clicked into the email, and when they've responded . With this tr...

When chatting with a customer, have the ability to see their current geographic location. This is important for businesses who have to comply with export restrictions.

Currently, shared contacts are shared with everyone in the company rather than by workspace. I'd like to be able to separate out shared contacts to specific workspaces, rahter than to everyone, to avoid confusion and support our security team's le...

Ability to compose emails with right to left text.