All ideas

It would be very helpful if there was a condition in rules that allowed you to trigger a rule based on what Front user performed the originating trigger/action. For example, we have an SLA set up but we have a tag that will exclude a message from ...

Provide access to contacts and accounts, similar to the plug-in available on the web browser and desktop app.

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

Ability to customize the link of the company logo to redirect to another link i.e. company website instead of the knowledge base home page.

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

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.

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

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

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