Questions about ASKLA

From the content you index: a sitemap, a single public page, a crawl of your site or text you paste in. Answers link to the pages they came from as numbered sources, so visitors can open and check them.

Run a sitemap refresh in the back office, or let your CMS send changed pages. A complete refresh updates changed pages and removes pages that are no longer listed. If a page fails or the sitemap is over the limit, nothing is removed and existing knowledge stays. ASKLA does not refresh on a schedule by itself.

If ASKLA finds no source that supports an answer, or the answer fails its check, it says so instead of guessing. A provider failure shows an unavailable message. Team contact options remain available.

Knowledge gaps lists refused questions, answers rated thumbs-down and chats your team marked, grouped by topic. Your team can create a content task from a conversation to follow up.

Before a visitor's question reaches the AI or is saved, ASKLA replaces detected email addresses, phone numbers, Singapore NRIC/FIN numbers, payment-card numbers and IBANs. Detection is pattern-based and can miss things; names and addresses are not reliably detected. Your team's replies are not redacted.

Yes. New sites start in Approved answers · AI off. Approve exact excerpts from indexed pages, add other ways of asking and link next questions into a guided conversation. Answering visitors in this mode makes no model calls. Business question templates suggest drafts for review and flag missing content; they do not invent answers. When a source page changes, its approved answers stop until they are reviewed again.

Three: Approved answers · AI off; Approved answers first · optional AI fallback; and AI answers. In every mode an exact approved match is shown first and calls no model.

AI is optional. The server supports Anthropic and OpenAI for answers, plus a mock mode for testing. Claude defaults to Haiku 5.5. Each site can store its own Anthropic key and choose Opus 5.5, Sonnet 5.5 or Haiku 5.5. PostgreSQL keyword search needs no embedding API; optional semantic search uses the configured embedding provider.

It searches your indexed content, drafts an answer with references to passages, then a separate check compares each statement with its source. Statements without a valid citation or a passing check are withheld. AI checks can still miss mistakes, so important details should be confirmed in the cited sources.

Yes. In What ASKLA may state, set Prices, Legal and tax facts, and Timelines and durations each to Quote published values or Never state, and add up to 10 rules of your own. The rules apply to AI answers. An approved answer stating a price or legal or tax figure set to Never state is not shown.

Yes. Version history keeps the last 50 saved versions of a site's settings, with who changed what and when. Owners can restore an earlier version; webhook addresses, lead emails, lead alert settings and the webhook secret are not changed by a restore.

Exact values ASKLA may cite: prices, hours, response times, legal and tax values and contact details. Each has an official source link, a last-checked date, optional start and end dates and a version history. When ASKLA answers with AI, a matching fact is used ahead of page text and links to its source. Approved answers never quote a fact, and Approved answers · AI off quotes none; an out-of-date legal or tax fact can still hold back an approved answer that states its figure.

A fact stays usable for a period you set after it was last checked, from 7 to 730 days (365 by default); legal and tax values for at most 180. An out-of-date, expired or disputed fact is not used. For a legal or tax value, such as a GST or CPF rate you have added, ASKLA does not quote the figure in any mode: it says the value may be out of date, or that its values disagree, and links the official source, or offers a person. ASKLA has no built-in rates.

When live chat is on and someone is available, your team can join a waiting chat or take over one ASKLA is answering, in the same conversation, and hand it back to ASKLA. When nobody is available, visitors can leave a contact request.

With "Show whether the team is available" turned on (it is off by default), the chat header reads Team available, Leave a message, or the assistant's name (with AI, unless only approved answers are used) when only ASKLA is answering. The words carry the state, not just the coloured dot.

Yes. Set opening hours by day and time zone, and add up to 50 closures of up to 31 days each. During a closure visitors are told the team is away and when it is back, and no chat is assigned.

A time limit for a person to reply, counted from the moment a visitor asks for a person until a team member joins or replies. New sites start at 5 minutes; you can choose 30 seconds to 5 minutes, or off. When it is missed, ASKLA emails the addresses under Email each request to and posts to the live-chat webhook, once per chat and at most 20 alerts an hour.

