> ## Documentation Index > Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt > Use this file to discover all available pages before exploring further. # Web Calls > What browser-based web calls are, how they start and end, how they differ from phone calls in the Call Log, and why they are never retried. ## 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). In the dialog, under **Call Options**, choose **In Browser** (the alternative, **My Phone**, places a normal outbound phone call to your saved number — see [Test Calls](/calls/test-calls)). The panel confirms: *"The call will be initiated directly in your browser."* Click **Start Call**. A few things happen in quick succession: 1. **Your browser asks for microphone access** — the first time, at least. The call can't connect without it. 2. **The dialog shows "Loading..."** while the call connects. 3. **The dialog shows "Connected"** in green, with a *"Browser call connected"* toast, and your assistant starts talking. Web calls don't queue. Unlike outbound phone calls, which wait for their scheduled time and a free dispatch slot, a web call connects the moment you start it — there is no **Scheduled** or **Queued** stage. ### 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. However the call ends, the usual post-call processing runs: the transcript is finalised, and the Call Summary, Call Objectives, and Analysis tab all appear in [Call Details](/calls/call-details) shortly after. *** ## 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: | What you'll see | How it differs from a phone call | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Type column** | A computer-monitor icon with a **Web** tooltip, instead of an inbound/outbound arrow. | | **Status** | The call appears the moment it connects, already **In Progress**. Web calls are never **Scheduled** or **Queued**. | | **Scheduled time** | Set to the moment the call started — for a web call, scheduled and actual time are always the same. | | **Contact** | If the call was started for a specific contact, that contact shows as normal. Otherwise the call is logged against a placeholder contact named **unknown web\_call\_received**, created automatically for your team the first time it's needed. | | **Phone numbers** | There are no real numbers on a browser call, so the number fields show **web**. | | **Filtering** | The **Type** filter offers **All Types**, **Inbound**, and **Outbound** only — there is no Web option. To find web calls, type "web" into the search box instead. | Statuses and end reasons themselves work the same way for every call type — see the [Call Statuses reference](/calls/statuses). *** ## 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](/calls/call-details) — press play as usual. * If you download the recording, you'll get an `.mp4` file 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. If a web call fails or ends early, simply start a new one — it connects in seconds and costs nothing extra to set up. *** ## Next Steps * [Test Calls](/calls/test-calls) — the operational side of testing: In Browser vs My Phone, billing, and the Test badge in the Call Log. * [Call Details](/calls/call-details) — the recording player, transcript, and analysis tabs where you review a finished web call. * [Call Statuses, End Reasons & Outcomes Reference](/calls/statuses) — the canonical reference for every status a call can carry.