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. Flow control nodes

Go to Flow

The Go To Flow node enables modular conversation design by connecting different flows together.

PreviousFlow control nodesNextCheckpoint

Last updated 3 months ago

Was this helpful?

Using separate flows for distinct conversation paths keeps your flows organized, maintainable, and reusable – a highly recommended practice for any non-trivial virtual being implementation.

Setting up flow transitions:

  1. Create a dedicated flow for specific conversation paths

  2. Use Go To Flow node to connect to that flow

  3. Select the target flow from your flows list

  4. Flow returns to original path when completed

Example: Rather than handling technical support queries in your main flow, create a dedicated "Technical support" flow:

Main Flow:
- Check if user has technical issues
- Go To Flow: Technical support
- Continue with personalized interaction

Technical support Flow:
- Collect device details
- Get issue description
- Provide troubleshooting steps
- If unresolved: collect contact info
- Return to main flow

Common use cases:

  • Authentication flows

  • Data collection sequences

  • Common response patterns

  • Multi-step processes

  • Reusable conversation segments

Important considerations:

  • Break complex conversations into logical modules

  • Reuse common flows across different paths

  • Keep flows focused on specific tasks

  • Keep main flow clean and high-level

  • Name flows clearly and descriptively

  • Test flow transitions thoroughly

  • Maintain clear entry and exit points