> For the complete documentation index, see [llms.txt](https://docs.virbe.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.virbe.ai/dashboard-management/conversation-flows/nodes/flow-control-nodes/go-to-flow.md).

# Go to Flow

**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:

<figure><img src="/files/qbHuNcJ4Mp8nWLBL6huF" alt=""><figcaption></figcaption></figure>

```
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

{% hint style="info" %}
**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
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.virbe.ai/dashboard-management/conversation-flows/nodes/flow-control-nodes/go-to-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.