View Categories

Setting Up Your Own Chatbot – Knowledge Base

Knowledge is what your chatbot answers from: your FAQ, policies, prices, product details and anything else customers ask about. Instructions tell your chatbot how to behave; knowledge gives it the facts. Learn more about instructions in Setting Up Your Own Chatbot: Instructions.

Knowledge changes go live right away. Unlike most settings, you do not need to publish them. Make sure a file is accurate and ready before you add it to a chatbot that customers already use.

1. Open the Knowledge page #

Open your project and click Knowledge. When the page is empty, you will see four tiles to get started: Upload a file, Write it here, Share files with customers and Read a web page. Once you have files, they appear in a list, and the Add knowledge button in the top right corner always has every option.

Knowledge Files page with the Add knowledge button and tiles for Upload a file, Write it here, Share files with customers and Read a web page

2. Six ways to add knowledge #

Click Add knowledge to choose how to add it:

Add knowledge menu with Upload a file, Write it here, Share files with customers, Read a web page, Learn about a website and Auto-update from the web
  • Upload a file: PDF, Word, text, CSV, JSON, XML or HTML, up to 50 MB. You can also drop files anywhere on the page.
  • Write it here: a policy, a FAQ, anything you can type or paste.
  • Share files with customers: photos, PDFs and documents your chatbot can send.
  • Read a web page: a FAQ, a price list or reviews. One page, kept as it says.
  • Learn about a website: reads a site’s main pages into one overview.
  • Auto-update from the web: re-reads a URL, or re-runs a web search, on a schedule you choose.

Upload a file #

The best first step is usually your FAQ or policies. Click Upload a file and pick a file, or drag it onto the page. Use clear file names, and upload documents with real text, not scanned images.

Write it here #

No file? Write it on the platform instead.

Write a knowledge file dialog with Name, When should your chatbot use this, a text editor and Start with a FAQ layout
  1. Name: for example “Returns policy”.
  2. When should your chatbot use this? (optional): for example “When a customer asks about returns or refunds”.
  3. What your chatbot should know: type or paste the content. Click Start with a FAQ layout for a ready-made question and answer structure.
  4. Put each question or topic under a heading. Tables and pictures are not kept.
  5. Click Save.

Share files with customers #

Use this when you want your chatbot to send files to customers, like a product photo, a brochure or a menu. Your chatbot shares the link and what you write about each file. It does not read the file itself, so put anything it should answer from in a regular knowledge file.

  1. Give the list a Name (for example “Products”) and, if you like, a hint for When should your chatbot use this?, such as “When a customer asks what a product looks like or what it costs”.
  2. Under Files, click Add files or drop files in the box. Click Choose one already uploaded to reuse a file from your project.
  3. Add a name and short details for each file, then click Save.

Anything listed here can be shared with your visitors, so only add files that are meant to be public.

Read a web page #

Enter the Page address and click Read page. NOEM turns that one page into a knowledge file, kept as it says. Click Only part of the page? to describe which part to keep.

Learn about a website #

Enter your Website and click Read website. NOEM reads the site’s main pages and writes one overview. Click Only part of the website? to say what to keep and how to shape it, for example “Only the services and prices, skip the blog”. It never adds anything the pages do not say.

Auto-update from the web #

For content that changes, like prices, opening hours or news, set up an automatic update. NOEM re-reads the source on a schedule and keeps the knowledge file current.

Automatic Updates dialog with name, URL or Internet Search source, When to use hint and update schedule
  • Name: a name for the source.
  • Source: choose Url and paste a page address, or choose Internet Search to re-run a web search. Click Test to check what NOEM gets back.
  • To use a Google Doc or Sheet, publish it to the web first (in Google: File, Share, Publish to web) and paste that link.
  • When to use (optional): describe the situation, for example “When the customer asks about opening hours, holiday closures, or where to park”. Leave it blank and the AI only sees the file name.
  • Update: Manually, Hourly, Daily, Weekly or Monthly. Pages that rarely change work well on Weekly or Monthly, which also uses far fewer tokens than Hourly.

Automatic updates may depend on your plan. For more details, see Automatic Updates: Web Content for Your Bot.

3. Your knowledge list #

Every file appears in one list, including web pages and automatic updates. Each row reads File | When your chatbot uses it.

  • Edit the hint in place. Click the “When your chatbot uses it” text to change it. A missing hint is highlighted, so you can spot files the chatbot may not know when to use.
  • Automatic updates sit with their file. A source and the file it creates are one row. Deleting the row removes both.
  • To replace a document, delete the old row and add the new version, so your chatbot never reads two versions.

4. How your chatbot uses knowledge #

Your chatbot looks up the relevant parts of your knowledge when a question needs them, guided by each file’s name and its “When your chatbot uses it” hint. It does not memorize whole documents, and it only uses a file when it fits the question. For example, if a visitor asks “What are the steps of your onboarding?”, the chatbot pulls that section from your onboarding guide and answers with it.

When NOEM builds a new chatbot for an online store, it adds a catalog knowledge file so the chatbot knows your product names. When you change your chatbot with Vibe Edit, it checks your knowledge files too, and it can point you here when a change needs new information.

5. Best practices #

  • Write a clear “When your chatbot uses it” hint for every file. Describe the situation, not the steps.
  • Keep one current version of each document. Remove old ones.
  • Use headings and short sections. Structured documents give better answers.
  • Use files with real text. Scanned images without text cannot be read.
  • Do not add sensitive or private data your chatbot should never share.
  • Test after adding knowledge: ask your chatbot a few questions the new file should answer.