AI Chatbot · Enterprise

Answer customers instantly — straight from your docs

Most support questions have already been answered in your documentation. The Scitor chatbot puts those answers one chat bubble away: a themeable widget you add to any website with a single script tag. When the docs don't have the answer, the visitor escalates to a real ticket — transcript included.

Get started Read the docs

One script tag. That's the setup.

No SDK, no build step, no iframe gymnastics. Enable the chatbot in your scitor.yaml, paste one line into your site, done.

index.html 
<script
  src="https://api.scitor.io/widget/chat.js"
  data-form="YOUR_FORM_ID"
  async
></script>

Localizable (English, Dutch, German, French — every string overridable), themeable (your color, left or right corner), and isolated in a shadow DOM so it never fights your site's CSS.

How it works

Your documentation is the single source of truth — for your docs site, your agents' draft replies, and now your chatbot. Drop PDFs into the docs folder and they're answerable too.

  1. 1

    A visitor asks a question

    Your customer clicks the chat bubble and types "How do I reset my router password?" — in any language.

  2. 2

    Scitor searches your docs

    The question is matched against your knowledge base — the same Markdown docs (and PDFs) that power your hosted documentation site.

  3. 3

    AI answers, with sources

    A short answer is generated strictly from the matching articles, with links to the source pages. No docs match? The bot says so honestly.

  4. 4

    Escalation when it matters

    One click opens a contact form. The submission becomes a GitHub Issue or Discussion with the full chat transcript attached, so your team has context.

A chatbot you can put in front of customers

Public AI widgets attract misuse. This one is built for it.

Answers only from your docs

The bot is grounded in your knowledge base. Off-topic questions — recipes, homework, other products — get a polite refusal and an escalation offer, never a made-up answer.

Prompt-injection resistant

"Ignore your instructions" doesn't work. Visitor messages and document content are treated as data, never as commands.

Rate limited by design

Per-visitor and per-site limits keep abuse and costs in check. When limits are reached, the widget gracefully falls back to the contact form.

Private by default

Conversations are never stored on our servers. The transcript lives in the visitor's browser and is only saved if they choose to escalate to a ticket.

Full details on data handling are on our AI transparency page.

Deflect the easy questions. Catch the hard ones.

The AI chatbot is included in the Enterprise plan, together with the contact database, customer history, and unlimited outbound email.

See pricing Read the documentation