All ideas

Sometimes having the ability to override an SLA timer is required from various actions such as: Internal customer emails OOO automated emails trigger a SLA reply but no action is needed Conversations requiring no actions During initial o...

We need the possibility to test all rules not only some to make sure it is working as expected.

My team spotted a couple of cases where the subject of a message did not align with the conversation subject; it turns out someone on the team manually edited the conversation subject. To make cases like this clearer, it would be useful to have a ...

Be able to specify the language of the Summary.

Allow certain apps to be authorised at a workspace rather company wide level. For multi-department or multi-org companies using Front, are scenarios in which different teams use different instances or workspaces for the same application. E.g. Jira

Exposing new API endpoints for extracting CSAT Scores would be very useful. For example, provide a `GET /analytics/csat` endpoint to list CSAT scores. Provide the response data in a structured way with the score, reviewer, reviewee (teammate), com...

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.

Some conversations don't need to be answered (newsletters, automations etc.). They are archived/resolved very fast and therefore skew analytics' metrics. Conversation stages offered a "no action needed" status, but are now deprecated. The "archive...

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

Show week numbers on the Front Calendar