Chat Widget

Current live chat does not pass any attribution back to the CRM so we have no way of knowing where the contact came from.

We need much greater control over when and how the chatbot appears on a website, especially for high-end and conversion-focused sites. At the moment, auto-opening chat windows can: Negatively impact SEO (heavy scripts + CLS concerns) Increase bounce rate Feel intrusive or irritating rather than helpful Reduce perceived brand quality on premium websites Requested Capabilities Chat Trigger Timing Controls Ability to set chatbot behavior based on: Time on page (e.g. after 30s, 60s, etc.) Scroll depth (e.g. 25%, 50%, 75%) Exit intent (desktop) First visit vs returning visitor Option to disable auto-open entirely Bubble-Only Mode (Default Closed State) Allow the chatbot to load as a floating icon/bubble only The full chat window should never open automatically User must consciously choose to engage This is essential for premium and high-end websites. Page-Level & Site-Type Customisation Ability to define different chatbot behaviors by: Page type (home, landing page, blog, checkout, contact) URL rules or page groups Example: Homepage → bubble only Blog → delayed trigger Checkout → disabled entirely Performance & SEO Considerations Lightweight loading options Defer or lazy-load chatbot scripts Clear controls to minimise impact on page speed and CLS Why This Matters Chatbots should feel like a helpful tool users can choose to engage with, not an interruption forced on them. For many brands, especially in tourism, luxury, and professional services, over-aggressive chat behavior damages trust and conversions. Better control over timing, triggers, and display would: Improve SEO outcomes Reduce bounce rates Increase intentional, higher-quality conversations Make GoHighLevel more suitable for premium websites and agencies

Right now, options are 2, 5, 10, and 15 minutes. Would be great if you could do custom time, especially with seconds (I want to do 30 seconds)

Currently, in the GoHighLevel chat automation, email notifications are sent each time there’s a new user response, which can lead to an overwhelming number of notifications if the user replies multiple times in one conversation. To streamline this, I’m requesting a feature that would allow users to receive a single email containing the entire chat transcript when the conversation has ended. Proposed Solution: Checkbox for "Email me a transcript": Add an optional checkbox in the chat window labeled "Email me a transcript of this conversation." If selected, a single email with the full transcript will be sent to the email address provided once the chat session is marked as "ended" or "resolved." Condition-Based Automation: Include an automation condition to check if the chat status is “ended” or “closed.” When the condition is met, trigger an email with the complete transcript, preventing repetitive notifications. Benefits: Improved User Experience: Users will appreciate the convenience of a single, complete email for review rather than multiple, fragmented notifications. Reduced Notification Overload: This feature would reduce the frequency of email notifications during an ongoing chat, helping users focus on responding to the conversation rather than managing notifications. Thank you for considering this feature. I believe it would enhance the functionality of GoHighLevel’s chat feature, making it more user-friendly and efficient.

Enable intelligent blocking of specific incoming live chats from "Guests" both manually and automatically based on their messages, browser fingerprint, session id, cookie, IP, device id etc..

Is there any option where we can receive the whole details that was opted in the chat widget and not just have the plain notification of "Congratulations! You have received a chat. The following are the submission details." Basically, we want the whole "submissions details" included in the notification.

Europe is home to 600 million inhabitants with significant purchasing power. With 39 official languages. It represents a vast market that cannot be overlooked. Many other chatbot competitors already offer support for multiple languages, so the technology is readily available. It would be wise to consider implementing multilingual support. Here is a list of the significant official languages spoken across European countries: 1. Albanian (Albania, Kosovo) 2. Armenian (Armenia) 3. Belarusian (Belarus) 4. Bosnian (Bosnia and Herzegovina) 5. Bulgarian (Bulgaria) 6. Catalan (Andorra, Spain - regional) 7. Croatian (Croatia, Bosnia and Herzegovina) 8. Czech (Czech Republic) 9. Danish (Denmark, Faroe Islands, Greenland) 10. Dutch (Netherlands, Belgium) 11. English (United Kingdom, Ireland, Malta) 12. Estonian (Estonia) 13. Finnish (Finland) 14. French (France, Belgium, Switzerland, Luxembourg, Monaco) 15. Georgian (Georgia) 16. German (Germany, Austria, Switzerland, Belgium, Luxembourg, Liechtenstein) 17. Greek (Greece, Cyprus) 18. Hungarian (Hungary) 19. Icelandic (Iceland) 20. Irish (Ireland) 21. Italian (Italy, Switzerland, Vatican City, San Marino) 22. Latvian (Latvia) 23. Lithuanian (Lithuania) 24. Luxembourgish (Luxembourg) 25. Macedonian (North Macedonia) 26. Maltese (Malta) 27. Montenegrin (Montenegro) 28. Norwegian (Norway) 29. Polish (Poland) 30. Portuguese (Portugal) 31. Romanian (Romania, Moldova) 32. Russian (Russia, Belarus - co-official, regional in some countries) 33. Serbian (Serbia, Bosnia and Herzegovina) 34. Slovak (Slovakia) 35. Slovene (Slovenia) 36. Spanish (Spain) 37. Swedish (Sweden, Finland) 38. Turkish (Turkey, Cyprus) 39. Ukrainian (Ukraine)

Add the pages UTM tracking where they initiated the live chat from so we can see where visitors have came from. This is especially essential when people are using AI, so we know if a client converts what ad platform and campaign they came from.

Ability to specify URL query parameters such as ?name=Bob and &email=bob@gmail -- especially useful for Trigger Links or internal-team usage