> For the complete documentation index, see [llms.txt](https://docs.voipnumber.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voipnumber.net/components/call-flow.md).

# Call Flow

{% hint style="info" %}
Should it just connect somewhere straight a way❓ Or maybe a music/audio announcement should be played first? Speech from text? Voicemail?

💡 Call Flow covers all of that
{% endhint %}

Setup your Call Flows at [app.voipnumber.net/callflows](https://app.voipnumber.net/aiagents)

You create a Call Flow in  [Call Flow Builder](/features/call-flow-builder.md) at [app.voipnumber.net/callflowbuilder](https://app.voipnumber.net/callflowbuilder) by dragging and dropping actions onto the Call Flow design pane

<figure><img src="/files/wOG5VaaN3hFWfrwNMCWd" alt=""><figcaption><p>Call Flow with TTS (Text to Speech), audio playback and bridge (call transfer)</p></figcaption></figure>

You probably remember that when you dial a [Connection](/components/connection.md) on [VoIP Number](https://voipnumber.gitbook.io/voip-number/), the call is executed according to the `Inbound Action` set on a Connection. This Inbound Action is either:

* `default` (bridge)
* `Call Flow`

By default new Connection has `Inbound Action` set to `default`  (bridge). That means that by default a call is sent to the `SIP` device registered on [VoIP Number](https://app.voipnumber.net/dashboard) to the Connection's SIP credentials. When you attach a Call Flow to a Connection in the web app, this `Inbound Action` changes to `Call Flow`, and your Call Flow is executed when the call is sent through our platform

If your Call Flow contains a single bridge action that bridges to dialled Connection, then your Call Flow is equivalent to `default` Inbound Action (bridge), they in effect connect a call to dialled extension&#x20;

But your [Call Flow](https://app.voipnumber.net/callflows) is more flexible 😎&#x20;

* You can add as many actions as you want
* You can connect them in any way you can only think about (as long as it makes a valid connection of course 🙂)&#x20;
* You can easily change what happens to a call 🥳 🚀 &#x20;

And if you need to change how the call is executed or what is played to the caller just edit your Call Flow and click `SAVE`

Keep reading to learn more about  [Call Flow Builder](/features/call-flow-builder.md)

<figure><img src="/files/fMNz6hG4akGPZyh9HXCX" alt=""><figcaption><p>A Call Flow with advanced structure: greeting message playback, (DTMF) digits collection and processing into TTS and voicemail</p></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 dynamically by asking a question.

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

```
GET https://docs.voipnumber.net/components/call-flow.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.