GoHighLevel Chat Widget: Setup, SMS Chat & Live Chat (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 31 July 2026 · 10 min read

On this page: What the chat widget is · Modes compared · Installing the widget · Branding and customisation · Routing to Conversations · Conversation AI on the widget · Follow-up automation · SMS consent and ACMA compliance · Measuring performance · Agency use cases · Common mistakes · FAQ

The GoHighLevel Chat Widget is the small chat bubble you add to any website that turns anonymous visitors into contacts you can actually follow up. Unlike most standalone chat tools, it does not trap the conversation in the browser. In SMS Chat mode it captures the visitor's mobile number up front and moves the whole exchange to text message, which means the lead survives even if they close the tab two seconds later.

I install this widget on almost every Australian client build, whether the site is a GHL funnel or a WordPress site the client has had for years. In this guide I will walk through the three modes, installation on GHL and external sites, branding, routing to the Conversations inbox, attaching a Conversation AI bot, follow-up workflows, and the ACMA compliance side that too many agencies skip.

What the chat widget is and where it lives

Inside a sub-account, go to Sites > Chat Widget. You can create multiple widgets per location, each with its own mode, branding and targeting, which matters when a client runs several sites. Under the hood the widget runs on LeadConnector, the same infrastructure as the mobile app, so every visitor message is a first-class message in your account rather than a webhook bolted on the side.

The practical difference from tools like Tidio or Intercom is ownership of the follow-up. The widget writes directly into the CRM, so contact records, tags, custom fields, pipelines and workflow automation all happen natively — no Zapier bridge to break, no separate inbox to forget.

SMS Chat vs Live Chat vs WhatsApp: modes compared

Choosing the mode is the single most important decision in the setup, because it determines what happens when a visitor walks away mid-conversation.

Why I default to SMS Chat for Australian clients

Live chat only converts when someone is actually watching the inbox, and most small businesses are not. SMS Chat mode sidesteps the problem: the visitor asks their question, gets on with their day, and your reply arrives as a text they will actually read. The trade-off is friction — asking for a mobile up front deters some casual browsers — but the leads who come through are far easier to close because you hold a verified number from message one.

When Live Chat wins

Live Chat mode suits e-commerce and larger teams with rostered coverage, ideally with Conversation AI as first responder so a human only steps in when needed. An email capture step means a session that goes cold is not a total loss.

Installing on GHL funnels vs external sites

GHL funnels and websites

For pages built inside GoHighLevel, there is no code involved. Open the funnel or website settings, and enable the chat widget for that site; the widget attached to the sub-account appears on every step. You can also toggle it per funnel if, say, you want chat on the home page but not on a distraction-free checkout.

WordPress and other external sites

Every widget generates an embed script under its settings. Paste it before the closing body tag: in WordPress via a header/footer scripts plugin, in Shopify via theme.liquid, on Squarespace or Wix via the code injection panel. One script serves the whole site, and any styling or prompt changes made later inside GHL push out automatically. The official steps are in the GoHighLevel help centre if your platform is unusual.

Branding, colours, avatar and prompts

The widget builder gives you control over the pieces visitors actually notice: brand colour for the bubble and header, an avatar photo (use a real staff member, not a logo), the intro heading, the prompt message that pops after a delay, and the acknowledgement text shown once a message is sent. In SMS Chat mode you can edit the legal consent line beneath the form, which becomes important for compliance later in this guide.

For agencies on a white-label plan, the "powered by" branding can be removed or replaced with your own agency name and link. That, combined with per-client colours and avatars, means the HighLevel chat widget you deploy looks like bespoke software your agency built, not an off-the-shelf plugin, and that perception matters when you are charging a monthly fee for it.

Routing messages to the Conversations inbox and mobile app

Every widget message, regardless of mode, arrives in the Conversations inbox alongside SMS, email, and social messages, so your team works one queue instead of five tabs. Push notifications go to the LeadConnector mobile app, where most of my tradie and clinic clients actually reply from. A new chat creates or updates a contact record automatically, capturing name, phone and source page into custom fields you can reference in automations.

Set expectations honestly in the widget copy. If nobody monitors chat after 5pm, say so in the acknowledgement message and lean on automation for after-hours coverage. The same principle applies to phone: if you have not already wired up missed call text back, chat and calls should both fail over to SMS so no enquiry dead-ends.

Attaching Conversation AI so the bot answers and books

This is where the widget stops being a message box and starts being a receptionist. Enable Conversation AI on the widget channel and the bot answers instantly, any hour, trained on your business FAQs, web pages and uploaded documents. In auto-pilot mode it handles the full exchange, including offering calendar slots and booking appointments directly; in suggestive mode it drafts replies for a human to approve while you build trust in its answers.

Because SMS Chat mode moves the thread to text, the bot follows the lead there too, continuing the same conversation over SMS until the visitor books or asks for a human. Configure a clear handoff: I use a workflow that removes the bot and notifies staff whenever intent keywords like "price for" or "speak to someone" appear. For prompt design, training sources and booking configuration, see my full GoHighLevel Conversation AI guide.

Follow-up automation when a visitor leaves

The widget's real ROI comes from what happens after the first message. Two workflow triggers do the heavy lifting: Customer Replied (filtered to the chat widget channel) fires on inbound messages, and the chat widget survey submitted trigger fires when the initial contact form is completed. From either, a simple sequence works: tag the contact chat-widget-lead, notify the team, wait five minutes, and if nothing has resolved the enquiry, send an SMS: "Hi {first name}, saw your message on our site — still need a hand?"

For leads that go quiet, a short two-touch nurture over 48 hours recovers a surprising share — reference their original question and include a booking link. Because the source page is stored on the contact, you can branch follow-up by service line with an if/else condition.

SMS consent and ACMA compliance for Australian businesses

When a visitor submits the SMS Chat form, replying to their question is fine, as that is a conversation they initiated. Ongoing marketing messages are a different matter. Under the Spam Act, commercial SMS requires consent, sender identification and a working unsubscribe, and the ACMA actively enforces this with substantial penalties. Keep the widget's consent text visible and honest about what the number will be used for, and honour opt-outs immediately, which GHL handles automatically when someone replies STOP.

If you are texting US numbers as well, carrier-side A2P 10DLC registration is mandatory before SMS will deliver reliably. Australian sending does not use the A2P framework, but ACMA's consent and identification rules apply to every local message, so treat the widget's consent text as a legal record, not decoration.

Measuring performance

Track four numbers monthly: conversations started, contact capture rate, median first-response time, and appointments booked from chat-tagged contacts. The tag applied in your intake workflow makes the last one easy to filter in any pipeline report. I benchmark a healthy SMS Chat widget at 2 to 4 percent of visitors starting a conversation, with 30 to 50 percent of those booking within 30 days when AI and follow-up automation are in place. If conversations are high but bookings are low, the leak is usually response time or a thinly trained bot, not the widget itself.

Agency use cases and reselling

For agencies, the chat widget is one of the cleanest recurring-revenue wedges in the platform: visible on the client's site every day, demonstrably capturing leads with mobile numbers attached, and deployable from a snapshot in under an hour. Common packaging is "24/7 website chat" in a base plan, with the Conversation AI layer upsold as an AI receptionist tier at a healthy margin over usage costs. White-labelled and paired with a monthly chats-to-bookings report, it becomes very hard to churn from, because leaving means putting a dumb contact form back on the site.

Common mistakes to avoid

• Choosing Live Chat with no one rostered to answer. A chat that goes unanswered for an hour is worse than no chat. Use SMS Chat mode or put Conversation AI on first response.
• Skipping the consent wording. Leaving the default text untouched, or deleting it, weakens your Spam Act position for any later marketing SMS. Customise it and keep it visible.
• Pasting the embed code on only some pages. Add it site-wide in the header/footer template, then exclude specific pages deliberately rather than the other way round.
• No follow-up workflow. Without a Customer Replied trigger and a timed nudge, cold chats simply die. The automation is the product.
• Launching the AI bot untrained. A bot that answers "I'm not sure" three times in a row burns trust. Load FAQs, services and pricing boundaries before switching to auto-pilot.
• Using a logo instead of a human avatar. A real face with a first name consistently starts more conversations than a badge.

If you want website chat wired into SMS, AI and your calendar so no enquiry slips through, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

Does the GoHighLevel chat widget work on WordPress?

Yes. Copy the embed script from Sites > Chat Widget and paste it into your theme's footer via a header/footer scripts plugin or the customiser. One script covers the whole site, and any later styling or prompt changes made inside GHL update automatically without editing the code.

What is the difference between SMS Chat mode and Live Chat mode?

SMS Chat captures the visitor's name and mobile number first, then continues the conversation by text message, so the lead persists after they leave your site. Live Chat is a real-time, session-based conversation in the browser, best when staff or an AI bot can respond within seconds.

Can Conversation AI answer chat widget messages and book appointments?

Yes. Enable Conversation AI on the widget channel and the bot replies instantly using your training data, and in auto-pilot mode it can offer calendar slots and book appointments directly. In SMS Chat mode the bot continues the same thread over SMS after the visitor leaves the site.

Do Australian businesses need A2P 10DLC registration for the chat widget?

A2P 10DLC only applies when texting US numbers. For Australian sending, ACMA's Spam Act rules apply instead: you need consent for marketing SMS, clear sender identification and a working unsubscribe. Replying to a chat enquiry is fine; ongoing promotions require the consent your widget form should capture.

Can agencies white-label the chat widget for clients?

Yes. On agency plans the LeadConnector branding can be removed or replaced with your own agency name and link, and each client widget can carry its own colours, avatar and prompts. Most agencies bundle it into a monthly plan and upsell the Conversation AI layer as an AI receptionist tier.