Don't generate placeholder name when chat visitor doesn't provide a name
When a user does not provide a name and the conversation is routed to an agent, Front creates a unique name for the participant (like "Blue Elephant"). It's causing agents to reply with those names and there is a preference for those to come throu...
We used a different chat app before and used to be able to see the navigation history of the guest we were chatting with, it was really helpful to understand what the guest was looking at at and what other pages he had visited before
Continue chat conversation across different channels for end user
Sometimes although a conversation may start on live chat, we may want to continue it on another channel like email, SMS, or WhatsApp. Currently there's no easy way to transition a chat conversation to another channel type.
Is it possible to update the chatbot transcript so it shows chat bubbles instead of a thread with all the chatbot history? It's better to show maybe 20 of the last messages with chat bubbles.
When a customer reaches out and is not verified (is not logged in), a random name appears on the chat. We would like these these chats to come in with users' name as 'Visitor'.