System requirements

LivePerson is constantly expanding its matrix of supported operating systems and browser versions.

1. We fully support only the generally available (GA) browser versions.
2. To benefit from the full functionality of LivePerson, cookies must be enabled.

We have two primary levels of support for the items listed in the tables below:

Supported: Items marked with an asterisk ( * ) meet the minimum requirements, with no known issues. Any new bugs will be evaluated and resolved on a case-by-case basis.

Certified: Unmarked items have been tested thoroughly by LivePerson. We are committed to resolving any bugs or issues based on the SLAs defined across the Conversational Cloud.

Visitor side: mobile web requirements

The tables below list the browsers LivePerson supports for visitors on mobile web assets (smartphones and tablets).

Android

iOS

WebView

iOS and Android in-app browsers, or WebViews consistently have technical limitations that affect the ability of the LivePerson web messaging experience to function properly (engagements, web messaging window, etc.), and are currently not supported.

Visitor side: desktop requirements

The tables below list the browsers LivePerson supports for visitors on desktop web assets.

Windows

Mac

Visitor side: unsupported browsers

We do not support incognito/private browsing in any browser.
Some browsers are not supported at all due to experience or security reasons. When consumers arrive at your website from certain browsers, the Conversational Cloud will not display any chat buttons or invitations, for example, on:

• Internet Explorer 7, 8, 9, 10, 11
• Line browsers

The recommended browser for the LivePerson messaging workspace is Chrome.

Visitor side: unsupported browser extensions

Due to the technical needs of the Conversation Cloud platform on the client side, some browser extensions can not be supported.

Visitor side: Mobile SDK Requirements

The official support of the LP Mobile SDK version is for the latest version only at any given point in time. This is applicable for both iOS and Android SDK versions.
The support for new OS releases from Apple and Google (iOS and Android OS) for the LP SDK would be within max 6-8 weeks from the date of GA availability of the OS. Beta SDK release of the newer OS beta will be available before 2-4 weeks of the GA availability for the customers to try their hands on and report any early issues.

Latest releases

Please refer here: iOS and Android

Android

Android SDK v4.6.1 and below excludes AndroidX support [supports API 21-30]
Android SDK v5.0.0 and above includes AndroidX support [supports API 21-30]

The SDK uses the following libraries:

• Com.google.android.gms:play-services-maps:16.1.0
• Com.squareup.okhttp3:okhttp:3.9.1

iOS

The SDK is compiled as an XCFramework and was compiled with Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53) which means it will work with Swift version 5.2.4 and above. For more information on XCFramework, see this Apple documentation.

Official support for the latest iOS SDK versions will be N, N-1, and N-2 as shown in the table above. Official support for the LivePerson iOS SDK version is only for the current Swift version (N) and previous Swift version (N-1).

All iOS OS beta releases will be provided approximately 1 month before the actual GA for the purpose of compilation only (no bug fixes or new iOS features supported). Once the GA is released, we will accept requests for new iOS features. Currently, we only support Cocoapods dependency manager, frameworks can also be integrated manually using the XCFramework binary format. We do not support integration with Carthage or Swift package manager.

LivePerson workspace requirements

The tables below list the browsers that Agents, Agent Managers, Admins, and Campaign Managers can use when accessing the workspace.

Windows

Mac

Tab Discarding in Chrome

Desktop notifications

Conversational Cloud desktop notifications do not support the following browsers:

• Internet Explorer 11x

Reporting

Conversational Cloud BI Dashboards do not support the following browsers:

• Internet Explorer 11x
• Microsoft Edge

While these browsers do support Conversational Cloud they do not support, and will not support, the BI dashboard. Users accessing the BI dashboards using these browsers may experience unexpected behaviors, such as missing scroll bars. The data in the dashboards may seem incomplete or missing when reviewing it without using scroll bars. To overcome this and see the full data, users can use the keyboard arrows.

Bandwidth requirements

LivePerson workspace

• Initial download speed: approximately 6MB GZIPPED for complete Agent Workspace download (includes scripts, HTML, CSS, and images).
• Average rate per CCP per second: 10-15KB for data.
• Max rate per CCP per second: 1.2MB - 1.5M.
• Browser resource requirements: Typical agent activities with max 3 concurrent chats, client resource requirements can be summarized as:
  • Processor: Any 6th Gen Intel i3 processor. (i3-6098P is the lowest cost one and is more than sufficient)
  • RAM - 2G
  • Network - 1G

CoBrowse visitor side

• Recommended upstream bandwidth: 1500 Kbit/s.
• Large rendered websites > 2 MB (DOM tree) can lead to a significant delay until the website is fully visible to the CCP (waiting time of 15 sec. or more to view the page).
• Your website should make sparse use of background animations (animations without user interaction).

Citrix requirements

LivePerson recommends hosting up to 30 Agent users per Citrix server with the following specification:

• Hosted VMWare
• Internal network 10 GB
• Network to WAN 200/200 (Up/Down)
• 6 VCPU (2.2 GHz minimum)
• Memory 16 GB
• 256 Video Card Memory
• Windows Server 2012 R2
• Supported client: 
  • Xenapp 7.15

Upon the above set up the below describes the resource consumption for each profile:

• CPU for Agent Manager role - minimum of 4500 GHz per user
• CPU for each Agent role - minimum of 800 GHz per user
• CPU wise - 1 Manager = 5 agents
• Steady set up can be 1 Manager with 10 Agents

CPU resources should be calculated according to the above parameters.

The new device certification process

LivePerson examines new devices and operating systems on a case-by-case basis and adds them to our certifications process. The certification cycle of a new device or operating system LOE is approximately two business weeks. Every new device or operating system which enters the certification process removes another device or operating system from the certification list.

Requests by customers for certification of a new device or operating system will be examined by LivePerson’s Product House. If a device or operating system is not in our roadmap, a request should be made to LivePerson using the ER (enhancement request) process. Please contact your account manager for more details.