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.

Customer would like to: 1) increase the number of options from 8 to something higher. Currently they need 10 but want the chance to expand further in the future 2) Increase the character limit from 35 for these options. The customer has a number o...

Today we need to get for each conversation what is the status and if status is resolve when it was resolved. Unfortunately we cannot retrieve this information using the end-point GET List Tagged Conversations or any other end-point. In addition we...

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

Currently we can create articles via API, but are not able to add attachments to it, so the import cannot be fully done without attachments

Would enable conversation in a much easier way, without internal communications being buried in the email thread as they currently are (when it is very easy to miss internal updates or requests if they are buried by emails).

External ID can be set when you create an account but afterwards there is no way to update it, this would be incredibly helpful if we could update the external id.

We're migrating from helpcenter.io and I love the migration and import features but since helpcenter.io is not supported it's going to make it a much more manual process.

A way to quickly view all waiting and open statuses for tickets!