Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 1619 of 1619

[context] Ai tagging based on entity in conversation (date, duration, amount...)

Situation & Request Wish to tag based on non-semantic values such as dates, amounts, and durations. Currently, the AI Tagging tool is not equipped to detect and apply tags based on these structured data types. Potential Solution Invest in enti...
about 6 hours ago in AI / AI tagging 0 Backlog

More granular API / OAuth token scopes

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/...
2 days ago in Core API / Partner Integrations 0

Channel setting: reply-to header

Allow to set a value to the reply-to email header when creating a new email - at least when we create that email through api : https://www.getresponse.com/help/reply-to-field.html
2 days ago in Admin Experience 0 Backlog

[accuracy] Similar conversation based on a more specific entity (inquriy, ticket, order, shipment ...)

Situation: The current “similar conversation” feature in Front is based on semantic proximity. This approach can be inefficient, especially when users need to find conversations related to specific entities like a ticket number, order number, ship...
3 days ago in AI / AI similar conversations 0 Backlog

[context] AI answer for chat to support multiple KBs as source of knowledge

Situation: Currently, AI Answer for Chat only supports a single knowledge base, limiting its ability to draw from multiple sources of information. In scenarios where knowledge is spread across several external public knowledge bases, users cannot ...
4 days ago in AI / AI answer for chat 0 Backlog

[channel] Auto summarize for SMS, Chat

Being able to auto-summarize conversation thread for other channels than email
about 11 hours ago in AI / AI summary 0 Backlog

[granularity] Improve the granularity of summaries details to include the inquiry, steps taken, entities shared like conv_ID, error codes ….

The summary's structure and granularity don't match all use cases. Support agents need more specific information than a collaborator or manager joining a conversation
1 day ago in AI / AI summary 0 Planned

[language] AI Answer to support more languages

AI-based features seem to support some languages but it's not guaranteed for many of them. cc https://help.front.com/en/articles/914304#prerequisites I'd be great if features like AI answer for chat, Suggested replies could leverage knowledge base...
17 days ago in AI / AI answer for chat / AI language / AI suggested replies (auto draft) 0 Backlog

Detect duplicate conversations & route them

Situation: Support teams can encounter multiple customer requests that are duplicates of previously resolved issues, leading to redundant work and decreased efficiency. Request: Implement a feature that automatically detects and flags duplicate cu...
8 days ago in AI / AI similar conversations / Workflows 0 Backlog
331 VOTE

Comments will not cancel a snooze event

A lot of teams have a workflow where they snooze a conversation and continue to comment on it. It can be frustrating for them to always have to click Snooze again when it was internal comments that broke the snooze rather than a message from the c...
over 1 year ago in Snooze 2 Backlog