# Why use WebRTC for business calling?

> Explore why a WebRTC softphone can make browser calling and PBX administration more convenient.

URL: https://webrtcclient.com/blog/why-webrtc/ | Published: 2021-09-07

![WebRTC Client panels: an active call with transcription and assistant toggles, live voicebot calls with transcript, and call queues](https://webrtcclient.com/img/product/webphone-panels.jpg)

WebRTC makes real-time communication possible in compatible browsers. With a browser softphone and a properly configured PBX, it gives teams a way to make and receive business calls without installing a separate desktop phone application.

## A familiar place to work

A browser-based dialer places calling alongside the web applications people already use. Users need a supported browser, network access and a microphone and speaker or headset. They must also grant microphone permission when prompted. The PBX and client still need to be configured before calling can begin.

WebRTC Client connects to an existing compatible phone system using SIP over WebSocket. That means a business can use its PBX for extension registration and call routing while providing a browser interface to its users. See the [compatibility overview](https://webrtcclient.com/compatibility/) for supported systems, including Asterisk, FreePBX and VitalPBX.

## Calling features around WebRTC

WebRTC itself supplies communication capabilities; the application adds the tools a team uses. WebRTC Client includes a web phonebook, presence buttons and speed dials, and a Chrome extension for dialing from `tel:` links. These features can reduce the need to switch between tools or retype numbers. Read more about [call features](https://webrtcclient.com/features/call-features/) and [click-to-call](https://webrtcclient.com/features/click-to-call/).

## Administration for multiple customers

For providers and resellers, managing users across separate customer organizations can be as important as the dialer. The management portal organizes access through system administrator, reseller, customer and user levels. White-label branding and policies offer further ways to tailor the service to customers.

A browser approach does not remove the need to check PBX settings, network connectivity or audio devices. It does provide a common interface for users and a central place to manage the service. The next generation of WebRTC Client is in development, with more to come.

## Key takeaways

- WebRTC enables real-time communication in compatible browsers.
- A browser softphone connects users to a suitably configured PBX.
- Calling tools and central management extend the basic browser connection.
- Audio permissions, network access and PBX setup still matter.
