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

# Outbound call limits

> Workspace-wide daily protection for calls placed through integrated numbers

## What the daily limit covers

The daily outbound allowance is shared by **every assistant in the workspace**. A call counts when it is started through:

* a phone number provided through the number marketplace, or
* your own verified caller ID when it uses the integrated outbound route.

Single calls, campaigns, scheduled callbacks, automations, the REST API, and the `make_call` MCP tool all use the same workspace counter. Parallel requests are reserved atomically, so the allowance cannot be exceeded by starting several calls at once.

Calls that reach `busy`, `no_answer`, or another carrier outcome still count because the outbound attempt has already been placed.

## What is always unlimited

These call types do not use the daily allowance:

* inbound calls,
* browser and web-widget calls,
* outbound calls through your own SIP trunk or BYOC connection, and
* WhatsApp voice calls.

Connect a provider such as Twilio, Telnyx, Zadarma, DIDLogic, MIXVOIP, or any SIP-compatible carrier under **Settings → Numbers** when you need unlimited outbound calling.

## View usage and request an increase

Open **Settings → Limits** to see:

* calls used and remaining today,
* the current daily allowance,
* the next reset time in the workspace timezone, and
* the latest increase-request status.

Workspace owners and admins can submit one pending increase request with a requested daily limit, a business reason, and an optional business website. Platform administrators review requests and may approve a different final allowance. Approved changes apply to the complete workspace, including every assistant.

## API and MCP

Use the public API with the `settings:read` or `settings:write` scope:

* `GET /v1/settings/outbound-limits`
* `POST /v1/settings/outbound-limits/requests`

Equivalent MCP tools:

* `get_outbound_limits`
* `request_outbound_limit_increase`

When the allowance is exhausted, new integrated outbound starts fail with HTTP `429 rate_limited` before the platform creates an outbound SIP participant. The response includes the next reset time; inbound, web, and BYOC calls remain available.