All ideas

Allowing the rule to define what teammates / teammate groups should be evaluated

Suggestion to have bcc field as default when creating message (new or forwarding, replying)

As teams grow on Front sometimes they need to expand from a single workspace into multiple workspaces. That process is extremely difficult and ad hoc.

Hide comments from teammates (while still recording results).

Allow admins to configure audiences on individual articles based on user segments. Not just based on knowledge base but instead, based on the actual article or category itself. Ensure that AI autopilot or copilot replies reference the correct know...

Give the ability to customize the HTML of a form channel more easily with the UI of a customer portal form. This allows you to have a customer portal embedded into your own website that funnels into Front.

Today, users can delete all the content in a KB and rename it or they can unpublish a KB but there is no way to delete it entirely

At present, Front API/OAuth tokens have very wide permissions, such as the "Shared Resources" token scope allowing read+write access to all shared resources. To help improve security, it would be great to support more granular scopes such as read/...

The new design of a Chat conversation means that Inbound messages, Outbound messages and internal notes/comments can be difficult to distinguish due to the shades of blue and grey used. The compose box also now has a "Shared Draft" bar at all time...

Would be based on the open-archived status, and replace the old "archived" metrics