> ## Documentation Index
> Fetch the complete documentation index at: https://fliqr.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Chain Flows with Go to Flow

> Hand a contact from one Fliqr AI Flow to another while keeping contact context — the key to modular Flow design.

**Go to Flow** transfers the contact into another published Flow and continues there. Use it to keep each Flow focused and under size limits.

## Why modular Flows win

* Stay under the [250 blocks per Flow](/docs/core-concepts/flows/limits) cap
* Reuse shared routines (FAQ, payment, handoff)
* Let different teammates own different Flows
* Ship safer changes by updating one child Flow at a time

## Set up a handoff

<Steps>
  <Step title="Publish the destination Flow">
    The child Flow must be published before the parent can send contacts into it.
  </Step>

  <Step title="Add Go to Flow">
    In the parent Flow, add **Go to Flow** and select the destination.
  </Step>

  <Step title="Pass context via the contact">
    Contact fields and tags persist. Set any fields the child needs before the handoff.
  </Step>

  <Step title="Test the full path">
    Run **Test Flow** from the parent and confirm the child path executes.
  </Step>
</Steps>

## Patterns

| Pattern         | Parent does…               | Child does…                            |
| --------------- | -------------------------- | -------------------------------------- |
| Orchestrator    | Menu + routing Conditions  | Specialized scripts per option         |
| Shared FAQ      | Detect intent              | FAQ Flow reused from many entry points |
| Human handoff   | Qualify + summarize fields | Notify / assign Flow                   |
| Channel adapter | Channel Condition          | Channel-specific message Flow          |

<Note>
  Go to Flow keeps **contact** context. It does not create a separate anonymous session. Design fields as your contract between parent and child.
</Note>

## Avoid loops

Do not create A → B → A cycles without an exit Condition. Loops burn trust and can look like spam.

## Next

<CardGroup cols={2}>
  <Card title="Conditions" icon="code-branch" href="/docs/core-concepts/flows/conditions">
    Decide which child Flow to open.
  </Card>

  <Card title="Best practices" icon="check" href="/docs/core-concepts/flows/best-practices">
    Naming and modularity guidelines.
  </Card>
</CardGroup>