Quick start

Olotalk is a website AI agent — it answers questions grounded in your content, captures qualified leads, and feeds your revenue pipeline. This guide gets you from zero to live assistant.

Step 1 — Create an assistant

1. Sign in to the Olotalk dashboard.
2. Go to Assistants and choose Create assistant.
3. Give your assistant a name and its main domain. (You can set a default locale under Advanced configuration, and add more languages later — see Multilingual below.)
4. Submit to create it.

Your assistant now has a unique ID — you’ll see it in the URL and on the assistant settings page (e.g. ast_oltk_7Kd2mQxRv9TbNhLpW3Zsy).

Step 2 — Add your install domains

Before the assistant can run, tell Olotalk which hostnames are allowed to load it.

1. Open your assistant, go to the Install step, and expand Install domains & API key to find Install domains.
2. Add the domain(s) where your snippet will live, such as mycompany.com, www.mycompany.com, or docs.mycompany.com.
3. Save.

Install domains are separate from content ingestion. An assistant can answer from one set of URLs and still be installed on a different hostname if that is the real deployment shape.

Step 3 — Copy your install snippet

On your assistant’s Install step, copy the snippet. It looks like this:

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

Step 4 — Paste it on your site

Paste the snippet just before the closing </body> tag on every page where you want the assistant to appear.

WordPress — use a headers-and-footers plugin, or the wp_footer hook in your theme.

Squarespace — Settings → Advanced → Code Injection, paste into the Footer field.

Webflow — Site settings → Custom code, paste into the Footer Code field.

Shopify — edit layout/theme.liquid and paste before </body>.

Wix, Framer, Ghost, Google Tag Manager and more — see Install on your platform for step-by-step guides.

Any HTML site — paste before </body> in every page template.

That’s it. A chat button appears in the bottom-right corner of your pages (the default — its position is configurable in the dashboard).

Your dashboard confirms it: the Install step’s Install status card shows Seen on yourdomain.com once the snippet loads — and if you pasted it on a domain that isn’t allowed yet, it says so with a one-click fix.

Step 5 — Add your content sources

The agent answers from your website content. To add content:

1. In your assistant’s setup, fill in About context to describe what your site covers (see the Customisation section below — do this first).
2. Open your assistant’s Source step.
3. Enter a URL you want indexed — Olotalk auto-discovers linked pages from the seed URL, so you rarely need to add each one by hand.
4. Click the + to add and ingest it. Processing usually takes a few minutes, depending on how many pages are discovered.

Once ingestion is complete your agent will answer from your actual content — and begin capturing intent signals as visitors interact.

Customisation

You can change the assistant’s appearance, language, and behaviour from the dashboard without touching the embed snippet:

• Theme — light / dark / custom colours
• Welcome message — the first message visitors see
• Languages — see the dedicated section below
• Install domains — restrict which sites the assistant will load on. Add the domain(s) where your embed snippet lives (e.g. mycompany.com). This is separate from ingestion — you can ingest content from any URL, but the assistant only loads on configured install domains.
• Notify email — set an email address on the assistant to receive an alert whenever a lead reaches qualified status. Set it under your assistant’s Base → Advanced configuration → Action policy (the Qualified-lead notify email field).

Multilingual

Olotalk supports any BCP 47 locale out of the box. Operators don’t pre-translate anything — en, fr, and de ship with hand-translated UI strings; every other locale (Vietnamese, Japanese, Arabic, etc.) is LLM-translated by Olotalk on first request and cached.

How the assistant picks a language for each visitor

Steps 3 and 4 are gated by the assistant’s Supported locales: if you ship only French content, an English visitor’s browser preference is ignored and the chrome stays French. Configure this set in your assistant’s setup. After you ingest, Olotalk also auto-derives supportedLocales from the actual content language distribution — Olotalk-detected entries are added (never removed) until you pin them manually.

Adaptive language switch

When a visitor types their first message in a different supported language than the chrome (e.g. types French on an English assistant that supports both), the bot replies in their language and the assistant shows an inline Continue in {language}? · Yes / No prompt. On Yes the entire chrome flips to that language and the choice sticks across reloads.

Auto-translated starter questions

The suggested-question chips on the welcome screen are auto-generated from your content in its primary language. When a visitor switches to a different supported language, the chips are LLM-translated on the fly (cached per-language so subsequent visitors hit zero LLM cost).

About context — the most important setting for answer quality

In your assistant’s setup, under About context, write 1–3 sentences describing what your site and knowledge base cover. For example:

Why it matters: When a visitor asks a question, the assistant generates several semantically diverse search queries before hitting the knowledge base. It uses the About context as domain knowledge to make those queries relevant to your content — without it, the search queries are generic and retrieval quality drops noticeably.

Set a good About context before you ingest content, and re-ingest if you change it substantially.

Verifying it works

Open any page where you pasted the snippet. You should see the Olotalk launcher button. Click it and ask a question — if content is ingested, you’ll get an AI answer grounded in your content. If not yet ingested you’ll see a fallback message.

If the button does not appear, check:

• The snippet is before </body>, not inside <head>.
• Your domain is in the Install domains list in the dashboard.
• The browser console shows no 404 or CORS errors.

Next steps

• Testing in the sandbox — try your real assistant from a local or staging app before you go live, with no billed conversations (preview feature — available when your Install step shows the sandbox card)
• Embed reference — advanced attributes, conversion config, self-hosting, framework guides
• Assistant JS API — open, close, destroy, and re-init from your own code
• Leads & conversions — lead scoring, outcome callback API, HubSpot integration