All ideas

The ability to create a linked conversation via the API and attach it to an existing conversation

Customers want to understand the user experience (NPS, CSAT) based on different issue types. Today, we can apply tags to filter in analytics but it'll be an extremely cumbersome process to get a holistic view of this data.

Similar to how the Salesforce and Hubspot rules work

Limit who can add, edit and delete contacts and accounts. This could also include limitations on freely browsing through contact data in the contact manager, although, we cannot restrict the ability to view contact data entirely.

Front today displays conversations in order of when they were sent, not received or imported in the product. This is a suggestion to offer sorting by received timestamp instead of sent.

Share a View with a teammate Group, and pin it to their sidebar. This allows teammates to work from a shared backlog of conversations from certain inboxes and/or certain tags. This is quicker than manually selecting a list of teammates, and also m...

When a conversation is moved by a rule : Choose whether it archives or not for subscribers : today, front automatically archives the conversation for subscribers.

Ability to have scheduling links for 2 or more people so that all teammates can offer their availability and a guest can schedule with any of them.

Customer wants to utilize Gated KB for internal employees that are not Front users. SSO makes this much easier to maintain.

Show the conversation summaries when it can help understand what a conversation is about, across the app so a user can work faster. For example, showing the summaries on conversation previews in the inbox view the search view linked conversation t...