Voice overview · Docs — Bird

Voice overview

Bird Voice lets you place calls to phone numbers and answer calls made to numbers you hold. Connect a phone system over SIP, place a browser call, or use the sequence builder to run a saved call flow. Bird connects calls to the public telephone network, the PSTN.

The connection between your phone system and Bird is a SIP trunk. SIP (Session Initiation Protocol) sets up calls between phone systems. Bird gives your workspace a trunk address, which your phone system uses for outbound calls to the telephone network, and which Bird uses in reverse to deliver the calls arriving on your numbers.

You do not need a phone system to make the first call: the phone in the dashboard places one straight from the browser, over one of your trunks.

You can also build a sequence in the dashboard and start it with the Create Call API. The sequence handles prompts, keypad choices, and call routing after the recipient answers.

How a call is placed

Your phone system sends a SIP INVITE to the trunk address to start a call. Bird checks the caller ID, destination country, limits, and wallet balance before contacting a carrier. If the call passes, Bird routes it and relays the audio. Each connection is a leg. When a leg ends, Bird writes its record under Voice > Legs and emits a voice_call.ended event.

A call that fails a check is refused before a carrier is involved, and the specific reason goes onto the leg record. Placing calls covers what Bird reads off each call, and Rejected calls lists every refusal reason and what to do about it.

How an incoming call is answered

A number your workspace holds carries one answer at a time, set on the number itself or, when the number has none, taken from your workspace's default route: deliver the call to one of your SIP trunks, forward it to a number you have verified, run a published sequence, ring a ring group of people online in the browser phone, or reject it. The default route starts as reject, so a number nobody has configured turns callers away.

When a call arrives, Bird checks the account limits and the wallet the same way it does for a call you place, then acts on the number's answer and records what that answer was on the call. Receiving calls covers pointing a number at an answer, what a forward presents to whoever picks up, and how to read a refusal.

Before your first call

For calls through your own SIP equipment, prepare the following. API calls follow the Create Call prerequisites.

Place your first call walks through all three requirements and ends with a real call.

Reading call records requires voice:read; placing calls requires voice:write. Managing trunks, number routes, caller IDs, and sequences uses voice_management permissions. Access to a page does not grant permission to change its settings or place a billable call.

The Voice app in the dashboard

Page What it is for
Metrics Call volume and answer rate over time, call outcomes, top countries, and the inbound and outbound split. See Voice metrics
Legs Per-leg records for workspace calls, with usage totals for the month
Calls Related legs and participants grouped into one call
Numbers Every number the workspace can use for voice, and what each one does with an incoming call
SIP Trunks Your trunks, their SIP domain, who may send traffic to them, and where inbound calls are delivered
Destinations The countries your workspace may call, off by default
Sequences Build, preview, publish, and inspect call workflows
Ring groups Groups of people an incoming call rings in the browser phone. See Ring groups
Phone A floating phone that places calls over one of your trunks and receives calls once you go online

Visibility

A call can contain multiple legs. The log has one record per leg, whether it connected, rang out, or was refused. Forwarded or multi-party calls can therefore have several entries:

The API reference lists the supported public HTTP contracts and SDK methods. The CLI reference and MCP tool reference describe their published operations. These surfaces can expose different operations; a dashboard action or CLI command does not by itself establish a public SDK method.

Limits

Three ceilings apply to your calls, in both directions: how many you may have in progress at once, how many new calls per second, and what you may spend on voice in a UTC day. Your Voice plan sets the concurrent-call and per-second ceilings for your organization: pay-as-you-go uses the default values, and higher Voice tiers raise them. The daily spend limit works differently. Each workspace sets its own limit under Voice > Spend limit, and per country under Voice > Destinations, up to your organization's maximum; the largest Voice plans raise that maximum. A call over any of them is refused at setup, and its record names which one, under Rejected calls. Each plan's values are on the Voice pricing page; upgrade under Billing and payments > Overview.

The platform call duration cap is 4 hours. Bird hangs up both sides of a call that reaches that length, so plan a longer session as more than one call. A call that runs a call sequence counts from when Bird accepted or received it, so time spent waiting to dial and ringing uses part of the 4 hours. Statuses explains how such a call appears in the log.

The per-second ceiling is the voice_call policy in Rate limits, which also explains how your effective limit is resolved and how to raise it.

Next steps

Page What it covers
Place your first call From an empty workspace to a ringing phone
Phone Calling from the dashboard, going online, and what you can do mid-call
SIP trunks Creating a trunk, its connection details, and controlling who may send
Placing calls What Bird expects on the INVITE, and what a call costs
Receiving calls Pointing a number at a trunk or a forward, and what it records
Caller IDs Registering a number and proving you own it with a verification call
Voice destinations Turning on the countries you call, and what high risk means
Leg log Browsing, filtering, and exporting your leg records
Voice events The three call events and their payloads
Troubleshooting Diagnosing a call that does not go through, from its symptom
Webhooks & events Endpoint setup, signature verification, retries, and replay