All ideas

Right now Front requires a channel_id to be supplied on calls to Create Draft endpoints - this is not required on send reply endpoints. Could we have the API select a default channel when the channel_id param is not supplied?

Could you please move the Tags in the message composer UI to facilitate the use of TAB to add tags? Meaning that after entering the "To" field into the composer field, you'd be able to TAB to the tags and more easily add a tag to an email.

Show and edit custom fields directly in teammates table without having to navigate into each user.

Be able to keep track of open / waiting etc. conversations on a regular basis

Currently, the scope of the report is not taken into account when calculating the metrics, leading to multiple counts. Ex: conversation is moved from inbox A to B. It will increment the new workload by one (for B) and the closed workload by one (f...

The metric is confusing and does not fulfil the user's expectations. It is particularly wrong in the time breakdowns (heat map, time chart) Could also be solved by changing its definition (=> make sure it is not counted twice by tying it to a s...

This would allow users to share specific rules, views, pages, inboxes, they are viewing with teammates. Currently not possible in the Desktop app.

This would be useful when sending emails to customer attempting to drive them to a specific page/landing page.

Sentry is a bug tracker, but also has a "User Feedback" feature, which is a perfect fit to pipe to a Front inbox.