All ideas

It would be a simpler way to share the reports with colleagues rather than a csv file.

Currently stats on the Tags Table display the stats on a tag by tag basis with no rollup. It would be nice to the hierarchy and a rollup metric for the nested tags to help track the full scope of the tag, and its children instead of having to look...

number of first responses (not response time, simply volume) by day and channelnumber of second responses (again, only volume) by day and channel on those same threads

Current limit on Customers Tab is 200 rows in dashboard export / API

If a teammate group's membership is managed by an IdP (Entra, Okta, etc.), the teammate group cannot be edited in Front via the API. This behavior prevents Admin from controlling a teammate group's contacts and contact list access. To control the ...

Adding FT requirements per hour would provide visibility on how many people you need at different times of the day.

Be able to create a test suite of conversations and the desired branch that was taken for them in a Front rule. If I had this capability, I could ensure that any new changes to a branch by Autopilot answer rule did not break backward compatibility...

As a Front user setting up a branch by autopilot rule, I want the ability to test the rule on a specific message in the conversation. Otherwise, if I test on the conversation as a whole, the context may be different than what I hope to test. As is...