Yes, when an owner turns it on. ASKLA emails the addresses under Email each request to when a visitor joins the queue, at most 20 an hour, with a link to the waiting chat. It never includes what the visitor wrote, their contact details or IP address, and it is cancelled if someone claims the chat first.

Yes. Create up to 20 departments; with two or more, visitors choose a team. Assignment can be Manual claim, Round robin or Least busy, and each person can have a chat limit and their own schedule. Your team can transfer a chat from the web admin or a phone, only to a teammate who can take a chat now, and the activity log records each transfer.

Yes. Internal notes sit in the conversation marked "team only". Visitors never see them, and they are not sent to the AI, webhooks, CRM or email. Owners can delete a note; the activity log records the deletion without the text.

Yes. The mobile web admin runs in a phone's browser. Your team can claim chats, reply with quick replies, see typing and when a message is seen, transfer, request contact details, hand back to ASKLA, close chats and add notes. They can see who the visitor is and their earlier chats, read past conversations, work leads, set their availability and chat photo, and open any other setting through Manage in web admin. Sign-in and site access are required.

Yes. Owners keep a library of quick replies; typing / in the reply box inserts one into the draft. Automatic welcomes are off until an owner enables them. They are labelled as ASKLA automation, wait at least 10 seconds and reach only visitors who allowed site assistance.

A visitor fills in the contact form and must agree to its consent statement. ASKLA stores the exact consent wording and the time with the details they submitted. Owners can ask for company, need and follow-up in the form or one at a time in the chat; the answers reach the team only when the visitor sends the form with consent.

To your team in the admin and, when set up, by email (SMTP or Microsoft 365) and to a webhook, signed when you set a webhook secret. Failed email or webhook deliveries are retried after 1, 5 and 30 minutes. A CRM can receive them through a signed HTTPS connector, with up to three attempts.

Lead details show a Singapore number's Do Not Call status in words, such as "not checked — only needed before phone marketing". ASKLA does not look numbers up on the register itself. A contact request is a service contact, so the callback a visitor asked for is never blocked. ASKLA does not send phone or SMS marketing.

Yes. Owners open Privacy request in Leads, find a person by email or phone and see counts only. They can download an export or erase the data after typing ERASE. Copies already delivered by email, webhook or CRM, content tasks and backups are not deleted.

Chats are cleaned up after 30 days by default, by a job that runs about every six hours. Contact requests are kept for two years (730 days) unless a site chooses 30 to 3,650 days. Returning-visitor records are removed after 180 days without a visit.

Yes. Owners can read the activity log: who changed what and when, across settings, knowledge, facts, team, keys, notes, chat transfers and privacy requests. It records setting names and counts, not values, secrets or visitors' contact details.

Depending on your settings and the visitor's storage choice, a random token, conversation identifier and expiry, plus interface preferences. Remembered visitor records renew for up to 180 days; conversation retention is separate. Message text is fetched from the server, not saved in browser storage. Your site can allow or clear remembered chats through ASKLA's consent API.

Add one script tag with your site key before </body> on each page. Optional attributes set the style, launcher, light or dark scheme and storage. The install guide lists them all.

The first script stays under 15 KB compressed, checked on every release. The chat panel, contact form and optional site assistance are separate files; the contact form loads only when it is needed.

Choose a Pill, Orb, Ask bar, Mascot or Side tab launcher; Soft, Glass, Minimal or Welcome styles; ASKLA original, Microsoft Fluent, Google Material, Apple Glass or IBM Carbon presets; and a floating window or slide-out panel, with your brand colour. On phones the chat uses the full screen. Owners can also use Match my website in Chat settings › Look and launcher: ASKLA reads your public homepage (respecting robots.txt) and the stylesheets and icon it links, then suggests a colour, light or dark, style, preset and launcher. Nothing changes until you apply the suggestions and save.

Yes. Each site has a full-page chat at its own ASKLA address for links, emails and QR codes. A site can turn it off.

Yes. ASKLA runs with Docker Compose and PostgreSQL. Talk to INFOC about managed hosting.

Contact INFOC to discuss setup, hosting options and a quote.