I want to be able to see the inputs a chat visitor has entered when they drop off before completing the flow. For many use cases, this data is crucial as it allows me to know who tried to interact with my chat widget and reach back out to them pro...
Clear definition for Chat Section and Internal Comment
I wanted to share a usability concern regarding the layout of the Chat and Internal Comment boxes. Currently, the two fields are very similar in both appearance and placement, which increases the risk of accidentally sending internal comments to t...
To have the ability to send proactive messages with Front chat on Mobile like we can on the Web. Additionally to be able to recognise the logged in user, that signed into the app for Type of Audience, and then leverage contact info as conditions f...
[context] AI features to leverage Front Conversation History
Leverage past email history for AI Answers/AI Suggested Replies. Past email conversations are a good source of knowledge to reduce product / general inquiries because: Doesn't required to be structured in a specific format Compared to a knowledge ...
Front Chat localization to support different languages
Localization in the chat widget to support different languages. Includes text & buttons in the collect customer details step in the chatbot flow, the "Start new conversation" button after the chatbot auto-archives the flow, and more.
Ability to branch chat based on agent visibility to ensure synchronous chat expectations are met - also to direct customers to submit a request via email or collect information but set expectations that all agents are "busy". and/or - ability to s...
When you view a completed Chatbot<>Visitor conversation in the conversation UI, we see the AI/Visitor messages differentiated by being bolded or not. While the HTML version of the message accessible via the API does contain the same bolding,...