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
  2. Conversation Flows
  3. Nodes
  4. Logic nodes

If/Else Router

PreviousRoute by ProfileNextIntent Matcher

Last updated 2 months ago

Was this helpful?

The If/Else Router node enables your flow to branch based on different conditions. You can string together multiple conditions to handle various scenarios, with each condition creating a new path in the conversation.

Setting up conditional routing:

  1. Select condition type (Signal, Language, or other available types)

  2. Configure the value to check for that condition

  3. Combine multiple conditions using "+ Add condition" (by If or And operator)

  4. Create specific cases for each scenario

  5. Set up an "Else" path for when no conditions match

Example:

Common use cases:

  • Check conversation state signals (start, interrupt, end)

  • Route based on user's language

  • Handle different user inputs

  • Process system events

  • Manage conversation flow based on multiple conditions

Important considerations:

  • Each condition creates a new path - keep them organized (e.g. by moving them to separate flows)

  • Conditions are checked in order, from top to bottom

  • The Else path handles any case not covered by specific conditions

  • You can remove individual conditions using "Remove case"

  • Multiple conditions can be combined for complex routing

  • Test all paths to ensure proper handling

Example of If/Else Router use