What are Web Calls?
A web call is a conversation with your assistant that runs entirely in your browser — your computer’s microphone and speakers stand in for a phone. No number is dialled, nothing rings, and the call connects within seconds of clicking Start Call. Web calls are Voxworks’ third call type, alongside Inbound and Outbound. In the Call Log’s Type column they show a computer-monitor icon with a Web tooltip, where phone calls show directional arrows. You’ll meet web calls when testing scripts — the In Browser option in the Test Call dialog places a web call, so you can talk to a script without using a phone. On the call itself, your assistant behaves exactly as it would on a phone call: the same script, voice, tools, and conversation behaviour. The differences are all in how the call starts, ends, and appears in your logs — which is what this page covers.Starting a web call
In the app, web calls start from the Test Call dialog, which opens from several places:- The Test Call button in the script editor header.
- The Test Call row action on the Scripts page.
- The Test Call button inside the New Call modal (enabled once you’ve selected a script).
- Your browser asks for microphone access — the first time, at least. The call can’t connect without it.
- The dialog shows “Loading…” while the call connects.
- The dialog shows “Connected” in green, with a “Browser call connected” toast, and your assistant starts talking.
If the call won’t start
Web calls draw on your wallet like any other call. If your balance is too low, the call is rejected before it connects and you’ll see: “Insufficient wallet balance. Please top up your account to place calls.” Top up under Settings → Billing and try again. Other connection failures show as “Browser call failed:” with a short reason — a retry usually resolves a transient network issue.Ending a web call
A web call ends in one of three ways:- You click Hang Up — the red button that appears in the dialog while the call is active.
- The assistant ends the call — the natural close after an exchanged goodbye, exactly as on a phone call.
- The connection drops — closing the browser tab or losing your network ends the audio, and the platform finalises the call.
How web calls appear in the Call Log
Web calls sit in the same Call Log as everything else, with a few differences worth knowing:
Statuses and end reasons themselves work the same way for every call type — see the Call Statuses reference.
Recordings are MP4 files
Web-call recordings are saved as MP4 files, where phone-call recordings are MP3. In practice this changes very little:- The recording plays back in the same waveform player at the top of Call Details — press play as usual.
- If you download the recording, you’ll get an
.mp4file rather than an.mp3. Any modern media player opens it.
Web calls are never retried
Phone calls that don’t connect — voicemail, no answer, busy — can be retried, automatically in batches or manually via the API. Web calls are excluded from all of this:- No automatic retries. A web call only exists while your browser session does, so there is nothing for the platform to redial.
- The retry API refuses them. Attempting to retry a web call through the Retry Call endpoint returns an error.
Next Steps
- Test Calls — the operational side of testing: In Browser vs My Phone, billing, and the Test badge in the Call Log.
- Call Details — the recording player, transcript, and analysis tabs where you review a finished web call.
- Call Statuses, End Reasons & Outcomes Reference — the canonical reference for every status a call can carry.

