Add an AI Chatbot to a GoHighLevel Site

What connecting GoHighLevel gets you

If you build client sites in GoHighLevel, you are already selling the thing an AI support agent completes: a site that captures leads and books appointments without the client lifting a finger. What the site can't do is answer the question that arrives before the form gets filled in.

Connect Evoriqa and every client site you ship carries an agent trained on that client's own content — their services, hours, pricing, and policies. It answers around the clock, captures the lead when the visitor is ready, and hands anything real to the client's team. It's one snippet per site, pasted in the same settings panel you're already in.

Where the snippet goes

In GoHighLevel, custom code for a site lives in the site's own settings rather than in a page. Open the website, click the three dots at the top right, and choose Settings. There you'll find two fields: **Head tracking code** and **Body tracking code**, which install a site-wide tracking code into the header and the body respectively.

The Evoriqa snippet goes in Body tracking code. It applies across the site, so one paste covers every page you've built and every page you add later.

For a funnel rather than a website, the equivalent settings are reached by selecting the funnel step and opening the Publishing tab.

Why it won't show up in view-source

This is the part that wastes an afternoon if nobody tells you, so: after you paste the snippet and save, do not check whether it worked by viewing the page source. It won't be there.

GoHighLevel injects head and body tracking codes on the client side, in the browser, so they don't appear inside the static HTML the server sends. What you see in view-source is the initial HTML used to render the page, not what the page becomes. The correct check is the live page itself: open it and look for the chat bubble, or find the script tag in your browser's element inspector rather than in the raw source.

Before you start

You'll need edit access to the GoHighLevel site or funnel and the embed snippet from the client's workspace on the Evoriqa side, with that client's chatbot id in it. Each client site gets its own snippet — that's what keeps one client's knowledge base, conversations, and leads separate from another's.

If you're evaluating this for an agency, start free at app.evoriqa.com; no credit card needed.

Selling it under your brand, not ours

The reason this integration exists is resale, so the widget is built to carry your name rather than ours. White-label Evoriqa runs on your logo, your colours, your custom domain, and branded system emails, so the agent your client logs into looks like part of the package they already bought from you.

Underneath, each client sits in an isolated workspace with role-based access, and their AI usage draws from one pooled credit plan with per-client spend caps — so you can price a client's agent as a monthly line item and know what it costs you. That's the same model the rest of the agency programme runs on.

Confirming it's live

Publish, then open the live client site in a private window and look for the chat bubble in the bottom-right. Ask it a question only that client's content answers, to confirm you pasted the right workspace's snippet — on an agency account running a dozen sites, pasting client A's chatbot id onto client B's site is the mistake to check for first.

Common questions

Head or body? Body. The head field is for tags that belong in <head>; the widget belongs at the end of the body.

Does one snippet cover every page? Yes — the body tracking code is site-wide, so new pages inherit it automatically.

Do I need a separate snippet per client? Yes, and you want one. Separate chatbot ids are what keep each client's knowledge and conversations isolated.

Will it clash with the GoHighLevel builder's styles? No. The widget is isolated in a shadow DOM, so the two never touch.