Olotalk
Docs

Install on your platform

Olotalk installs with one line of HTML — the same snippet works everywhere. These guides show exactly where that line goes on the tools people build sites with.

<script
  src="https://cdn.jsdelivr.net/npm/@olotalk/assistant-loader@0/dist/loader.iife.js"
  data-olotalk-assistant-id="YOUR_ASSISTANT_ID"
  async
></script>

Find your Assistant ID (ast_oltk_…) on your assistant’s Install step. Brand new? Do the Quick start first — it covers creating an assistant and adding content.

Can’t add code at all? Your assistant also works with zero installation through its Share link — a hosted chat page with a printable QR code.

Web only. The snippet embeds in websites — including any mobile website. Native mobile apps aren’t a target; where an app needs the assistant, point it at your Share link, which opens in any browser.

Several sites, one assistant? That works: add every domain under Install domains and paste the same snippet everywhere. Create separate assistants only when the sites need different content or behaviour.

<html>
<head> … </head>
<body>
… your page …
target<script src="…/loader.iife.js" data-olotalk-assistant-id="…" async></script>
</body>
</html>
Paste the snippet into target. Wherever a platform puts it, the goal is the same: it loads just before the closing body tag.

Website builders & no-code

CMS & blogs

E-commerce

Tag managers

Two rules that apply everywhere

Almost every install problem is one of these. Skim them once and you’ll likely never need the Troubleshooting page.

  1. Allow your domain. The assistant only loads on hostnames you’ve added under your assistant’s Install domains — including your builder’s preview domain (e.g. *.myshopify.com, *.webflow.io). Miss this and the launcher doesn’t appear — though not silently: your dashboard’s Install status card shows the blocked hostname with a one-click fix. (Wix is the exception — its custom code runs only on your connected custom domain, not on *.wixsite.com; see Troubleshooting.)
  2. Use site-wide custom code, not an “embed” block. Most builders have a per-section “Embed HTML” element that renders inside an iframe — a floating chat button can’t escape it. Always use the platform’s site-wide custom code / footer feature instead.

Don’t see your platform? Anything that lets you add a <script> before </body> works — see the Embed reference for the generic instructions and advanced options.