# Conversation Flows

They determine how your virtual being understands inputs, processes information, and generates responses. Think of flows as the pathways your virtual being's "thoughts" follow during conversations.

## Core Concepts

### Flow Triggers

Every conversation flow begins with an input, which can come from multiple sources:

* User's text or voice input
* System signals (like conversation start/end)
* External integrations
* Interface interactions (buttons, cards)
* Custom events

<figure><img src="/files/SE4MFQDTI4P09MdGXu9f" alt="" width="563"><figcaption><p>Start of Main flow: all relevant events should be connected with follow-up nodes in order to</p></figcaption></figure>

**The entry point of a flow activates each time any of these inputs occurs,** making your virtual being responsive to all types of interactions.&#x20;

{% hint style="info" %}
**All relevant events branching out** of the Start node should be connected with follow-up nodes in order to be handled predictably.
{% endhint %}

### Conversation Context

Your virtual being maintains context throughout the conversation automatically. This means it remembers:

* Previous messages
* User information
* Conversation history
* Current conversation state

**This context is automatically included in LLM prompts,** enabling coherent, contextual conversations without additional programming.

### Nodes

Conversation flows is built from blocks that we call "Nodes". Their functionality ranges from simply delivering predefined text response, through LLM responses, complex conditional logic to external integrations or webhooks.

<figure><img src="/files/IM4BMu3j6yx1FNO9U3xc" alt=""><figcaption><p>Conversational flow is built with nodes of different types</p></figcaption></figure>

***

Read more about basic concepts of building a conversational flow:

{% content-ref url="/pages/DIfQvGbrkHyrk8Ejr1yj" %}
[Getting started with Conversation Flows](/dashboard-management/conversation-flows/getting-started-with-conversation-flows.md)
{% endcontent-ref %}

Or learn more on how and when to use each node type:

{% content-ref url="/pages/PR6yBx27HTy9LPR8rEXO" %}
[Nodes](/dashboard-management/conversation-flows/nodes.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.virbe.ai/dashboard-management/conversation-flows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.