Outbound calling
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.
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
Trusted every day by teams that build world-class software
Read more customer storiesHow does an application place a call?
A SIP application or PBX sends the call through a Bird trunk. Bird checks access, identity and destination, then connects the telephone leg. Your application owns the reason for the call and the conversation. Use the call API to read records and events to keep your system informed.
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
Confirm access to the trunk, an eligible caller identity, destination permissions and available wallet funds.
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?
Does the call-record API start a call?
How are outbound calls priced?
Build the rest of the calling path
Voice overview Choose the calling path for your customer journey.
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.
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Talk to our Voice team
Make your first outbound connection.
Prepare one calling path and test it with a number your team controls. Bring your destinations and calling pattern to a specialist when you plan a larger rollout.