Here are some common issues and suggested fixes:
Reauthorize the connection between Ultimate and Zendesk
Only Client Admins are able to reauthorize the connection.
To do this:
- Sign in to Zendesk as the virtual agent
- Sign in to the Ultimate Dashboard in a separate tab
- Toggle the Automation Engine off
- Navigate to Settings > CRM Integration and click Unauthorize Zendesk Chat
- On the same page, go to Integration Parameters and make sure the correct departments are selected
- Click Authorize Zendesk Chat
- Once authorization is completed, log OUT as the virtual agent in Zendesk.
- Toggle the Automation Engine back on.
Department selection
Chats are routed using departments/groups. If you have prechat form enabled in Zendesk Chat, make sure the hide department snippet is implemented correctly with the exact names of the departments/groups.
Sign out from Zendesk
The bot in our Dashboard can’t join the chat if there’s someone logged in using the bot account in zendesk. To solve this:
-
Sign out from Zendesk
-
Restart the bot by switching the toggle next to automation engine in CRM Integration on and off
Restart the bot
- Restart the bot by switching the Automation Engine toggle off in CRM integration.
- Give it a second before switching it back on again.
Reconnect the bot
It is important to login as the bot in Zendesk before authorizing. Try to reconnect by following the steps below:
-
Unauthorize in Dashboard
-
Log out of all Zendesk products
-
Sign in as the bot account in Zendesk Chat
-
Repeat the connecting steps
Check settings in Zendesk Chat
Settings > Agents
-
Is the Bot there?
-
Is it enabled?
-
Is it online?
-
Is there a department for the bot?
-
Is the bot the only agent in there?
-
Is it enabled?
-
Pre-chat form should be on
-
Required department should be enabled
Settings > Account > Operating hours
-
Is it switched On or Off?
- If you want the bot to be online only during certain hours, make sure to set it up here.
-
If it’s switched on, are the hours correct?
Settings > Routing
-
Escalation might fail when there are no agents available. Agent availability can be affected by Chat routing and Chat limit.
-
There are two options here:
-
Broadcast is preferred if the client doesn’t have “Skills-based routing” on.
-
Assigned is used when the client has “Skills-based routing” on. This can be checked by going to the Skills tab in the top left corner.
-
Chat limit can also be found on Settings > Routing
In Zendesk Support
Check if the bot account has access to Zendesk Chat
-
Go to Zendesk Support > Settings > People
-
Locate the bot by searching for its name
- Then enable Zendesk Chat by toggling the switch on
- You might see "Manage in Admin Center" instead of the toggle depending on your Zendesk version
- If that's the case follow this screenshot instead:
- You might see "Manage in Admin Center" instead of the toggle depending on your Zendesk version
In Dashboard
Make sure there’s nothing under Zendesk Tags in Integration parameters
This is only used IF the client uses Zendesk Skill routing. The “tag” here refers to “skill tag” and is NOT the same as chat tags that we use in dialogues. Read more about skill routing in this Zendesk guide.
The screenshot below is an opposite example. If this is what you see, click the trash can icon to remove it.
If you use Google Tag Manager
-
Does the widget look like the new one or legacy one?
- If it looks like the old one, then check the following:
-
Is the correct container / version being published?
-
In Tags, see if the old one is still enabled. If the client sees one that could be the old one, try to “pause” it and see if it changes anything - they should know how to do this.
-
Another way to see if it’s the legacy one spooking us, go to the website where the current chat widget is, right click to inspect the code.
-
Error - The bot sends an EOS error when turned on
Check if the client has IP Restrictions set up on their account:
-
Login to your zendesk
-
go to "zendesk chat"
-
click on "settings " --> "account"
-
click on the tab "security"
-
If the IP restriction is enabled, please add the following:
-
134.76.204.185 235.189.236.225 335.189.247.185 435.241.186.184 5104.199.104.45 6104.155.74.121 735.205.242.151 835.195.247.223 935.195.110.66
-
-
Error - The widget is missing from the website
If you don't see the widget on your website, please follow the Zendesk article below: