A deliberate callback. A result you can follow.
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.
One callback. One original attempt.
Let your application own callback intent and duplicates. Follow the telephone record without turning an uncertain response into another call.
Fieldnotes Studio
A customer asked for a callback about their studio visit.
Business request pendingSIP origination and deliberate retry policy belong to the connected application. A public call-record read does not dial.
Queued
No original attemptThe request remains queued. Choose an outcome and run the fictional attempt.
Telephone connection established. Verify two-way media and check the booking system before claiming the request was completed.
The destination was busy: failed with SIP 486. Keep the original callback case and apply a deliberate policy after checking the destination.
The call rang until timeout. Offer the agreed alternate contact or schedule a later attempt under the application’s policy.
The destination was not enabled; no carrier call was placed in this example. An authorized owner must review eligibility and the country setting before a deliberate new attempt.
Final response unavailable. Reconcile this original call and the business case before any replacement. Unknown does not authorize a duplicate callback.
Reconciliation updates the observation of the same original call. A terminal result is retained if later evidence conflicts.
Fictional example. No calls, audio, workspace changes or business actions are sent.
Read the maintained guide ↗Companies that trust Bird across their communications.
Read Bird customer storiesHow does an application place a call?
Send a call from your PBX or application through a SIP trunk. Bird checks access, caller identity and destination. Follow the accepted call through its events and final record while your application keeps the customer context.
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?
How do I test an outbound call?
How are outbound calls priced?
Build the rest of the calling path
Place and inspect your first call ↗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.