Chat Widget

SUMMARY (the short version) If you've custom-branded your Chat Widget, one setting — "System message text color" — controls several different pieces of text that sit on different colored backgrounds at the same time: the post-chat feedback prompt, the "start a new chat" button text, and the legal/consent disclaimer under the contact form. Because those backgrounds are different colors, there is no single color value that stays readable on all of them. Pick a color that reads on the dark area and the consent disclaimer on the accent-colored panel becomes hard to read. Pick one for the panel and the rest suffers. Requesting that these be split into separate color controls. WHO HITS THIS Any agency that (1) customized the widget colors beyond the default theme and (2) uses the legal/consent checkbox + disclaimer. If both are true, you likely already have a consent disclaimer that's lower-contrast than you'd want and no way to fix it without compromising the rest of the widget. WHY IT MATTERS (not just cosmetic) Of the texts tied to this one setting, the legal/consent disclaimer is the one that fails contrast on the accent panel, and it's also the one that carries the SMS/email consent language. So this isn't only a branding annoyance — it means agencies can't reliably guarantee the consent text is legible without degrading the rest of the widget. The other affected texts (feedback prompt, restart button) are cosmetic by comparison. THIS HAS ALREADY BEEN DONE ONCE — THIS IS THE NEXT STEP This is not new architecture. The August 8, 2024 "Chat Widget Upgrade" split header message and welcome message text colors out of previously shared tokens — the welcome message color was previously bound to "System message text color." That release already established the pattern and the mechanism for carving a surface out of this shared setting. This request applies the same approach to the surfaces that release didn't cover. THE ASK Split the texts currently bound to "System message text color" into independent color controls. Minimum viable version: a dedicated color for the legal/consent disclaimer, separated from the feedback prompt and restart button. That alone fixes the only readability-failing, compliance-relevant case. Full per-surface separation is the preferred end state. ALSO DESCRIBED AS (so others can find this) System message text color shared across multiple elements; consent text unreadable; disclaimer text color; legal disclosure low contrast; chat widget text not readable on colored background; separate / individual / granular text color settings; per-element color customization in Live Chat widget. REFERENCE Originated from premium support ticket 5476653. Reproducible from a standard Live Chat widget with custom colors and the consent disclaimer enabled.

Idea: Enhance the chat widget to include a more engaging video chat bubble similar to https://www.warmwelcome.com/Benefit : This will drive up website engagement and conversions for many industries especially if that video chat can also be used to collect reviews and user feedback. HIGHLVL-I-3265

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

Including the subaccount's chat widgets in the Snapshots would be a time saver because of all the different customizations possible that we have to do for each new sub-account using basically the same widget

Have the ability to set delays in showing the chat bubble. Currently, as soon as the chat widget loads, the chat bubble pops right-away and it's covering all the elements of the funnel or landing page. I would love to have my audience read the content first in a few seconds and have the chat bubble pop-out to remind them that they can talk to us via chat widget. Optimize the chat widget as well with the new cookie consent prompt. Currently the chat widget is covering the buttons in desktop view.

Each Chat Widget customization can be select its own agent specifically. So, we can utilize different different chat widgets on different funnels by minimizing one step of transferring bot. Also if we have function specific page like technical support so the chat widget initiates with its own specific agent on that page.

I would love to allow a chat widget to be opened and centered on a web page. This will allow us to start chatting with people live, or use AI to start chatting right away, without someone having to click the pop up button. Like the image attached. It could also allow us to collect live leads, and have a lead opt in and begin a conversation immediately live or with ai.

Hello team, The new chat widget whit voice AI is great, however not being able to record and transcript the call we are missing what's happening during these call , we are not able to attack the pain point or understand customer experience which allows us to enhance AI behavior. Is there any plan regarding launching this feature soon?

Hi HighLevel team and community! Currently, Conversation Agent widgets can be 'steel' and embedded anywhere without restrictions, creating a major security gap. I suspect one of my client's chatbots was hijacked—conversations appearing have zero relation to their business, but I can't check which URL the widget was used on. Why this matters? Admins need to whitelist specific URLs (e.g., only client.com pages) to prevent unauthorized use and track abuse. This is a critical security flaw that could expose sensitive data. Has anyone experienced this? Vote if you agree—let's secure our widgets! #GHL #ConversationAI #Security #Widgets #FeatureRequest

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)