Make the call. Keep the context.

Connect your application or phone system to the telephone network with Bird Voice. Present an eligible caller identity, choose the destinations you serve and follow the call from routing to its recorded outcome.

Get Started Contact Sales

Example call journey

A callback from your application

1
Prepare
Trunk · caller identity · destination
2
Connect
Your application → Bird → customer
3
Reconcile
Answer · end · call record

How does an application place a call?

Use POST /v1/voice/calls to place a call with a published sequence or an inline definition. The sequence starts when the recipient answers. You can also connect a SIP application or PBX through a Bird trunk. Both paths require an eligible caller identity, destination access and normal calling admission.

Put the next action inside your customer workflow.

Customer callbacks

Let a customer request a call from your team, then pass the relevant case or order into your own application. Keep your callback queue, permissions and retry decisions beside that context.

Appointments and service updates

Build a calling workflow around a clear outcome: confirm an appointment, explain an update or connect the customer to the right person. Use call sequences when the conversation needs prompts and keypad input.

A call from your browser

Use the Bird browser phone for a controlled outbound call. Prepare the trunk and caller identity first; the phone gives you a practical way to check the connection and inspect its result.

An answered call is the start of the conversation.

Check audio in both directions, keypad tones where needed and a clean hangup. Then match the call record to the job your application intended to complete. A telephone answer can be a person, voicemail or another system; it does not establish that the customer completed the task.

Before dialing

For API calls, prepare the sequence and both Voice write permissions. For SIP, confirm trunk access. Check caller identity, destination permissions and available wallet funds before either path.

If a call fails

Find the stage that failed. Authentication can fail before a record exists; recorded refusal and carrier response help you choose the next check.

Before retrying

Inspect the last call and your application state. Avoid duplicate callbacks when a timeout leaves the outcome uncertain.

Questions before you connect

Can I use my existing PBX?

Yes. Connect SIP-capable equipment to a Bird trunk and keep the calling logic your application or PBX already owns. Test transport, authentication, audio and keypad behavior before rollout.

How do I create a call and inspect its outcome?

Create Call accepts the outbound request. Inspect a saved sequence’s run in the dashboard and its call-leg record when available. Acceptance, an answered call and a completed business task are separate outcomes. An inline call has no saved sequence; if it fails before its leg registers, it has no inspectable result yet.

Can an AI agent prepare the call?

The CLI and MCP Create Call preview requires a compatible client. It prepares a request for a person to review and run in the browser. Preparing the request does not place the call; the HTTP API and SDKs support direct call creation.

How are outbound calls priced?

Review the destination rate card and its billing minimum and increment. Check the recorded answered time and rated cost. Capacity, number charges and additional call components belong in the complete workload estimate.

Build the rest of the calling path

Voice overview Choose the calling path for your customer journey.

Create Call guide Prepare a published or inline sequence, place the call and follow its outcome.

SIP trunking Connect your PBX, softphone or SIP application to the telephone network.

Call sequences Turn prompts, keypad choices and named branches into a versioned workflow.

Browser calling Place an outbound call from your workspace with a browser phone and your SIP trunk.

Voice pricing Review the current destination rates and call components.

Scale without
losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

HarborOrganization

WorkspacesProductionSandbox

Delivery agent

API key · Customer operations team

Active

PermissionsAccess

EmailRead & write

SMSRead & write

ALAlex Lee AdminPermissions updated

Audit log

Production

Workspace: Production
Resource: Delivery agent
WhatsApp: Read accessRead & write

Succeeded

Explore Enterprise

Start with Voice.
Build across channels with Bird.