All ideas

Same as auto-draft with AI for emails, but for chat and SMS or others TBD

The ability to tag drafts would be useful so that the user is allowed to "sit" on an email for a while, and not forget to tag it after sending. Currently, the only way to apply a tag to a draft is to schedule it for sending later, and then cancel ...

To make it easier to identify phishing attempts, it'd be useful to configure Front to always display the email address. This makes it less likely a user is caught in a phishing scam.

I'd like an endpoint to fetch a conversation via API using the Ticket ID. Use case is that we want to give information about a ticket to our customers and the people who help our customers in Discord. They know their inquiry by the Ticket ID. Thus...

Be able to specify the language of the Summary.

Allow managers to understand how the volume of work in their team's backlog is fluctuating. Implementation: how many conversations were in each status (custom ticketing status or open/snoozed) at a certain point in time.This would replace the "ope...

Front being an all in one platform without having to subscribe to a partner solution for calls

Syncing our Front contacts with Dialpad would eliminate the need to update two systems. We could then focus on maintaining our Front contacts as our single source of truth. This will help our team focus on what matters most: interacting with our h...

Templating is currently limited to basic text formatting. The ability to use custom HTML templates would open up the possibility of using Front to send emails with richer branding and formatting (especially in bulk/sequence emails), like many othe...

Many customers ask for the full conversation in an analytics export. This is not possible as conversations can be very long, and the infrastructure cannot handle it. However, we could think about adding conversation-level metrics in the Get conver...