Go to Flow

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

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