Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 1711

Adding more time conditions to CSAT surveys

This could help increase response rates on surveys by sending them only at times when people are more likely to respond. Ideally, we would like to keep the current Delay and be able to add additional criteria. For example, it would wait 24 hours a...
over 1 year ago in Rule conditions / Workflows 1 Backlog

Add ability to disable autocorrect emojis

Front has a feature that autocorrects certain punctuation to emojis. I would like the ability to disable this feature. I frequently use certain URLs and file paths which autocorrect to emojis. Which, as you can imagine, I don't want to happen. Ple...
about 1 year ago in Core Product Experience 1 Backlog

Set chatbot hours and/or conditionally split chatbot responses based on hours

At a high level we would like to be able to only have our chatbot run in Off Hours and have our support representatives handle all live conversation during business hours. So part 1 of the request: be able to set the chatbot to only turn on during...
over 1 year ago in Live Chat 0 Planned

[action] AI compose to show the before and after

I wish AI compose to be easier to use. Problem 1: It requires to many clicks, it's not automated enough ideas: inline suggestion; autocomplete; floating bar ... Problem 2: hard to know the changes when using a compose text transformation ideas: Se...
7 months ago in AI / AI compose / Core Product Experience 0 Backlog

Multi language chatbot

Possibilty to detect user's browser language and adjust chatbot flow accordingly
over 1 year ago in Chatbots 0 Backlog

Allow a user to send a message only if certain criteria are met

There is currently no way to prevent a user from sending a message. Some examples could be: allow only if the conversation has the tag "approved" block sending to external domains if the conversation has the tag "internal" only allow account manag...
about 1 year ago in Rule library 0 Backlog

Sort conversation list by received/imported timestamp rather than sent timestamp

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.
almost 2 years ago in P2 display - conversation list 0 Backlog

[language] Translate selected portion of previous messages

Currently the "Compose with AI" Translate option is only available for the messaging being composed - it would be very helpful if we can also highlight text from earlier conversations and have that translated as well within Front app. Perhaps as a...
7 months ago in AI / AI language 0 Backlog

Slack channels should still import message text/content if attachment size is too large

Currently we fail to import messages if the message contains a file over 25MB. However, it would be nice if we dropped the attachments that are too large, and still imported the message text. When this happens we should also display some type of w...
about 1 year ago in Existing integrations 0 Backlog

Increase the Merge conversation message limit - 100 is too low

Merging conversations is my favorite Front feature and we use it extensively. We've recently come up against the 100 message limit (15 people on an email chain and 4 support engineers can hit 100 messages VERY quickly). 100 Message merge limit has...
almost 2 years ago in Merge / privacy leaks / threading 0 Backlog