Wrong time or date shown in workspace
In the Conversational Conversational, the displayed time is the same as the user's PC's timezone configurations. It can be different for two users in the same account, if they are currently located in different timezones or their local computer time is custom configured with a different one.
Agent is not getting audio notifications for incoming conversations
- The Agent Workspace in the Conversational Cloud audio notification is muted.
- The agent’s browser is not set to “Play Sounds in Webpages”.
- Firstly check your agent status bar and un-mute sound, as per the image above
- If the agents browser is not set to “Play Sounds in Webpages”. The agent should turn audio on in their browser.
- For Chrome browsers, see Turn notifications on or off in Google Chrome Help.
- For other browsers, search the browser’s Help for instructions on turning on audio.
For Internet Explorer, follow these steps:
- Open Your Control Panel: The easiest way to open the Control Panel is to click on “Start” and then click on “Control Panel.”
- Open the Internet Options: Use the search box to find the “Internet Options” section of the Control Panel.
- Select the “Advanced” Tab: The Advanced Tab is usually on the far-right side of the Internet Options screen.
- Scroll Down to Multimedia: Scroll through the options until you see the section called “Multimedia.”
- Deselect the Play Sounds Option: Click to uncheck the option called “Play Sounds in Webpages.” This will turn off all sounds in your internet browsers.
- Turn Sounds On Again When You’re Ready: If you would like to resume listening to sounds on your internet browser, be sure to follow these steps again and check the “Play Sounds in Webpages” option once again.
Some agents can't see the conversation summary widget in their workspace
The conversation summary widget is configured via Engagement Attributes on the Skill level. The account had set their Visitor Journey engagement attribute to track Lead information for agents with certain skills. The agents who did not see the conversation summary widget were not assigned to any skills in that list.
Assign the agents one of the skills configured for Visitor Journey leads.
To edit the Visitor Journey engagement attribute:
- Log into the Conversational Cloud, and then click on the Campaign Builder. The footnote is displayed at the bottom of the page.
- In the footnote, click Data Sources. The Data Sources page is displayed.
- On the Data Sources page next to Visitor Journey click Configure.
- On the Visitor Journey page under Lead, select Submit By Agent.
- Select the skill(s) for which you want this feature to be available.
- Select the Engagement Attribute properties that will be displayed to the agent in the Agent Workspace by clicking Add field to widget. You must select at least one property.
- For each of the selected properties, enter a display name. This name will be displayed to the agent in the Agent Workspace.
- Click Save.
For more information on Conversation Outcomes and the Conversation summary widget, see Conversation Outcomes.
Why is there a delay in the delivery of agent messages?
Sometimes latency issues are experienced by users, such as agent statuses switching to away automatically, delayed delivery of agent messages to customers, etc.The affected agents were working in unsupported browser versions.
Update agent browser version. For a list of supported browsers, see system requirements and supported languages.
Why isn’t CoBrowse available to chat agents?
- Agents in chat do not have the CoBrowse icon available to them and therefore cannot initiate a CoBrowse session.
- The CoBrowse function for the account is not switched on in Night Vision.
- The agents are not assigned to a profile that includes CoBrowse permissions.
Why isn’t the scroll bar showing in the predefined content widget?
A setting that is configurable in the Mac OS X.
- Click the Apple menu at the top-left of the screen and select System Preferences.
- Click the General preferences pane (first one at the top).
- Under Show scroll bars select Always. The scroll bar will now display in the predefined content widget.
An agent’s status is AWAY, yet he/she is still receiving chats
The ACD setting of the agent’s LivePerson Conversational Cloud account is manual mode. In this mode, incoming chats ring for all agents who are logged in, regardless of their state (Away/Back Soon/Online).
When the ACD setting is manual, this is the expected behavior - it allows agent managers to get notifications and take chats when they feel their agents are overwhelmed.
Chats cannot be transferred from other agents to an agent who is in Away state.
Agents in Away state do NOT count toward the current available chat slots of a specific skill.
Why don’t agents see their Predefined Content?
The account’s admin/agent manager exported the predefined content, modified all the predefined content IDs in the exported file and then imported the predefined content from the modified file. During the import process all the predefined content items in the account were deleted because it could not locate them in the import file. The import process identifies items by their IDs and the IDs in the import file had been changed.
Do not modify IDs of predefined content items.
For more information, see Importing Predefined Content.
Why doesn’t our agent manager see all his groups on the Web History tab?
The agent manager is defined as the manager of the India call center group but not of the USA agent group.
A user on the account who has permissions to modify user settings, should change the agent manager’s permissions as follows:
- Go to the Users tab.
- Click the Agent Manager user in the list. The Edit user window opens.
- In the Manage groups field select the group you want the agent manager to manage.
- Click Save. After logging out of the Conversational Cloud and then logging in again, the agent manager will see both groups in the Web History.
Check out our Developer Center for more in-depth documentation. Please share your documentation feedback with us using the feedback button. We'd be happy to hear from you.