All ideas

Give Front rules the ability to interact with the read receipt setting so that we can create automations around this product behavior

I was on a call with Tarion and they wanted to be able to embed a form on their website but they're not that technically sufficient with HTML, so they're probably going to use a 3P. It would be great if Front could provide a drag and drop feature ...

Have the ability to change a once private tag to a shared tag.

User StoryAs a business owner, I need to work with SaaS providers that allow me to increase or reduce my software seats during a given year based upon headcount. Current FunctionalityCurrently Admins are allowed to increase software seats during a...

Situation: Currently, AI Answer for Chat only supports a single knowledge base, limiting its ability to draw from multiple sources of information. In scenarios where knowledge is spread across several external public knowledge bases, users cannot ...

Once a message comes in from Slack, any edits that the original creator makes are not updated in Front, making it possible to miss information without going back to check the message in Slack. Images as an example.

As an Admin, I want to create a View that includes inboxes from multiple different workspaces.

Have the option to be notified/export audit logs. This can be via webhooks and/or a dedicated API endpoint. This is useful for: Monitor changes in workspace configuration on internal dashboards Add logs into SIEM platforms like Sentinel

SLA rules work on "oldest unreplied message". This makes sense because that's how long the end customer has been waiting. But some use cases require it to work on "last unreplied message".

When moving a message to a new conversation, there is no base rule trigger to automate actions on the new conversation. This idea suggests adding a new item to rule triggers for when a conversation is created from a split.