Troubleshoot HyperConnect issues
This article covers common issues with voice calls, messaging, physical phone devices, and the HyperConnect application, along with steps to diagnose and resolve each problem.
On this page
- Voice call issues
- Messaging issues
- Physical phone device issues
- Application issues
- Network troubleshooting
- Understanding message status indicators
- If the issue persists
- Related articles
Before you begin
- You need the Connect Access Enable permission under Configuration > Security > Security Roles > select a role > Zenoti HyperConnect.
- For voice-specific troubleshooting, you also need Enable Incoming Calls and Enable Outgoing Calls permissions.
- HyperConnect must be provisioned for your organization before any of the features described here are available.
Voice call issues
Employee cannot make or receive calls
If an employee cannot place or receive calls, the issue is most likely related to permissions or device configuration.
- Navigate to Configuration > Security > Security Roles at the organization level.
- Select the role assigned to the employee.
- Go to the Permissions tab.
- Expand Zenoti HyperConnect > Voice.
- Verify that these permissions are enabled:
- Enable Outgoing Calls β allows the employee to make outgoing calls.
- Enable Incoming Calls β allows the employee to receive incoming calls.
- Click Save.
If the permissions are already enabled and the issue persists, ask the employee to delete and re-add their device in HyperConnect to reset the connection.
Calls drop unexpectedly
Calls may drop in two scenarios: the call disconnects after ringing a few times, or the call drops during an ongoing conversation.
Common causes:
- Network connectivity issues on the caller's or the center's end.
- The caller ended the call intentionally.
If the call was not ended intentionally, ask the caller to check with their network service provider. On the center side, verify that the internet connection is stable and meets the minimum bandwidth requirements.
No audio on a connected call
If a call connects but there is no audio:
- Spam call β The system may have identified the incoming call as spam. Check if similar calls have been flagged previously.
- Faulty receiver β The physical handset may be damaged. Test with a different handset to confirm.
- Bluetooth issues β Verify that the Bluetooth device is properly paired, charged, and turned on. Try a different Bluetooth device to isolate the problem.
Poor call quality
For physical phone users:
- Verify that the employee has a strong, stable internet connection.
- Check that the handset is securely connected to the base phone.
- On Yealink phones, verify that both the power adapter and the Ethernet cable are connected. Using only an Ethernet cable without the power adapter can degrade call quality.
For softphone users:
- Confirm that the headset is correctly paired with the computer.
- If the issue persists, try re-pairing or using a different headset.
- Close unnecessary browser tabs and applications that may consume bandwidth.
Greetings or recorded messages do not play
If welcome messages, hold messages, or voicemail prompts do not play:
- Navigate to HyperConnect > Settings > Voice.
- Check each section where audio files are configured (welcome greeting, hold greeting, voicemail prompt).
- Verify that an audio file is uploaded in each required section.
- Confirm the audio file is in MP3 format. HyperConnect supports MP3 files with a maximum size of 5 MB. Files in other formats (WAV, M4A) may upload but not play.
- If the file is not in MP3 format, convert it and re-upload.
- Place a test call to verify that the greeting plays.
If the issue persists, clear the browser cache and cookies, or try accessing HyperConnect from a different browser.
Calls go straight to voicemail without ringing
If incoming calls skip ringing and go directly to voicemail:
- Navigate to HyperConnect > Settings > Voice.
- Scroll to the Missed Calls Forward To section.
- Check the After field. This controls how many seconds an incoming call rings before forwarding to voicemail.
- If the value is 0, calls go directly to voicemail without ringing. Set it to at least 10 seconds.
- Click Save.
If the After value is already set to a sensible number of seconds, check the routing order next.
A member who cannot answer still uses up ring time. If your center rings staff in an order rather than ringing everyone at once, each entry in that order holds the call for its own ring timeout before the call moves on. Those timeouts come out of the same total the After value sets. Enough entries that no one is answering, and the budget is spent before the call reaches someone who is there β so the call lands in voicemail having rung, from the caller's side, for the full time and, from the team's side, not at all.
Employees who have left are the usual cause, because an entry can outlive the person in two ways:
- They are still in the routing order. Open Configure call routing and review the order and any group membership. Remove anyone who has left or who no longer takes calls.
- A physical phone is still assigned to them. An assigned desk phone keeps an employee eligible for calls even after they stop signing in, so removing the person from the order is not enough on its own β check that no device is still assigned to them. See Configure a physical phone device.
After changing the order, place a test call and confirm it rings a live handset before the forward time elapses.
Voicemail is not working
If voicemails are not being received:
- Navigate to HyperConnect > Settings > Voice.
- Scroll to the Missed Calls Forward To section.
- Verify that Forward to Voicemail is enabled.
- If it is not enabled, select the option and click Save.
- Place a test call and let it go to voicemail to verify the feature is working.
A phone tree's voicemail greeting repeats and no message is recorded
The steps above cover the center's missed-call voicemail. If the problem is a Voicemail node inside a phone tree, check the node itself.
- Open the phone tree flow and select the Voicemail node.
- Look for an Invalid configuration detected: warning on the node. If it lists Number on loop, set that value β a voicemail node needs it, and a flow missing it can still be saved.
- Confirm the greeting audio file is uploaded and is an MP3 under 5 MB.
- Check what the voicemail node connects to. A voicemail node's behavior once recording finishes is decided by its onward connection, and a node with nothing after it leaves the call with nowhere to go. Connect it to the node that ends the call, as described in Configure a phone tree (IVR).
- Save the flow and place a test call, letting it reach voicemail and leaving a short message.
Unable to transfer calls
If the transfer option is visible but transfers fail, the issue may require investigation from your support team. If the transfer option is missing entirely:
- Navigate to HyperConnect > Settings > Call Extensions.
- Confirm the employee's extension number is listed. If missing, click Associate Extension, select the employee, enter a unique 4-digit extension number, and click Add.
- Verify that the employee's device is properly associated in the Phone Device section.
- Confirm that the employee receiving the transfer also has a configured extension and an associated device.
Caller displays as unknown or private
When a call displays as "Unknown" or "Private," the caller is hiding their caller ID (for example, by dialing *67 before the number). The call may also be a spam or robocall. Advise employees not to answer persistent unknown calls and to report suspicious numbers.
Messaging issues
Daily message rate limit reached
If an employee sees a "Message Rate Limit" error when sending SMS, they have reached the daily messaging threshold. Daily limits are enforced per employee, per day:
- 600 messages per day for known guests (contacts in the system).
- 300 messages per day for unknown guests (new or unsaved contacts).
The limit resets at the start of the next day. If the employee needs to send more messages, another employee can send on their behalf.
A sent message shows only one status indicator and the guest says they never received it
HyperConnect displays two distinct message status indicators. Understanding what each one means helps you determine whether a delivery problem is on Zenoti's side or the carrier's side.
| Indicator | What it means |
|---|---|
| Single indicator (sent) | The message has left Zenoti and been handed off to the carrier network. Zenoti's responsibility ends here. |
| Confirmed-delivery indicator | The carrier has reported back that the message reached the destination device. This confirmation can lag by a wide margin depending on carrier propagation time. |
What to do when a message is stuck on the single indicator:
A message that shows only the sent indicator is almost always a propagation delay, not a fault. Zenoti has no visibility into what happens after the message leaves the platform β delivery depends on the carrier network, the guest's device, and regional routing. Before escalating, advise the guest to:
- Check that their device has signal and is not in airplane mode.
- Verify that their SMS inbox is not full.
- Confirm that the number on file is correct and can receive SMS.
- Check whether their carrier is experiencing a service outage.
If the guest confirms none of these apply and the message still has not arrived after several minutes, the issue lies with the carrier network. Zenoti cannot intervene once a message has been handed off to the carrier.
Note: A genuine send failure surfaces immediately as a Failed status, not as a stuck single indicator. If you see Failed, the message did not leave Zenoti β check the guest's phone number format and SMS opt-in status.
Physical phone device issues
All the phones are completely dead, not one misbehaving
The entries below cover one phone behaving badly. If all the phones have gone silent at once β no display, no dial tone, no ringing β treat it as a site problem before a Zenoti one, and do not start by restarting the phones. A phone that has lost its network, or its power, comes back in the same state.
Work through this first:
- Ask what else stopped working at the same time. Check the till area and the back office β payment terminals, printers, anything else plugged into the same network points. If equipment that has nothing to do with Zenoti also stopped at that moment, the fault is in the shared network or power, not in HyperConnect.
- Check whether computers and the web app are fine. If staff can still use Zenoti in a browser while every phone is dead, the two are on different paths β another sign the problem is local to the phones' segment rather than to Zenoti.
- Check the switch the phones are plugged into. Look for power at the switch and for link lights on the phone ports. Many phones draw their power from the switch itself (Power over Ethernet), so a switch with no power leaves them completely dead rather than showing an error. See Hardware and network requirements.
- If the switch is dead or has no link lights, this is one for whoever manages your network or your equipment supplier. Restoring the switch restores the phones; no change in Zenoti will.
- If the switch is healthy, computers are fine, and the phones are still dead, contact Zenoti Support with what you checked.
If the phones are reachable but calls sound bad, that is a different problem β see Network troubleshooting.
Phone rings once and disconnects, shows sync issues, or has a red flashing light
- Unplug the base station from both the power supply and the Ethernet cable.
- Wait 30 seconds.
- Reconnect the base station to the power supply and then to the Ethernet cable.
If the issue persists:
- On the handset, press OK.
- Select Status and click Base.
- Go to IPv4 and enter the IP address in a browser.
- Log in with the device credentials (default: admin / admin for new devices).
- Navigate to Settings > Upgrade.
- Click Reboot.
- After reboot, verify that the phone is connected.
Handset shows "Unregistered"
The handset needs to be registered with the base station. Follow the device manufacturer's registration instructions to pair the handset with the base.
Calls visible in the app but not ringing on the physical phone
The phone device may not be associated with the employee.
- Navigate to HyperConnect > Settings > Voice.
- Scroll to the Phone Device section.
- Verify that a phone is listed and associated with the correct employee.
- If no phone is listed, click Add Phone and enter the required details: manufacturer, model, MAC address, machine ID, a friendly name, and the employee who uses the device.
- Click Save.
- Reset the device: click Reset base for wireless phones or Reset config for wired devices.
- Wait 15 to 20 seconds for the device to sync with HyperConnect.
Change the employee associated with a phone device
Navigate to HyperConnect > Settings > Voice > Phone Device and update the employee assignment for the device.
Application issues
HyperConnect does not open from Zenoti
If the HyperConnect window does not launch from within Zenoti, incoming calls do not reach any device, and outbound calls fail with an error, these symptoms indicate a system-wide issue rather than an isolated problem.
- Confirm with multiple employees to verify whether the problem is widespread.
- If the issue affects all employees, notify your support team.
If the phones are also completely dead, check the site's own network first β see All the phones are completely dead, not one misbehaving.
HyperConnect does not work on a tablet or mobile device
Verify that the Zenoti mobile application is updated to the latest version. If the issue persists after updating, contact your support team.
HyperConnect does not work on desktop
- Verify that you are using a supported browser (Chrome or Edge, latest version).
- Clear browser cache and cookies.
- Disable browser extensions that may interfere.
- Try accessing HyperConnect from a different browser.
Network troubleshooting
VoIP call quality depends heavily on network conditions. If you experience poor audio, one-way audio, or dropped calls across multiple agents:
- Check bandwidth β HyperConnect requires at minimum 50 Mbps download / 20 Mbps upload. Each concurrent VoIP call uses approximately 100 Kbps in each direction.
- Use wired Ethernet β Wi-Fi introduces variable latency that causes audio jitter and one-way audio. Connect VoIP workstations via Ethernet cable, not Wi-Fi.
- Verify firewall ports β Ensure these ports are open: HTTPS (TCP 443), STUN/TURN (UDP 3478), and media (UDP 10000-60000).
- Check VPN β Some VPNs add latency or block UDP traffic, causing one-way audio or no audio. Test with VPN disabled. If quality improves, configure a VPN split tunnel for VoIP traffic.
- Dedicated VLAN β For businesses with 10+ agents, configure a dedicated VLAN for VoIP traffic with QoS priority to prevent bandwidth contention with guest Wi-Fi and POS (Point of Sale) systems.
For detailed hardware and network specifications, see Hardware and network requirements.
Understanding message status indicators
Zenoti can observe and influence a message only up to the point it leaves the platform. Once a message is handed off to the carrier, delivery depends entirely on the carrier network, regional routing, and the guest's device. Zenoti has no mechanism to retry, reroute, or confirm delivery beyond what the carrier reports back.
When a guest reports a missing message and the status shows the sent indicator, the practical next step is to advise the guest to check their device and carrier β not to escalate within Zenoti. If the status shows Failed, the message never left Zenoti and the issue is actionable on your end (check the phone number format, SMS opt-in status, and available SMS balance).
If the issue persists
If the troubleshooting steps above do not resolve your issue:
- Note the exact error message or behavior, the time it occurred, and which employees are affected.
- Check whether the issue is isolated to one agent/device or affects multiple agents.
- Contact Zenoti Support with the details collected. Include browser version, OS version, and network configuration if relevant.