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
  1. Dashboard Management

Dashboard Architecture

A dashboard represents a single virtual being use case. This one-to-one relationship between dashboards and use cases is a fundamental design principle that helps maintain clarity and purpose.

PreviousAzure-hosted deploymentNextOverview

Last updated 6 months ago

Was this helpful?

CtrlK

Was this helpful?

A dashboard consists of the following core components:

  1. Overview

    • Dashboard Status

    • Subscription Information

    • Recent Issues

    • Profiles List & Status

      Overview
  2. Profiles

    1. Configure channel-specific settings

    2. Customize interface and behavior

    3. Manage deployment

      Profile
  3. Configurations

    • Speech-to-Text Setup

    • Text-to-Speech Setup

    • AI Models Integration

    • External conversational AI engines

    Configurations
  4. Personas

    • Avatar Management

    • Voice and Language Configuration

    • Personality Settings

      Personas
  5. Knowledge Base

    • Manage content to be used when generating responses

    • Collections and documents management

  6. Data Tables

    • Store structured information

    • Manage data in real-time

    • Ensure data accuracy

      Data tables
  7. Conversation Flows

    • Design conversational flows

    • Configure response logic

    • Set up integrations

      Conversation flows
  8. Conversations

    • Conversation history

    • Human hand-over

      Conversation log with human handover
  9. Issues

    • Error Monitoring

    • System Notifications

Each component works in harmony to create a cohesive virtual being experience, ensuring consistent behavior and responses across all deployment channels while maintaining the specific requirements of each implementation context.