Skip to main content

Spoke hardware and audio requirements

Device, browser, headset, and network requirements for using Spoke (Cubby Calls) reliably.

Cubby Calls uses Spoke, a cloud-based phone system that runs in your browser. To make and receive calls reliably, your device, audio setup, and network need to meet the following requirements.


Device and browser

  • Browser: Google Chrome (strongly recommended). Spoke's audio engine is optimized for Chrome. Safari, Firefox, and Edge may work but are not officially supported for calls.

  • Operating system: Windows 10+, macOS 11+, or ChromeOS. Mobile devices (iOS/Android) have limited support — use a desktop or laptop for the best call experience.

  • Microphone permission: Chrome must have permission to access your microphone. If prompted when a call starts, click Allow. To check: Chrome Settings → Privacy and security → Site settings → Microphone — confirm Cubby is not blocked.


Audio devices

  • Headset (recommended): A USB or 3.5mm headset with a built-in microphone gives the best call quality. Wired USB headsets have lower latency and more consistent quality than Bluetooth.

  • Built-in microphone: Laptop microphones work but pick up more background noise and echo. A headset is strongly preferred in front-desk or office environments.

  • Speakers: If you use external speakers instead of a headset, position them away from the microphone to prevent echo. A headset eliminates this problem entirely.

⚠️ Echo or feedback during calls? This almost always means audio is routing through speakers rather than a headset. Switch to a headset with a built-in microphone to resolve it immediately.


Network requirements

  • Minimum bandwidth: 1 Mbps upload and download per active call.

  • Connection type: A wired Ethernet connection is preferred over Wi-Fi for call stability. If on Wi-Fi, ensure you have strong signal at your workstation.

  • VPN: If your facility uses a VPN, check with your IT team that Spoke and WebRTC traffic is not blocked or routed through a congested VPN tunnel — this is a common cause of one-way audio.


Quick fixes for audio issues

  • Refresh the Cubby page — Spoke re-initializes the audio device on each page load.

  • Check that your headset is selected as the default audio device in your OS sound settings (not just plugged in).

  • Unplug and replug USB headsets if Chrome is not detecting them.

  • For persistent issues, see Troubleshoot Cubby Calls and Spoke issues.

Did this answer your question?