Browser calling
Your next call. Right in the browser.
Place outbound calls from your Bird workspace. Choose your caller identity and trunk, allow microphone access and dial. Use the same controls and call records as the rest of your Voice traffic.
A phone inside your workspace
ExampleExample phone
+1 202 555 0194
Select digits to explore the keypad
Your workspace, ready to call
Choose a trunk, caller identity and microphone before a real call.
Interactive keypad illustration. This preview never places a call.
Trusted every day by teams that build world-class software
Read more customer storiesA practical first call
What does a browser call need?
The browser supplies the phone interface, while Bird carries the call through your trunk. Prepare an eligible caller identity, outbound calling, session credentials and an enabled destination. A browser button cannot replace those calling permissions.
Keep credentials short-lived
The dashboard requests a session credential for the calling client. You do not paste a long-lived API key into the phone interface.
Select the devices you use
Allow microphone access and choose the appropriate microphone. Speaker selection depends on browser support; other browsers use the system output device.
Stay in the workflow
Use a phone without leaving your workspace.
Keep the floating phone available while you work in the dashboard. Send keypad tones when the far end asks for a menu choice or extension. The familiar calling controls sit beside the product records your team needs to investigate the result.
- 01
Test the actual audio path
Check microphone permissions and both audio directions before relying on a customer call. A connected signaling session can still have an audio problem.
- 02
Finish the call deliberately
Hang up through the phone control before closing it. A page or window action should not be your call-management procedure.
One operational record
Find the browser call beside every other call.
Browser calls use the same Voice records and billing path as calls from your own equipment. Inspect the final status and reported reason when a call fails. Use the common timeline and events to keep your application’s view consistent.
Separate connection from completion
An answered status means a call connected. Your team or application records whether the customer’s task was completed.
Use the right client for the job
The dashboard phone is an outbound calling tool. Choose your phone system or call application for incoming ringing, queues, hold and transfer behavior.
Questions about browser calling
Do I need to install a softphone?
Does the phone receive incoming calls?
Can I send keypad tones?
Do browser calls have different rates?
Can I use the browser phone for emergencies?
Build the next part of your calling path
Browser calling guide Follow the setup, requirements and operational checks.
SIP trunking Connect your PBX, softphone or SIP application to the telephone network.
Inbound routing Connect each number to your phone system, forwarding target or call sequence.
Voice pricing Review published destination rates and relevant call components.
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Talk to our Voice team
Hear your first browser call.
Prepare a trunk and caller identity, allow microphone access and call a number you control. Check audio in both directions and inspect the call record.