Browser calling (WebRTC)

A visitor clicks a button on your website, their microphone connects, and they're talking to your assistant — no phone in hand, no number dialled. That's browser calling.

What it is#

Browser calling turns a button on your website into a live voice call with your OnCore assistant. The visitor clicks, grants microphone access, and speaks to the same assistant that answers your phone line — the call runs over the internet, entirely inside the web page, so there is nothing to dial and no phone needed. Your server hands the visitor's browser short-lived connection details for each call; your account credentials never reach the visitor.

What you can do with it#

• Put a "talk to us" button on your site — visitors get a spoken conversation the moment they click, instead of hunting for a number and dialling it.
• Reach visitors anywhere — someone browsing from abroad talks to your assistant without dialling an international number.
• Greet by page — each call can carry its own opening line, so the button on your pricing page can open differently from the one on your support page, while the assistant's saved greeting covers everywhere else.
• Keep one assistant for phone and web — the button connects to the assistant behind a phone number you already own, so its behaviour stays in one place.
• Tell website calls apart — every browser call is announced to your systems marked as coming from the web, so your reporting can separate website conversations from dialled-in ones.

How to set it up#

The prerequisite is an assistant already answering one of your phone numbers — the button connects to that number. From there, your server exchanges your API key for short-lived connection details tied to that number, passes them to the visitor's browser, and the browser joins the call with its microphone — the two-step integration is in the Browser voice calls guide, with the full endpoint specification in the WebRTC API reference. Browser calls fire the same webhooks as phone calls — an assistant-request when the call starts and an end-of-call report when it finishes — and appear in your call history through the Calls API with their transcript and summary like any other call.

Limits & FAQ#

• Connection details are valid for 10 minutes — that is the window to join, not a cap on the call; once connected, the visitor stays on until the call ends. If the details expire unused, your server simply requests fresh ones.
• Each browser call is private between one visitor and the assistant — every click starts its own call; visitors never share a line.
• The per-call opening line can be up to 500 characters; leave it out and the assistant uses its saved greeting.

Does the visitor need to install anything? No. The call runs in the web page itself — the visitor only has to allow microphone access when the browser asks.

Is it the same assistant as our phone line? Yes. The button is keyed to a phone number you own, and the assistant assigned to that number takes both the dialled calls and the browser ones.

How do these calls show up in our reporting? Exactly like phone calls — an end-of-call report is delivered when each call finishes, and the call appears in your call history with its transcript and summary. The start-of-call event marks the call as coming from the web — see the assistant-request webhook — so you can count website calls separately.