# 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. [Start for Free](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fvoice%2Fphone) [Contact sales](/demo?product=voice-browser) ## Set up with your agent [Read the agent setup guide](/docs/ai/set-up-your-agent) Copy this prompt into your coding agent: ```text Bird connects customer communications, data and automation. Help me build with Bird using my coding agent. 1. Read https://bird.com/docs/ai/set-up-your-agent.md and follow its setup workflow for this client. Use an existing connected Bird MCP server or signed-in CLI when available. 2. Read the product guide for the task I want to complete and inspect my existing integration. Identify the workspace, available operations and required setup. 3. Help me complete a first example for the product and destination I choose. Follow the operation through to its actual result, explain any uncertainty, and help me choose the next step. First task: Check the browser phone prerequisites, trunk and caller identity. Walk me through microphone setup and a controlled outbound call. First use the connected Bird MCP server or signed-in CLI for a read-only inventory. Discover the available tools and read their schemas or help; do not invent call-control operations. If neither surface is available, follow https://bird.com/docs/ai/set-up-your-agent.md. Read the linked guides through their .md alternatives. Present the exact target and configuration before changing routing, placing calls, recording audio, purchasing numbers or submitting a port. Obtain my approval for those actions. Use this Bird page as the starting context: https://bird.com/products/voice/browser-calling Read its Markdown alternative and linked guides. Keep the first example relevant to this page and the customer outcome I choose. Preserve the supplied campaign context when following Bird signup or sales links. ``` A phone inside your workspace Example phone 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 stories](/customers) - [Airwallex](/customers/airwallex) - [Glovo](/customers/glovo) - [Zillow](/customers/zillow) - Uber - [Binance](/customers/binance) - Adobe - Meta - PayPal - Pinterest - Square - [Al Jazeera](/customers/aljazeera) - [Aramex](/customers/aramex) - [Bazaar Technologies](/customers/bazaar) - [ComparaOnline](/customers/compara) - [Emma](/customers/emma) ## 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. ## 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. ## 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? No. The dashboard phone uses the browser and a configured Bird SIP trunk. ### Does the phone receive incoming calls? The dashboard phone places outbound calls. Route incoming calls to the phone system or application designed to answer them. ### Can I send keypad tones? Yes. Use the keypad for DTMF choices such as an IVR menu or extension. ### Do browser calls have different rates? They are carried and rated as Voice calls. Review published rates for the destination and inspect the final call record. ### Can I use the browser phone for emergencies? No. Bird Voice does not carry emergency calls. ## Build the next part of your calling path [Browser calling guide](/docs/guides/voice/phone) Follow the setup, requirements and operational checks. [SIP trunking](/products/voice/sip-trunking) Connect your PBX, softphone or SIP application to the telephone network. [Inbound routing](/products/voice/inbound-routing) Connect each number to your phone system, forwarding target or call sequence. [Voice pricing](/pricing/voice) Review published destination rates and relevant call components. ## 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. [Read the browser phone guide](/docs/guides/voice/phone) ## Related resources - [Voice overview](/docs/guides/voice/overview) (docs) - [What is a voice API?](/explained/voice/what-is-a-voice-api) (answer) - [Voice](/products/voice) (product) [Get an implementation brief](/learn/workspace?topic=voice)