All ideas

Ahead of scheduling the meeting, allow for a link to be sent out to multiple people with multiple time options so that everyone can weigh in and give their preference on a meeting time. From there, the organizer then choose to schedule the meeting...

Being able to turn off auto-suggest in composer for all Front users

Case: after tag deletion Situation: Currently, when an admin deletes an AI tag from an AI tagging rule, the associated message samples used for training are also removed. If the admin wishes to add the tag back, they must go through the process of...

Ability to configure different Welcome Messages for Front Chat across your website depending on URL

When building a Jira issue-created macro, we can't let the agent select which Jira teammate it should be assigned to.

Every time someone comments on a Jira Ticket, ALL tickets linked to the issue are opened in our Front inbox. Ideally, we would need the comment to be sent to the ticket (& thus only that ticket should open again) where the Jira issue was origi...

After installing Front Chat on my site, I see various items logged to the browser console, like the chat version - could you add an option to the Chat init code to allow developers to disable these logs?

As a Front Admin, I want to be able to duplicate a Macro so that I can easily create a new one with similar settings, as opposed to setting one up from scratch. For example, if I want to set up the option to move into an inbox, it'd be much easier...

There currently is the ability to add notes to a contact but when you switch the contact to the account level, that feature goes away. This would allow us to log notes to the account regardless of who reaches out to our support team.

The ability to set a global inactivity period for all inboxes. At present Close conversation segment if inactive for can only be set on a per inbox basis. Creates a massive manual lift if a company needs to mass update all their inboxes.