> ## 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.

# How Gomobile works

> Learn how contacts, audiences, flows, campaigns, runs, and calls work together.

Most Gomobile workflows connect customer data to an automated experience, then produce activity that your team can investigate.

```mermaid theme={null}
flowchart TD
    Contacts[Contacts] --> Audience[Audience]
    Audience --> Campaign[Campaign]
    Flow[Saved flow] --> Campaign
    Campaign --> Run[Run: flow execution]
    Run --> Activity[Calls, messages, or contact updates]
    Activity --> Results[Activity and outcomes]
    Results --> Report[Campaign report]
```

A campaign is the outreach program; a run is a flow execution. These docs use **Campaign** and **Run** to match the Gomobile interface. The flow is saved configuration, while the run records what happened when it executed.

See the [core concepts](https://docs.gomobile.ma/learn/concepts/organizations.md) and [architecture overview](https://docs.gomobile.ma/learn/architecture.md) for more detail.

## Core objects

| Object | What it represents | Example |
| - | - | - |
| Contact | One customer identified primarily by phone number, with standard fields and optional custom attributes | Amina El Amrani in Casablanca |
| Audience | The contacts eligible for a campaign | Customers with a renewal date in the next 30 days |
| Flow | The automation Gomobile runs | Confirm an appointment and update the contact's status |
| Campaign | The audience, flow, schedule, channel resources, calling policy, and lifecycle for an outreach operation | October appointment confirmations |
| Run | One execution of a flow for a particular context | The automation created for Amina during the campaign |
| Call | A placed or answered voice interaction associated with a run when voice is involved | The outbound call to Amina |

## Static and live audiences

A **static audience** changes only when someone adds or removes contacts. It works well for a reviewed list, event attendees, or a one-time operational batch.

A **live audience** uses rules. Contacts enter and leave automatically as their data begins or stops matching those rules. Use it for continuously changing segments, such as customers whose renewal date is approaching.

You choose the audience type during creation and cannot switch the type later.

## Voice and multichannel flows

A **Voice flow** defines what happens during a call. The visual builder can play audio, say text, collect keypad input, record a segment, transfer or end the call, branch, connect to an AI agent, update the contact, apply a tag, or send a follow-up message.

A **Multichannel flow** coordinates actions outside a single call. It can branch, update contacts, apply tags, send SMS, send approved WhatsApp templates, and invoke a Voice flow as a sub-flow.

> [!NOTE]
>
> A campaign, flow test, API request, or inbound binding can start a run. Voice flows can connect to an active AI agent. Multichannel flows can invoke Voice sub-flows; Voice flows cannot invoke sub-flows.

## Runs, calls, tries, and outcomes

* A **run** records how a flow progressed for one execution context.
* A **call** records a voice interaction and its timeline, result, and associated media when available.
* A **try** is one campaign attempt to reach a contact. Retries create additional tries.
* An **outcome** summarizes what ultimately happened for the contact or interaction.

Use the campaign report to understand the operation as a whole, Runs to investigate automation paths, and Calls to investigate voice details.

## Inbound routing

An **inbound binding** routes an available phone number to one AI agent or one Voice flow. Binding history separates reporting periods when a number's destination changes.

## Credits

A credit is Gomobile's prepaid usage unit. It is not a currency. Eligible users can see the organization balance, while calls, runs, and campaigns show applicable usage and cost breakdowns.

> **[Tour the workspace](https://docs.gomobile.ma/getting-started/workspace-tour.md)**
>
> Find each area in the Gomobile navigation.

> **[Import contacts](https://docs.gomobile.ma/getting-started/import-contacts.md)**
>
> Start preparing customer data for an audience.

## Channels, agents, and workspace resources

* [Voice, SMS, and multichannel](https://docs.gomobile.ma/learn/concepts/channels.md): choose channel resources and flow types.
* [WhatsApp and templates](https://docs.gomobile.ma/learn/concepts/whatsapp.md): understand connection state, approval, and sends.
* [AI voice agents](https://docs.gomobile.ma/learn/concepts/agents.md): distinguish configuration, testing, and publication.
* [Knowledge bases](https://docs.gomobile.ma/learn/concepts/knowledge-bases.md): prepare documents for compatible agents.
* [Inbound routing](https://docs.gomobile.ma/learn/concepts/inbound.md): connect incoming calls to a flow or agent.
* [Audio and pronunciation dictionaries](https://docs.gomobile.ma/learn/concepts/audio.md): prepare reusable voice resources.
* [Calls, outcomes, and reports](https://docs.gomobile.ma/learn/concepts/reporting.md): investigate activity at the right level.
* [Credits and usage](https://docs.gomobile.ma/learn/concepts/credits.md): review balance and usage before testing.
* [API keys, access, and security](https://docs.gomobile.ma/learn/concepts/access.md): understand credentials and workspace access.


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