Hardware and network requirements
Before deploying HyperConnect across your business, verify that your workstations, network infrastructure, and peripherals meet the requirements below. Proper hardware ensures clear voice quality, reliable messaging, and a smooth experience for front-desk staff handling calls and conversations throughout the day.
On this page
- Why this matters
- Workstation requirements
- Network requirements
- Headset requirements
- Mobile requirements
- Physical phone requirements
- Related articles
Why this matters
HyperConnect runs a VoIP softphone, a real-time messaging interface, and Zenoti CRM simultaneously in the browser. This combination demands more resources than typical web applications. Businesses that deploy on underpowered hardware experience choppy audio, delayed notifications, and browser crashes during peak hours β all of which directly impact guest experience and staff productivity.
Workstation requirements
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| CPU | Dual-core 2.0 GHz | Quad-core 3.0 GHz or higher | Multitasking with CRM, browser tabs, and VoIP requires additional cores. |
| RAM | 4 GB | 8 GB or higher | Softphones and browsers typically use more than 4 GB when running concurrently with CRM and multiple browser tabs. |
| Storage | 10 GB free | SSD 256 GB+ | SSD dramatically reduces access times for call recordings, transcripts, and frequently used templates. HyperConnect caches data locally before upload. |
| Operating system | Windows 10 or macOS 10.14+ | Latest stable release | Keep your OS updated for security patches and WebRTC compatibility. |
| Browser | Chrome or Edge (latest) | Chrome on Windows (best-supported) | Safari on macOS may have WebRTC limitations affecting call quality. Firefox is supported but Chrome provides the most reliable VoIP experience. |
| Display | 1280 x 720 | 1920 x 1080 or higher | Higher resolution improves readability of the timeline, conversation list, and analytics dashboards. |
Tip: For call center environments with 10+ agents, use the recommended specifications as a baseline. Agents who frequently multitask (CRM + HyperConnect + browser tabs) should have 8 GB RAM minimum.
Network requirements
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| Internet speed | 50 Mbps download / 20 Mbps upload | 100 Mbps+ symmetric | Per-agent VoIP uses approximately 100 Kbps up and down. Total bandwidth must account for all agents plus other business traffic. |
| Connection type | Wired Ethernet | Gigabit Ethernet or dedicated VLAN | Avoid Wi-Fi for VoIP workstations. Wi-Fi introduces variable latency that causes audio jitter, one-way audio, and dropped calls. |
| Latency | Less than 150 ms | Less than 50 ms | High latency causes noticeable voice delay. Test with a VoIP quality tool before deployment. |
| Jitter | Less than 30 ms | Less than 10 ms | Jitter causes choppy, robotic-sounding audio. |
| Packet loss | Less than 1% | Less than 0.1% | Even 1% packet loss causes audible voice quality degradation. |
Important: For businesses running VoIP on the same network as guest Wi-Fi and POS (Point of Sale) systems, configure a dedicated VLAN for VoIP traffic with Quality of Service (QoS) priority. This prevents bandwidth contention during peak hours.
Firewall and port requirements
HyperConnect VoIP requires the following ports to be open:
- HTTPS (TCP 443) β Application traffic and signaling
- STUN/TURN (UDP 3478) β NAT traversal for WebRTC
- Media (UDP 10000-60000) β RTP voice media streams
If your business uses a VPN, test VoIP quality with the VPN active. Some VPNs add latency or block UDP traffic, causing one-way audio or no audio.
Headset requirements
| Component | Minimum | Recommended | Notes |
|---|---|---|---|
| Type | USB noise-cancelling microphone | Certified VoIP headset (USB or DECT) | Professional VoIP headsets provide better noise cancellation, echo suppression, and call control buttons. |
| Connection | USB | USB or DECT (with base station) | Avoid Bluetooth headsets for front-desk use β they introduce latency and may drop connections during long calls. |
For supported headset models and adapter compatibility, see Supported headphones and headsets.
Warning: Consumer Bluetooth headsets are not supported for VoIP use. This includes Apple AirPods, Samsung Galaxy Buds, Beats Fit Pro, Bose QC Earbuds, and generic Bluetooth earbuds. These devices introduce audio latency, have unreliable microphone quality for voice calls, and lack call control functionality.
Mobile requirements
| Component | Requirement |
|---|---|
| Android | Android 8.0 or later, Zenoti Mobile App version 4.21.5+ |
| iOS | iOS 14.0 or later, Zenoti Mobile App version 1.43.4+ |
| Internet | Stable Wi-Fi or 4G/LTE connection. Cellular data usage for VoIP is approximately 1 MB per minute. |
Note: Mobile VoIP call quality may be lower than desktop, particularly on cellular connections. For critical call handling, use the desktop application.
Physical phone requirements
If using Yealink physical phones, the following are required:
- Ethernet cable (D-Link or standard Cat5e/Cat6) β connects the phone to your network
- Power adapter β required unless your network switch supports Power over Ethernet (PoE)
- PoE switch (optional) β eliminates the need for a separate power adapter per phone
For supported phone models and provisioning steps, see Configure a physical phone device.