All ideas

This would allow multiple people to collaborate on the Knowledge base via push and pull requests. It would also allow us to replace our very expensive Gitbooks subscription and keep everything within Front.

In some cases, teammates should never reply to or compose message from a particular shared channel. To ensure this happens, the admin can set the channel settings such that it cannot be used for outbound messages.

Timers in rules at the moment do not reboot when a new event happens. It makes sense most of the time but it's not ideal for some use cases. For instance, you want to send CSAT surveys 5 days after the last email, any new email should reboot the t...

Our team currently has a fairly large number of templates which we use for rules and automations (mostly for off-hours requests). Though we don't change business hours often, when we hire in different time-zones and therefore update hours, it woul...

It would be great to have content localization built into the knowledgebase. Have multiple versions of a page, for example a version for Ireland and a version for the US. The link/url to the page remains the same and the site will show the correct...

Ability to highlight part of a draft and leave a comment for the specific part. My team utilizes the shared email features in Front and they are great, but we regularly collaborate on draft emails to a customer. One feature that we regularly use w...

In the To: section when I start typing "dispatch" I want the first dispatch email that shows up to be dispatch@company.com, it doesn't even show up when I type "disp" I'm required to type "dispatch@co" to get it to appear. .

Our "seen" tracker tell users when an email has been read by the recipient. It can be disabled for a given channel if it is regarded as too intrusive, however, this is not scalable if an admin wants to ensure it is disabled across all channels. We...

For some workflows, it is more desirable to keep conversations closed after task completion.