Treat Workspace as a service-bound client family
Aircall Workspace exposes desktop, Chrome web and mobile paths for an Aircall company account. It is not documented as a generic SIP softphone for arbitrary registrar credentials. A successful sign-in establishes a user session, not an assigned number, outbound caller identity, inbound distribution, emergency address or completed call.
Record company, user, role, assigned numbers, selected calling number, client path and the administrator who owns number and distribution changes. Aircall documents a “No lines available” result when an administrator has not assigned the user to a number; preserve that state before reinstalling or changing local devices.
Pin client path, package, build and update owner
Keep the downloaded Windows or macOS application, Chrome web app, iOS app and Android app as separate execution paths. Record package source, architecture, installer type, app-reported build, browser or operating-system version and update owner. Aircall documents automatic background updates for standard EXE or DMG installs, administrator-managed updates for MSI or PKG installs, and real-time web updates that can change behavior after reload.
The current download and support pages do not state every mobile and tablet boundary identically. Treat those pages as dated records, not a compatibility guarantee. Preserve the failing build and current store or support record before updating, reloading, reinstalling or changing deployment method.
Separate number assignment, distribution, availability and alert delivery
For an inbound attempt, retain the called Aircall number, user or team assignment, call-distribution branch, ringing duration, user availability, desktop or browser notification, operating-system permission, mobile background state, visual alert, audible alert, answer action and final endpoint. A call-history row, voicemail, notification on another device or teammate answer does not prove the affected client rang.
For outbound calling, preserve the selected Aircall number, entered country code, displayed caller identity, destination, policy result and call ID. Signing in, seeing a keypad or choosing a number does not prove authorization, routing, answer or two-way media.
Keep local audio controls and live media independently observable
Record operating-system microphone, speaker and ringtone devices, Workspace selections, browser permission, mute state, headset path, remote-control support, signaling, packet directions, codec, decoding and what each party heard. Aircall exposes microphone and speaker tests plus processing, automatic-level and noise-cancellation controls; each is a local observation rather than proof of a completed two-way call.
Preserve one original failing result before changing devices or processing. A meter, test tone, supported-headset list, USB connection or remote-control button does not prove the affected call used that device or that the far party heard intelligible audio.
Use diagnostics as scoped measurements, not root-cause verdicts
Aircall Workspace network diagnostics report items including MOS, bandwidth, TURN, protocol, packet loss, jitter, round-trip time, processor and memory. Retain the client path, host, network, VPN state, selected roaming region, bitrate, test time and raw result. These measurements simulate or sample conditions; they do not reproduce every route or establish what happened on an earlier call.
Correlate one affected call ID and timestamp with observed traffic, media direction and what each party heard. A green test, alternate network, manually selected region or lower bitrate can narrow a boundary, but it does not by itself prove the original Wi-Fi, VPN, firewall, ISP, media region or provider was the cause.
Bound emergency, recording and support evidence
For U.S. and Canadian numbers, Aircall documents a per-user emergency address, callback number, address validation and a 933 verification path. Keep entered address, validated form, current physical location, selected line, callback number, 933 playback and an actual emergency route separate. Use the provider-approved 933 test; do not place 911 as a generic test.
Recordings, notes, tags, diagnostic screenshots and support submissions may contain customer or location data. Preserve authorization, minimization, call ID, case, provider finding, action and verified restoration separately. A support reply, restart, reinstall, address status or diagnostic recommendation does not by itself prove root cause or durable recovery.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Aircall — Workspace downloads ↗
- Aircall — What is Aircall Workspace? ↗
- Aircall — Access Workspace and make calls ↗
- Aircall — Mobile device requirements for Workspace ↗
- Aircall — Device and headset recommendations ↗
- Aircall — Keeping Workspace up to date ↗
- Aircall — Workspace audio settings ↗
- Aircall — Audio quality troubleshooting guide ↗
- Aircall — Workspace network diagnostics ↗
- Aircall — Emergency address setup for US and Canada numbers ↗
- Aircall — Workspace inbound calls ↗
- Aircall — Contacting Aircall Support ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.