# Video Call Check

> A guided pre-meeting check for your microphone, camera and speakers, with a pass/warn/fail verdict and fix for each, plus a shareable report. Nothing uploaded.

- URL: https://bytescope.dev/en/call-ready/
- Locale: en · Also: [ja](https://bytescope.dev/ja/call-ready.md) · [zh-Hant](https://bytescope.dev/zh-Hant/call-ready.md)
- Runs: Everything runs locally in your browser — nothing is uploaded.
- Requires: Any modern browser (Chrome, Edge, Firefox, Safari), desktop and mobile.
- Updated: 2026-09-08

## What it does

Before an important call, what you want isn't ten meters and charts — it's a yes or no. This wizard walks through the three things that break meetings: microphone (does the level move when you speak), camera (can you see yourself), and speakers (left/right test tones you confirm by ear). Each step ends in a green pass, orange warning or magenta fail with a one-line diagnosis and the fix.

At the end you get a summary report: every check, its verdict, and your device names — copyable as plain text to paste to IT, a colleague, or a meeting host who's asking "is your setup okay?". The speaker step plays isolated left-then-right tones, which also catches reversed headphones and dead earbuds sides — the failure people discover mid-meeting.

Runs entirely in your browser with nothing uploaded. The full Mic Test and Webcam Test tools are one click away from their respective steps when a check fails and you need the deeper instruments.

## Limits

Does not test the video-call service itself (Zoom, Meet, Teams); it checks your camera, microphone and speakers from the browser.

## Machine output

Copy JSON copies an envelope `{ tool, url, generatedAt, userAgentHint, result }`. `tool` is `"call-ready"`; `result` is the three-step wizard verdict below. `"untested"` is a distinct string — never folded into fail.

- `mic` (string) — `"untested"` | `"pass"` | `"warn"` | `"fail"`. Mic step status; `"untested"` means that step was not run.
- `camera` (string) — `"untested"` | `"pass"` | `"warn"` | `"fail"`. Camera step status; `"untested"` means that step was not run.
- `speakers` (string) — `"untested"` | `"pass"` | `"warn"` | `"fail"`. Speaker step status; `"untested"` means that step was not run. `"warn"` is emitted when the meter was quiet or speakers were unconfirmed.

## FAQ

### What exactly does the check test?

Microphone (permission, device present, level responds to speech, clipping/noise sanity), camera (permission, device present, live frames arriving, resolution granted), and speakers (you confirm hearing isolated left and right tones). Each produces pass/warn/fail with a specific reason.

### Can I send the results to IT?

Yes — the final report is a plain-text summary (verdicts, device names, browser) with a copy button. It deliberately contains no IP address or anything sensitive, so it's safe to paste into a ticket or chat.

### Everything passed but people still can't hear me in the meeting app — why?

Then your hardware and browser are fine, and the problem is the meeting app's own settings: it may be using a different microphone or speaker than the one that passed. Check the app's audio device dropdowns first — this check narrows the problem to exactly that layer.

### Does it work right before a meeting on a locked-down work laptop?

It runs in the browser with no install, so usually yes. If your organization blocks camera/mic access for websites, the permission step will fail with that diagnosis — which itself tells you the meeting app may face the same policy.

## Related tools

- [Mic Test](https://bytescope.dev/en/mic-test.md) — The full microphone instrument panel.
- [Webcam Test](https://bytescope.dev/en/webcam-test.md) — The full camera instrument panel.