How can I troubleshoot issues with Zendesk Talk? What are your Talk troubleshooting tips?
All web-based software can experience performance issues relating to the connections and environment in which it operates. Existing system or connection issues may not be as noticeable during normal ticketing, but these issues can be much more pronounced with the additional demands of a telephony connection such as Zendesk Talk.
To help you deal with such issues, we have compiled a list of common troubleshooting steps to try first.
- Problems with Voice quality (delays, echoes, dropped calls)
- Numbers and billing
Problems with voice quality (delays, echoes, dropped calls)
- Issues with Talk call quality can sometimes be traced to a disruption of Twilio services, as this is the system handling our Talk connections. To determine the status of Twilio’s servers, visit the Twilio Status Page.
- Review the ports on your network Firewall. Verify that you have the following ports open with your network administrator:
TCP: 80, 443
- Have your affected agents go to Twilio WebRTC Diagnostics and review the resulting information. This page points to incompatibilities with your system setup or browser configuration.
- Have your affected agents try another headset and microphone and review their sound card settings.
- Have your affected agents use another browser. Most browsers use WebRTC for connections with Zendesk Talk. If the issue is with Chrome, ask your agents to test their WebRTC using the WebRTC Troubleshooter.
If you are still unable to determine the cause of your quality issues, contact the Zendesk support team providing the information listed below.
- A screenshot of the information at Support Details from an agent who is experiencing quality issues.
- A ticket example where call quality was an issue.
For more information, see How can I improve the quality of calls using Zendesk Talk?.
Receiving an EC# error
EC# errors are often caused by your network or router configuration. They represent an issue with Zendesk Talk not having an adequate network connection. This can occur anywhere along with the network, but often they are the result of local network limitations, or from a computer that does not meet the minimum requirements to make the connection.
To troubleshoot an EC# error:
- Zendesk recommends you use a browser that supports WebRTC.
- Review the WebRTC Port Requirements:
To use WebRTC, ensure that the following ports are not blocked:
TCP: port 80 and 443
UDP: all ports between 10,000 and 20,000
If you are still experiencing EC# errors, contact the Zendesk support team providing a screenshot of your firewall and router settings showing these open ports.
Zendesk Talk resetting to Offline status
Refreshing your page causes the agent to be set to unavailable for Talk. The agent needs to manually reset themselves to become available. Do not refresh your page in your browser when you wish to be available for calls.
Numbers and billing
Billing a spoke account for Zendesk Talk with multi-brand
With the current multi-branding setup, a credit card cannot be added to a spoke account. Billing is done through the hub account, and the spokes are sponsored. Because our billing system does not allow a credit card on spoke accounts for use with Talk, you need to purchase credits in advance by contacting your account manager in our Sales team.
Your Zendesk Talk number will expire in 7 days
Zendesk Talk reclaims unused phone numbers after 60 days of no activity. If your phone number hasn’t been used within that time, you will receive an email notifying you that your number will expire in 7 days. If you are still using this Talk number, you can prevent the deactivation by simply calling your Zendesk Talk number. Any call activity will prevent the number from being deactivated. However, if you haven’t used the number in 60 days you may want to consider canceling this support channel given the low amount of use.
For more information, see Zendesk Talk billing FAQ.