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

# Inbound and outbound calling

> The difference between receiving calls and placing them, and how teams usually roll them out.

Ramba Voice supports both inbound and outbound calling, but they serve different goals.

## Inbound calling

Inbound calling is about answering the caller who reached out first.

Common inbound use cases:

* front-desk coverage
* appointment requests
* after-hours answering
* basic qualification before handoff

Inbound is often the best place to start because the caller intent is more immediate and the business value is easier to observe.

## Outbound calling

Outbound calling is about reaching the customer first.

Common outbound use cases:

* reminders
* follow-ups
* reactivation campaigns
* status updates

Outbound usually needs tighter review because the caller did not initiate the conversation.

## How teams usually sequence rollout

A common rollout pattern is:

1. launch a narrow inbound use case
2. review call quality and outcomes
3. expand to additional numbers or call paths
4. add outbound once the team trusts the operating model

## Use different success measures

Inbound and outbound should not be judged the same way.

For inbound, common questions include:

* did the agent answer the call well
* did it help the caller reach a useful outcome
* did it route or hand off correctly when needed

For outbound, common questions include:

* did the contact strategy feel appropriate
* did the agent complete the intended task
* did the team have the right controls before launch

## Keep the first rollout narrow

For either direction, a narrower rollout usually produces better learning than a broad one.