← Back to Guides

Getting Started With 0xDoktor: From Signup to Live Widget in Under an Hour

What you will accomplish

By the end of this guide, you will have:

  • A 0xDoktor tenant with at least one knowledge base
  • Your documentation ingested and searchable
  • The chat widget live on your website
  • Confidence thresholds and escalation configured for your use case

Total time: 30–60 minutes depending on the size of your documentation.

Step 1: Create your account

Go to admin.0xdoktor.com and sign up. During signup, you will provide:

  • Your organization name (this becomes your tenant display name)
  • Your email address
  • A password

After signup, you will receive a tenant ID. This is the identifier you will use in the embed script. Keep it accessible.

Step 2: Create your first knowledge base

In the admin dashboard, navigate to Knowledge Bases and click Create new KB.

Give your knowledge base a name that reflects its purpose: for example, "Product Documentation" or "Help Center" or "API Reference". You can create multiple knowledge bases later — for now, start with one.

You will also set the language for this KB. This affects how the content is chunked and how queries are matched.

Step 3: Ingest your documentation

Navigate to your new knowledge base and click Add content.

You have three options:

Upload files: select PDF or Markdown files from your computer. You can upload multiple files at once. Ingestion for a typical documentation page (a few thousand words) takes 5–10 seconds.

Ingest from URL: paste a URL to a public web page. 0xDoktor fetches the page, extracts the main content, and ingests it. Useful for existing online documentation.

Paste text: for short pieces of content (FAQs, policy statements) you can paste the text directly.

Start with your 10–20 most important documentation pages. You can add more later.

After ingestion, you will see each document listed with its chunk count. This tells you how many pieces of content were extracted.

Step 4: Test your knowledge base

Before going live, test the widget against your KB using the built-in test interface in the dashboard. Navigate to Test within your knowledge base.

Type questions that your users would realistically ask. Check:

  • Does the widget return the correct answer?
  • What is the confidence score?
  • Is there important information missing?

If the widget cannot answer a question you expected it to handle, check whether the relevant documentation has been ingested. Add it if missing, then re-test.

Step 5: Configure your widget

Navigate to Widget Settings in the dashboard. Configure:

  • Welcome message: the first message shown when a user opens the widget
  • Placeholder text: the hint text in the input field ("Ask anything about our product...")
  • Colors: primary color and background to match your brand
  • Confidence threshold: the minimum score required before the widget answers without a caveat (recommended starting point: 0.65)
  • Escalation: what happens when confidence is below threshold — show a fallback message, show a contact form, or route to copilot mode

Step 6: Embed the widget on your site

Navigate to Embed in the dashboard. You will see your personalized embed code:

<script
  src="https://widget.0xdoktor.com/v1/widget.js"
  data-tenant="YOUR_TENANT_ID"
  data-kb="YOUR_KB_ID"
  async
></script>

Add this script tag to your HTML, just before the closing </body> tag. The widget will appear on the page immediately after the script loads.

If your site uses a Content Security Policy, add https://widget.0xdoktor.com to your script-src directive.

Step 7: Monitor and improve

After going live, check the admin dashboard regularly in the first week:

  • Conversations: review what users are asking and how the widget is responding
  • Low confidence: flag conversations with low confidence scores — these indicate KB gaps
  • Resolution rate: track the percentage of conversations marked as resolved by users

Use this data to prioritize documentation additions. A well-maintained KB compounds: each gap you fill reduces future escalations.

Next steps

  • Ingest your full documentation corpus
  • Set up copilot mode if you have a support team
  • Create a second knowledge base for a different section of your product or a different language
  • Read the guide on customizing the widget appearance

See 0xDoktor in action — ask anything about this page: