Live Chat

Customer would like to: 1) increase the number of options from 8 to something higher. Currently they need 10 but want the chance to expand further in the future 2) Increase the character limit from 35 for these options. The customer has a number o...

When customers are not using our website on full-screen mode, the current chat box will expand & take up their entire page. Previously, the chat box would only show up in a smaller screen on the bottom right corner. We'd like this small chat b...

Requesting a 4th option is added for Chatbot end-of-path options - the option to create a new Customer Portal thread. Our team wants to move towards a portal-based support model, so auto-creating a new portal conversation when a chat visitor needs...

Integrate chatbot with API so we can automate lookups to external databases. Ex) Automate lookups like appointment time, enter a zip code to find store locations, etc.

Google Ads conversion events for Chatbot – track users who come to our website from an ad and interact with the chat (and not the other CTAs).

When viewing a completed Front Chat transcript that's transitioned to a conversation, the teammate is presented with a transcript that looks something like this. It's tricky to tell the difference between multi-select options the user entered vs f...

Ability to show chat visitors which support agents are currently online and also the average response time like Intercom does. Would also be helpful to display a message "The team will reply in [xx] hours" if no one is online.

Right now, links (event those from the knowledge base) need to be sent as URL text. A nice to have would be to display a nicer block with a preview of the link webpage (like shown on the chatbot marketing assets at launch)

Currently the Chat SDK allows you to verify chat visitor identity using email only. This would allow you to verify chat visitor identity using other fields like phone number or user ID.

We already have live chat message templates that address commonly asked inquiries. We'd like to be able to use them directly in the chatbot flow instead of having to replicate them manually.