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. Action nodes

Collect User Data

The Collect User Data node gathers and stores specific information from users during conversations.

PreviousAction nodesNextQuick Reply

Last updated 2 months ago

Was this helpful?

It provides structured data collection with validation and storage capabilities.

Setting up data collection:

  1. Define the question to ask the user

  2. Choose where to store the collected data (this is a variable that can be used later on in LLM Response node's instruction).

  3. Select appropriate input type for validation

  4. Configure "Skip if value exists" to avoid repetition

Example: Collect user's email if they requested to be contacted by a human team member:

Question: "What's your email address?"
Store in: user_email
Input type: Email
Skip if exists: Enabled

Common use cases:

  • Contact information

  • Order references

  • User preferences

  • Account details

  • Support ticket info

  • Survey responses

Important considerations:

  • Use clear, specific questions

  • Consider privacy implications

  • Check existing values before asking

  • Verify data storage

  • Plan error handling

Example of Collect User Data