Freeze one company, user, client and symptom
Record company, user, role, assigned numbers, selected number, desktop, web or mobile path, package and update owner, installed build, browser or operating system, network, local and UTC time, direction, destination, call ID and first visible symptom. Redact credentials, precise location and unrelated customer content.
Separate sign-in failure, “No lines available,” wrong caller identity, route rejection, missing inbound assignment, unavailable user, missing notification, silent ringtone, answer failure, one-way audio, poor media, drop and missing support evidence. Do not merge different users, clients or calls.
Prove assignment and running client before changing either
Confirm the company user, role, assigned number or numbers, inbound user or team assignment, selected outbound number, client path and exact running build. Distinguish a standard EXE or DMG installation from administrator-managed MSI or PKG deployment and from the Chrome web app.
Authentication and a visible keypad do not prove line assignment or calling authorization. Preserve the original state before password reset, number reassignment, update, web reload, cache clearing or reinstall.
Trace distribution, availability and every alert boundary
For one controlled non-emergency inbound call, record the called number, distribution branch, IVR choice if present, user or team membership, ringing duration, availability, application background state, operating-system notification permission, browser permission, ringtone destination, visual alert, audible output, answer action and final endpoint.
A call-history entry, voicemail, browser banner, mobile notification, teammate answer or recording does not prove the affected desktop, web or mobile client received and rendered the ring. Change one routing or alert variable at a time.
Separate local audio, diagnostics, packets and perceived media
Record operating-system and Workspace microphone, speaker and ringtone selections, browser permission, mute, headset or Bluetooth path, device meters and test playback. Preserve diagnostic time, host, network, VPN state, roaming region, bitrate, MOS, packet loss, jitter and round-trip time separately from the affected call ID, signaling, packet directions, decoding and what each party heard.
A passed device test or green network diagnostic is bounded evidence, not proof of the affected call or its remote leg. Repeat the same controlled call after one authorized change and retain an unaffected control.
Compare one bounded network path without declaring causation
After preserving the original failure, compare one controlled alternate path or region. Retain DNS results, VPN state, firewall handling, resolved targets, observed transport, media region, packet flow and local resource state. Do not convert a published requirement, successful alternate network or lower bitrate into a claim that the original Wi-Fi, VPN, firewall, ISP or provider edge was faulty.
If a diagnostic shows NaN, missing metrics or a warning, preserve the raw result and the traffic policy before changing access controls. A diagnostic tool can itself be blocked or incomplete.
Correct one owner and preserve emergency and support evidence
Assign the first divergence to identity, line assignment, distribution, availability, client path, package, build, notification, local device, browser permission, network, media region, signaling, media, emergency address or support. Change one controlled variable and repeat the same non-emergency destination, endpoint, network and direction plus one unaffected control.
Keep entered emergency address, validation, current location, callback number, 933 playback and live emergency outcome distinct. Preserve minimized diagnostic screenshots, call IDs, case, provider finding, action and verified restoration. No Aircall account, client, call, diagnostic, emergency outcome or support response was inspected or tested.
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.