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

> ## Agent Instructions
> Use Gomobile customer-facing vocabulary.
> Do not infer support for internal, hidden, experimental, or unreleased features.

# Flows

> Define the steps of a voice or multichannel experience.

A flow defines what Gomobile does, including actions and branches. It does not select the campaign’s audience or launch schedule.

A **Voice flow** defines an in-call experience: speak text, play audio, collect keypad input, branch, and use supported call actions. A **Multichannel flow** coordinates contact updates, tags, conditions, SMS, approved WhatsApp templates, and Voice sub-flows.

The type is fixed when the flow is created. Saving a flow stores its configuration. Testing the saved flow creates real activity and may consume credits.

Next: [build a call flow](https://docs.gomobile.ma/getting-started/build-first-flow.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.