Contact Centre Feature

Browser Calling (WebRTC)

Browser calling runs the agent's audio path through the browser over WebRTC. An agent needs a headset and a tab, not a desk phone, a VPN or an IT-managed softphone install. Calls can be created, answered, transferred and ended from the browser, which is what makes remote and hybrid contact centre teams practical to run.

No hardware

Browser-based agents

API included

What Browser Calling gives you

Let agents take and make calls from a browser tab, including transferring a live call, with no desk phone or softphone install.

Nothing to install

A browser and a headset. No desk phone, no softphone rollout, no per-machine IT ticket.

Transfer a live call

Transfer is supported from the browser, so the workflow is not limited to simple answer-and-hang-up.

Remote agents work the same way

An agent at home is the same configuration as an agent in the office.

Short-lived access tokens

Browser sessions authorise with minted tokens rather than embedded permanent credentials.

How Browser Calling works

End to end, in the order it actually happens.

  1. 1

    The agent opens the dialer in a browser and signs in.

  2. 2

    A short-lived token is minted for the session.

  3. 3

    Calls are placed or received in the browser over WebRTC.

  4. 4

    The agent can transfer or hang up from the same interface.

What Browser Calling does not do

Worth knowing before you build a process around it.

  • Audio quality depends on the agent's own network and headset. Browser calling does not fix a bad home connection.
  • Confirm supported browsers for your rollout rather than assuming every browser behaves identically.
  • This is the agent-side audio path, not a replacement for your telephony numbering and routing.

Common uses

  • Remote and hybrid teams

  • Fast agent onboarding

  • Seasonal or temporary agents

  • BYOD contact centres

Used most in

BPOE-commerceSaaSEdTech

Related features

Browser Calling FAQs

What is Browser Calling in a contact centre?

Browser calling runs the agent's audio path through the browser over WebRTC. An agent needs a headset and a tab, not a desk phone, a VPN or an IT-managed softphone install. Calls can be created, answered, transferred and ended from the browser, which is what makes remote and hybrid contact centre teams practical to run.

How does Browser Calling work?

1. The agent opens the dialer in a browser and signs in. 2. A short-lived token is minted for the session. 3. Calls are placed or received in the browser over WebRTC. 4. The agent can transfer or hang up from the same interface.

What does Browser Calling not do?

Audio quality depends on the agent's own network and headset. Browser calling does not fix a bad home connection. Confirm supported browsers for your rollout rather than assuming every browser behaves identically. This is the agent-side audio path, not a replacement for your telephony numbering and routing.

Which industries use Browser Calling most?

BPO, E-commerce, SaaS, EdTech. Typical uses are remote and hybrid teams, fast agent onboarding, seasonal or temporary agents, byod contact centres.

What is a cloud contact center?

A cloud contact center is a customer service platform hosted in the cloud that allows businesses to manage customer interactions across multiple channels (phone, email, chat, social media) without on-premise hardware. It provides features like automatic call distribution (ACD), IVR, call recording, and analytics.

How is CCaaS different from traditional call centers?

CCaaS (Contact Center as a Service) is cloud-based, requiring no hardware investment, offering pay-per-use pricing, automatic updates, and easy scalability. Traditional call centers require significant upfront investment in hardware, ongoing maintenance, and are harder to scale.

Set up Browser Calling for your team

Self-serve platform. No hardware, no long procurement cycle.