All ideas

We use the normal tags feature, and a custom tag feature where we tag the customer name. These data are required to resolve a ticket. Annoyingly, the "Tagging required" dialog box supports autofill, but it doesn't default to selecting any field in...

Having the articles from the KB be available to be sent via email (the same as email templates) is something that I think is really great. We have a company agreement that we don't actually send emails internally, we use Discussions within Front f...

Allow users to see whether a conversation has been marked as phishing when fetching it via the API

We would be interested in having the option to have individual sorting orders for the different status tabs of an inbox, for example, being able to sort the assigned tickets oldest-to-newest, but having the archive status be simultaneously sorting...

As a support agent or a support manager, I need to know how fresh is the data I'm looking at, so that I can trust its value.

Currently today, we only support comments and direct messages in fb messenger. However, messages originating as Facebook messenger/lead ads are not syncing in Front. This would be helpful to capture more inbound communications/opportunities.

Allow to customise the CSAT stars , in survey and in signature Problems: Stars are not prominent enough for some customers Allow to make them stand out more. Some customer also want control over the starts look and feel

Ticket Statuses currently cannot be used as conditions or actions in Company Rules - they can only be used in Workspace Rules. This means the rules need to be duplicated for every workspace to apply to all inboxes. This is a time-consuming, manual...

As mentioned in the How to set up a Twilio SMS inbox in Front help center article, outbound Twilio SMS messages send from a source other than Front (like a third-party integration, or the Twilio API) will only sync to Front after an inbound reply ...

Merging conversations is my favorite Front feature and we use it extensively. We've recently come up against the 100 message limit (15 people on an email chain and 4 support engineers can hit 100 messages VERY quickly). 100 Message merge limit has...