All ideas

Requesting a 4th option is added for Chatbot end-of-path options - the option to create a new Customer Portal thread. Our team wants to move towards a portal-based support model, so auto-creating a new portal conversation when a chat visitor needs...

Macros or quick action buttons that we can surface on a contact, account or app object card. If we want to be an operations cross team platform it would be great to have actions that appear elsewhere in the platform, not just on the conversation. ...

To monitor the "seen" status of messages, api clients currently need to implement a polling strategy. Adding a seen event to enable web-hook integration, will limit api usage and improve state change detection.

At the moment you cannot delegate all inboxes of a member of staff without showing all their private discussions. But if you turn off delegation and select their inbox, you can then no longer see assigned emails etc.

Microsoft Forms integration to allow for easy form submission/poll creation directly in Front Composer

Ability to create macros at the PERSONAL level For instance for me : answer to my private email, and then automatically label them "to follow", and move it to custom/personal view of this label "to follow" Thanks,

Today, users can edit conversation subjects. However, the action is not logged in the activity thread. Admins need to track every action. Editing the subject of the conversation cannot be tracked (unlike most of the other actions)

When a message is received in Front, the name of the contact saved in Front should be displayed over the sender information provided in the message headers.

Admins would like the ability for Front to detect Japanese for multiple use cases.

Keeping an external record of workspace configuration requires periodic polling of the API, which is inefficient and not real-time. To support better auditing and configuration backups, Webhooks integration should be expanded to include admin even...