Audio call (WebRTC): technical requirements and troubleshooting
What your browser needs for the in-session voice call in Co-browse, and how to fix the most common microphone and connection problems.
Watch this step in the video · Voice call
During a Co-browse session you can talk to the customer by voice without dropping the chat or installing anything. The call runs on WebRTC, right in the browser. This guide covers what it needs and how to fix the most common issues.
How it works
Inside the Co-browse session modal, the agent starts the call with the Call button. The customer sees a prompt ("The agent wants to talk") and can Accept or Decline. On accept, audio is established and the state moves through Ringing… → Connecting… → In call, with a timer. To end it, tap Hang up. It is audio only (no video) and the agent always initiates.
Requirements
- A WebRTC-capable browser: up-to-date Chrome, Edge, Firefox or Safari. Some in-app embedded browsers block WebRTC.
- A secure connection (HTTPS): microphone access only works over HTTPS. The customer widget must be served over HTTPS.
- Microphone permission: the agent's browser asks for the microphone right after the customer accepts.
- A network that allows STUN/UDP: this version uses STUN servers only (no TURN relay), so very restrictive networks may fail (see below).
Steps for a clean call
- Start the Co-browse session and wait for the customer to accept it.
- Tap Call in the modal toolbar.
- Ask the customer to accept the voice prompt on their screen.
- When your browser asks for the microphone, click Allow.
- Confirm the status reads In call and the timer is counting up.
Troubleshooting
"Couldn't access the microphone. Check your browser permissions." The microphone permission is blocked. Click the padlock in the address bar, enable the microphone for the site, and reload. On Windows/macOS, also confirm the OS allows the browser to use the microphone.
You hear nothing even though it says "In call". Check the system audio output device, the volume, and that the browser isn't blocking autoplay. Ask the customer to raise their volume too.
"Couldn't establish the call." This is almost always a network issue (symmetric NAT, corporate firewall, or VPN). Because we don't use a TURN relay yet, roughly 1 in 7 very locked-down networks may fail to connect. Try another network (mobile data), turn off the VPN, or ask the customer to switch networks.
"Your browser doesn't support voice calls." The browser has no WebRTC, or you're in an embedded browser. Open the chat in an up-to-date Chrome, Edge, Firefox or Safari.
The customer never sees the voice prompt. Make sure the Co-browse session is still active and the customer hasn't stopped sharing.
Tips
- Tell the customer in chat before tapping Call so they expect the prompt.
- If the call fails on an office network, switching to mobile data usually fixes it instantly.
Related articles
Related articles
-
What Co-browse is and how to enable it
Co-browse lets you see the customer's screen in real time to guide them better. Learn how to enable it.
-
Co-browse complete guide
Co-browse in depth, in 32 chapters: radar, identified visitors, consent, remote control, masking, marks, voice call, page changes and how a session ends, all real.
-
Co-browse: add-on tiers and pricing
Co-browse is bought separately on any plan: Standard 50 USD/mo (3 concurrent sessions), Pro 90 (6), Business 150 (10) and custom Enterprise.
-
How to start a Co-browse session with a customer
Step by step to invite the customer to share their screen and guide them in real time.
-
Prerequisites for using Co-browse
Before you start your first Co-browse session, check the add-on, your permissions and the Webchat channel conditions.