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

# Inbound routing

> Understand how a phone number routes callers to a flow or agent.

An inbound binding connects an available phone number to one Voice flow or one AI agent. It defines where an incoming call goes; it is separate from an outbound campaign’s audience and schedule.

```mermaid theme={null}
flowchart LR
    Caller[Caller] --> Number[Available phone number]
    Number --> Binding[Inbound binding]
    Binding --> Target[Voice flow or AI agent]
    Target --> Results[Call activity and inbound results]
```

## Binding history

When a number’s destination changes, binding history separates the reporting periods. Investigate the binding associated with the activity rather than assuming all historical calls used the current destination.

## Before receiving calls

Review the destination, available number, saved flow or agent configuration, credits, and recording requirements. Test with a phone you control.

General phone-number provisioning and binding management are not covered by the current customer machine API. Agent publication is a separately documented supported route where approved.

Next: [AI voice agents](https://docs.gomobile.ma/learn/concepts/agents.md), [Flows](https://docs.gomobile.ma/learn/concepts/flows.md), and [Inbound reference](https://docs.gomobile.ma/developers/reference/inbound.md).


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