​

Intake Form Nodes

​

Overview

• Structured data collection within natural conversations
• Dynamic form fields based on caller responses
• Built-in validation and error handling
• Integration with CRM and database systems
• Multi-step form progression with conditional logic
• Automatic data formatting and organization

​

When to Use Intake Form Nodes

​

Structured Information Collection

• Collect complete customer profiles and preferences
• Gather contact information with verification
• Document service requirements and specifications
• Capture billing and payment information

• Document detailed problem descriptions
• Collect relevant background information
• Gather environmental or contextual details
• Record preferred contact and resolution methods

• Capture comprehensive appointment requirements
• Collect health or service history information
• Document special needs or accommodations
• Record insurance or payment information

​

Business Process Integration

• Systematically collect qualification criteria
• Document budget, timeline, and decision-making process
• Capture competitive landscape information
• Record communication and follow-up preferences

• Structure issue reporting and categorization
• Collect system or product information
• Document troubleshooting steps already attempted
• Capture urgency and impact assessments

• Collect required regulatory information
• Document consent and authorization details
• Capture identity verification data
• Record compliance-specific disclosures

​

Integration Patterns

​

With Conversation Nodes

1. Conversation Node: Explain information needed
2. Intake Form Node: Collect structured data
3. Conversation Node: Confirm and summarize information
4. Logic Split: Route based on collected information

Conversation: "I'd like to get some information to help us serve you better. This will just take a couple of minutes."
�
Intake Form: Collect required information
�
Conversation: "Thank you for that information. Based on what you've told me..."

​

With Function Nodes

1. Intake Form Node: Collect customer information
2. Function Node: Validate against existing systems
3. Logic Split: New vs existing customer handling
4. Function Node: Create or update customer record
5. Conversation Node: Confirm next steps

1. Intake Form Node: Collect service request details
2. Function Node: Check inventory/availability
3. Function Node: Calculate pricing
4. Conversation Node: Present options
5. Function Node: Process selection

​

With Logic Split Nodes

1. Intake Form Node: Initial qualification questions
2. Logic Split Node: Route based on responses
   - High priority � Immediate processing
   - Standard � Normal workflow
   - Low priority � Self-service options
3. Additional form nodes as needed per path

​

Best Practices

​

Form Design Principles

• Collect only necessary information for immediate need
• Break long forms into logical sections
• Use progressive disclosure for complex requirements
• Prioritize essential fields for workflow decisions

• Introduce forms with clear context and purpose
• Use conversational prompts rather than field labels
• Provide examples for complex or ambiguous fields
• Confirm information naturally within the conversation

// Good: Conversational and clear
"What's the best phone number for us to reach you if we get disconnected?"

// Poor: Formal and confusing
"Please provide your primary contact telephone number for our records."