All ideas

In order to connect FRONT with AI agents, an MCP Server would make this incredibly more easy than handling all the APi tasks.

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.

If a teammate forgets to mark themselves OOO, then it will disrupt the team's workflows and assignment rules. Today, only a company admin or teammate with 'Teammate - Invite/Manage' permission can change another user's OOO status. By adding a new ...

As title says, allow a Front admin to not allow people to track their requests in the Customer Portal, only submit them. This would also mean allowing submitters to continue their portal conversation via email or a different channel since all comm...

Ability to view the inbox and settings side by side

When a Conversation or subset of teammates need management oversight, it would be nice to be able to automatically subscribe a Teammate to a Conversation with rules. Right now, notifications serve as partially good, but when the conversation is be...

As an operator / agent, I'd like to be able to "end" a chat with a customer. They can still start a new one.

At present, Front API/OAuth tokens have very wide permissions, such as the "Shared Resources" token scope allowing read+write access to all shared resources. To help improve security, it would be great to support more granular scopes such as read/...

We have clients who own multiple businesses. It would be very useful if a single Contact could be associated with multiple Accounts. This would allow our Contacts organization in Front to better match reality.