> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/setting-up-flow-builder/steps/route-to-chatbot.md).

# Route to Chatbot

In certain situations, you may need to route a user to multiple flows. For example, when a payment is collected, you might want to route the user to another flow where you can gather detailed requirements and pass them to your team for further action. When routing from one flow to another, it is possible to pass all the data collected from the current flow to the destination flow in order to maintain the context of the conversation.

By seamlessly transitioning the user from one flow to another, you can ensure a smooth and personalized experience. The data collected in the current flow can be transferred to the destination flow, allowing for continuity and enabling your team to have access to the relevant information.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXelCIAJOwlDI3rpK9GiQ75ZWuTCUQnGpLtLTgZJgiree77m3U_z_Sty26ebc4z3CWjsLjOD1cERYZEgEmn5eLE8uXsR_FrR7rV3xHuZ9wpIaaaAOUsyk1Mp1utND4ZmLSX3BYWr0kiTcUSqQgqpHUlls0eT?key=1qqFXlcKQC4QffFFDupvgw" alt=""><figcaption></figcaption></figure>

You can select the channel, select the flow and select the attributes and insert all the values that need to be passed to the other flow for maintaining the context of the conversation, the values passed from here to another flow will be available under attributes with named **"Routed Flow Data"** as shown below&#x20;

<figure><img src="https://3382165395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LlJChpzcxtwOYGcBd1q%2Fuploads%2FeiEH4WVJXnLBDLmROaKa%2Fimage.png?alt=media&amp;token=469f0fb1-01cb-4979-83af-67046154dad5" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pickyassist.com/setting-up-guide/setting-up-flow-builder/steps/route-to-chatbot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.