Install

Put ASKLA on your site

Add ASKLA with a script tag after configuring your server, website, allowed origins and indexed content. Approve answers to work without AI, or enable an AI provider. Authorized team members can use the back office for retained conversations.

1. Add the script

Paste this before </body> on every page, so the chat follows visitors from page to page. Your site's key is in the back office under Settings.

<script src="https://askla.chat/widget.js"
  data-key="pk_your_site_key" defer></script>

Running ASKLA on your own server? Load widget.js from your server's address instead. Add your site's exact origin in Settings so ASKLA can check browser requests against the configured list. The embed key is public; never put an admin or publication key in this script.

2. Point ASKLA at your pages

In Content, configure your approved public website origins and index your sitemap, a single HTML page or text. Private and preview paths are excluded. Refresh the sitemap when content changes, manually or through a schedule you manage. Complete successful refreshes can update changed pages and remove missing ones. Failed, empty or partial runs retain existing knowledge. Content changes invalidate saved answer-cache versions; they do not rewrite historical conversations. PDFs and pages requiring JavaScript rendering need separate extraction.

3. Choose how it looks and behaves

In Content → Answers and guided questions, choose Approved answers (AI off), Hybrid, or AI answers. New websites start with AI off; existing websites keep their configured behavior. Select a business type to suggest standard questions and source excerpts. Review each draft before approving it. Add alternative wording and up to four next questions to build a guided flow. Approve exact website origins and included page paths under Website access. Source changes and unpublishing stop old answers from being served.

Set these as attributes on the script tag. Each site's defaults live in Settings.

Attribute	What it does
`data-style`	The chat window: `soft`, `glass`, `minimal` or `welcome`. The site's saved style applies unless this attribute overrides it. The older `sharp` value is still read for compatibility but is not offered as a new admin choice.
`data-launcher`	The button: `pill`, `orb`, `bar` (a question box), `mascot` or `tab` (on the page edge). The saved site setting applies unless overridden.
`data-theme`	The v0.7.2 name, still read: `brand` means Sharp, `soft` means Soft.
`data-scheme`	`light`, `dark` or `auto` to follow the visitor's device.
`data-open`	`true` opens the chat on page load.
`data-storage`	`remember` (renewable 180-day visitor record), `session` (record lasts for the tab) or `none` (no persistent visitor record). Site settings and consent also apply. Message retention on the server is separate.
`data-fonts`	`false` stops ASKLA loading its own font, if your site already serves Manrope.

4. Open ASKLA from your own buttons

Any element with data-one-chat opens the chat. Give it a value to ask that question straight away.

<button data-one-chat="Do you support InvoiceNow?">Ask about InvoiceNow</button>

From a script: INFOCOneChat.open(), INFOCOneChat.open('your question'), INFOCOneChat.talk() for the "talk to a person" route, and INFOCOneChat.close(). Single-page apps call INFOCOneChat.navigate('/new/path') after each route change, so suggestions and analytics follow the page.

ASKLA remembers a returning visitor with one random token in your site's storage. If your banner asks first, pass on the visitor's choice:

// after the visitor chooses in your banner
INFOCOneChat.consent(true)   // may remember the visitor
INFOCOneChat.consent(false)  // clear the remembered visitor record

Where browser storage is available, a "no" is remembered across pages of the same site. A page set to data-storage="session" stays that way even after a "yes". To ask before remembering a visitor, configure data-storage="none" initially and grant permission through the API.

Optional visitor journeys and proactive invitations use a separate tracking choice. Enable assistance for the site and connect INFOCOneChat.trackingConsent(true) or INFOCOneChat.trackingConsent(false) to your visitor-tracking controls. Declining this tracking still allows a visitor to start a chat.

Inside a CMS

Put the script in your public site template's footer. The back office can also be framed or hosted by your CMS when its exact origin is allowed on the ASKLA server. Staff still sign in to ASKLA; this does not automatically share the CMS login. Microsoft sign-in should use top-level navigation.