Live Chat Widget

One script tag on your site, and every visitor conversation lands in your Live Chat agent dashboard.

Integrator guide, document version 1.3.

1. How It Works

The snippet loads a small script that injects a chat bubble into your page as an iframe. No account, password, or SDK install is needed on your side — the widget figures out which company (tenant) it belongs to from your website's own domain.

2. Before You Install — Your Domain Must Be Registered

The widget identifies your company by matching your website's domain against a registered list — not by a login or an API key. Your domain has to already be added to your tenant's origin list before the widget will work.

3. The Snippet

Paste this right before </body> on every page you want the chat bubble to appear on:

<script src="https://chat.enopsy.com/embed.js" data-code="your-site-name" async></script>

That's the whole thing — one tag. An older two-tag form using window.LiveChatConfig still works if you already have it installed that way, but there's no reason to use it for a new install:

<script>
  window.LiveChatConfig = {
    code: "your-site-name"
  };
</script>
<script src="https://chat.enopsy.com/embed.js" async></script>

Config fields

4. How To Add It To Your Site

It's one <script> tag — how you get it onto every page is up to you. Three common approaches:

Hardcode

Paste the script tag directly into your HTML, right before </body>, on every page you want the bubble to appear on. See the snippet in Section 3.

Google Tag Manager

1. Open your container at tagmanager.google.com.
2. In the left sidebar click Tags, then New (top right). Name the tag, e.g. "EnOpSy Live Chat Widget".
3. Click the Tag Configuration box → choose type Custom HTML.
4. Paste the script tag from Section 3 into the HTML box, exactly as shown.
5. Click the Triggering box. Pick an existing DOM Ready or Window Loaded trigger that fires on all pages, or create one (+ → Trigger type DOM Ready or Window Loaded → "fires on all DOM Ready events" / "all Window Loaded events") — not All Pages / Initialization / Consent Initialization (these can fire before <body> exists).
6. Click Save.
7. Click Preview (top right), open your site in the preview session, and confirm the bubble appears and the tag fired on the expected trigger in the Tag Assistant debug panel.
8. Back in GTM, click Submit (top right), add a version name/description, then Publish.

Other Tag Managers / CMS Script Injection

The same rule applies everywhere: whatever "fire on" / "load timing" option the platform offers, pick the one closest to DOM ready — not "as early as possible" or a plain <head> injection. If the platform only offers a single header-code field with no timing choice, prefer a footer/body-end field instead if one exists — for the same reason hardcoding goes before </body>.

5. How Your Company Is Identified

When the widget loads, it reads the domain it's running on (from the page's own origin, falling back to the referring page) and asks EnOpSy "who owns this domain?" That lookup is what your registered origin list (Section 2) answers. Nothing about which company you are comes from the snippet itself — swapping the code value to something else has no effect on this.

6. Verifying It Works

1. Load your page and confirm the chat bubble appears in the corner.
2. Send a test message from the widget.
3. Log into chat.enopsy.com — the conversation should appear in the conversation list within a few seconds.
4. Reply from the dashboard and confirm it shows up back in the widget.

7. The Agent Side

Your team doesn't need a separate account for this — signing into chat.enopsy.com uses the same login as the rest of your EnOpSy account. Once in, every visitor conversation across every one of your registered domains appears in one shared conversation list, with a live-visitors panel showing who's currently browsing.

8. Troubleshooting