> ## 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 objects connect

> See how customer-facing Gomobile objects connect.

This overview shows the objects you configure and the activity you inspect.

```mermaid theme={null}
flowchart TD
    Contacts[Contacts] --> Audience[Audience]
    Audience --> Campaign[Campaign]
    Flow[Saved flow] --> Campaign
    Campaign --> Run[Run: flow execution]
    Run --> Call[Call when voice is involved]
    Run --> Message[SMS or approved WhatsApp template]
    Run --> Update[Contact updates and tags]
    Call --> Results[Activity and outcomes]
    Message --> Results
    Update --> Results
    Results --> Report[Campaign report]
```

The campaign connects the audience to a saved flow. The run records an execution of that flow. Channel activity depends on the steps reached; every run does not create both a call and a message.

## Other entry points

A flow test or supported API request can start a run without launching a campaign. An inbound binding routes a phone number to a Voice flow or AI agent.

```mermaid theme={null}
flowchart LR
    Caller[Incoming call] --> Number[Bound phone number]
    Number --> Destination[Voice flow or AI agent]
    Destination --> Activity[Call activity and available results]
```

See [How Gomobile works](https://docs.gomobile.ma/product/how-gomobile-works.md) for the object definitions and [campaign lifecycle](https://docs.gomobile.ma/product/campaign-lifecycle.md) for enrollment and scheduling.


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