All ideas

Problem When a single customer email requires multiple quotations or requests, only one ticket ID can be created, forcing the team to artificially group separate requests together. Request Allow multiple ticket IDs to be created against a single e...

Problem Currently there's no way to automatically assign conversations to agents based on their SLA urgency, so high-priority messages with tight SLAs may be routed the same way as lower-priority items with longer SLAs. Request Add an assignment o...

Request Add ability to split a conversation into multiple conversations through the API.

Request Show additional older conversations in the dashboard view for easier access to historical conversation data.

Request Integrate a Microsoft Report Message Add-in with Front, enabling teams to flag and escalate important messages through a dedicated workflow.

Problem API clients currently need polling to monitor message 'seen' status, which limits efficiency and increases API usage. Request Add a 'seen' event to webhooks for real-time seen status updates.

Request Display saved contact names instead of email sender information when messages arrive.

Problem When a single chatbot is deployed across multiple web properties (support.example.com, dev.example.com, etc.), chatbot analytics cannot be filtered by host, making it impossible to isolate metrics by domain. Request Add URL/host-based filt...

Problem Rule conditions cannot explicitly check for empty or null values, preventing workflows like 'do X if subject is empty.' Request Add support for explicit empty/null value conditions in rule logic.

Problem The Analytics tag report displays all tags on filtered conversations or only tags used in the filter, but teams need to hide irrelevant tags from the table. Request Allow users to define a list of tags to exclude from Analytics tag reports...