Virbe Documentation
  • Say hi to Virtual Beings!
  • Getting started
    • Introduction to Virbe platform
      • Virbe-hosted launch
      • Azure-hosted deployment
  • Dashboard Management
    • Dashboard Architecture
    • Overview
    • Profiles
      • General
      • Language
      • Persona
      • Settings
        • Web widget profile settings
        • Metahuman kiosk profile settings
      • Deployment
        • Web widget deployment
        • Metahuman kiosk deployment
    • Configurations
      • Speech-to-Text
      • Text-to-Speech
      • AI Models
      • Conversational Engines
    • Personas
    • Knowledge Base
      • Best Practices for Knowledge Base Content
    • Data tables
    • Conversation Flows
      • Getting started with Conversation Flows
      • Managing nodes
      • Nodes
        • Logic nodes
          • Route by Profile
          • If/Else Router
          • Intent Matcher
        • Flow control nodes
          • Go to Flow
          • Checkpoint
        • Response nodes
          • Text
          • LLM Response
          • Call ConvAI
          • Behavior
        • Action nodes
          • Collect User Data
          • Quick Reply
          • Cards from Table
        • Context nodes
          • Find Record(s)
        • Integration nodes
          • Call Webhook
          • Custom Action
      • Troubleshooting Conversation Flows
  • Touchpoints
    • Kiosk Apps
      • Metahuman Kiosk
        • Hardware setup
          • Recommended setup
          • Computer
          • Screen
          • Microphones
          • IoT
          • Peripherals
          • Operating System
            • Windows
              • Login & power management
              • Other
              • OpenHab
            • Mac
            • Remote Access
        • Customer Experience
          • VAD & press-to-talk
          • Microphone settings
          • Avatars
    • Web Integration
Powered by GitBook
On this page

Was this helpful?

  1. Dashboard Management

Knowledge Base

Last updated 2 months ago

Was this helpful?

In Knowledge Base you can provide the virtual being with all the important information and content that is specific for your use case and needs. The virtual being will use this content to provide the most truthful and relevant responses based on the user's input as well as the context of the conversation.

(If you're into AI tech like we are, you might find plenty of online resources regarding the core philosophy behind creating functional knowledge bases under the term "RAG", or Retrieval Augmented Generation, for example .

Building your Knowledge Base

Knowledge Base in AI Editor is made of Collections and Docs.

Collection is a group of Docs, most likely related to each other. This organization will allow you to manage the content easily by dividing your information into smaller content pieces, Docs, grouped into corresponding categories – Collections.

Document, Doc for short, is a content item in the Collection that contains text as well as images. The text field accepts up to 10,000 characters. When adding images, there's an additional text field for the description of the image.

It's important to include information on what is depicted in the image – this will allow the virtual being to select the most relevant images during the conversation and display them contextually.


by LangChain here)
Knowledge organized into Collections and Documents
Example: A Document in the "Snowboards" collection
Adding an image to a Document