Deploying AutoCompose for LivePerson

​

Overview

This page describes how to Integrate AutoCompose in your LivePerson application.

​

Integration Steps

There are four parts to the AutoCompose setup process. Use the links below to skip to information about a specific part of the process:

1. Install the ASAPP browser extension on all agents’ desktop (via a system policy or using your company’s existing deployment processes)
2. Configure the LivePerson organization centrally using an administrator account
3. Setup agent/user authentication through the existing single sign-on (SSO) service
4. Work with your ASAPP contact to configure Auto-Pilot Greetings, if desired

​

Requirements

Browser Support

ASAPP AutoCompose is supported in Google Chrome and Microsoft Edge

• NOTE: This support covers the latest version of each browser and extends to the previous two versions

Please consult your ASAPP account contact if your installation requires support for other browsers

LivePerson

ASAPP supports LivePerson’s Messaging conversation type

SSO Support

The AutoCompose widget supports SP-initiated SSO with either OIDC (preferred method) or SAML.

Domain Whitelisting

In order for AutoCompose to interact with ASAPP’s backend and third-party support services, the following domains need to be accessible from end-user environments:

Policy Check

Before proceeding, check the current order of precedence of policies deployed in your organization. Platform-deployed policies (like Group Policy Objects) and cloud-deployed policies (like Google Admin Console) are enforced in a priority order that can lead to lower-priority policies not being enforced.

• If installing the ASAPP browser extension via Group Policy Objects, set platform policies to have precedence over cloud policies.
• If installing the ASAPP browser extension via Google Admin Console, set cloud policies to have precedence over platform policies. For more on how to check and modify order of precedence, see policy management guides from Google Enterprise.

​

Integrate with LivePerson

​

1. Install the ASAPP Browser Extension

Customers have two options for installing the AutoCompose browser extension:

A. Group Policy Objects (GPO)

B. Google Admin Console

​

A. Install Group Policy Objects (GPO)

Customers can automatically install and manage the ASAPP AutoCompose browser extension via Group Policy Objects (GPO). ASAPP provides an installation server from which the extension can be downloaded and automatically updated.

The Customer’s system administrator must configure GPO rules to allow the installation server URL and the software component ID. Through GPO, the administrator can choose to force the installation (i.e., install without requiring human intervention).

The following policies will configure Chrome and Edge to download the AutoCompose browser extension in all on-premise managed devices via GPO:

Each Policy Name above links to documentation that describes how to set the values with the proper format depending on the platform.

Figure 2 shows example policy files for the Windows platform. The policy adds the URL ‘https://*.asapp.com/*’ as a valid extension install source, allows the extension ID ‘bfcmlmledhddbnialbbdopfefoelbbei’, and forces the extension installation.

Google Chrome:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist]
"1"="bfcmlmledhddbnialbbdopfefoelbbei"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallSources]
"1"="https://*.asapp.com/*"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist]
"1"="bfcmlmledhddbnialbbdopfefoelbbei;https://app.asapp.com/autocompose-liveperson-chrome-extension/updates”

Microsoft Edge:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallAllowlist]
"1"="bfcmlmledhddbnialbbdopfefoelbbei"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallSources]
"1"="https://*.asapp.com/*"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist]
"1"="bfcmlmledhddbnialbbdopfefoelbbei;https://app.asapp.com/autocompose-liveperson-chrome-extension/updates”

Figure 2: Example policy files to install the AutoCompose browser extension in Google Chrome and Microsoft Edge browsers respectively (Windows Registry)

​

B. Install via Google Admin Console

For Google Chrome deployments, customers can install and manage the ASAPP AutoCompose browser extension using Managed Chrome Device policies in the Google Admin console. The Customer’s system administrator must set up the AutoCompose browser extension through the Google Admin console by creating a custom app and configuring the extension ID and XML manifest URL. Through managed Chrome policies the administrator can choose to force the installation (i.e. install without requiring human intervention).

In order to have Chrome download the ASAPP hosted extension in all managed devices through the Google Admin console:

1. Navigate to Device management > Chrome.
2. Click Apps & Extensions.
3. Click on Add (+) and look for Add Chrome app or extension by ID option.
4. Complete the fields using the values provided below. Be sure to select the From a custom URL option.

Please check Google’s Managing Extensions in Your Enterprise for more information.

Testing

The following two checks on a target machine will verify the extension is installed correctly:

1. The extension is force-installed in the browser a. Expand the extension icon in the browser toolbar. b. Alternatively, navigate to chrome://extensions/ or edge://extensions/ and look for ‘ASAPP Extension’ c. Alternatively, navigate to edge://extensions/ and look for ‘ASAPP Extension’
2. The extension is properly configured a. Click the extension icon and validate that the allowlist and denylist values in the extension’s options are as they were set. b. Alternatively, navigate to chrome://policy and search for the extension policies. c. Alternatively, navigate to edge://policy and search for the extension policies.

​

2. Configure LivePerson

Before You Begin

You will need the following information to configure ASAPP for LivePerson:

• The URL for your custom widget, which will be provided to you by ASAPP

• Credentials to login to your LivePerson organization as an administrator

Configuration Steps

1. Add New Widget
   • Open the LivePerson website and login as an administrator.
   • Go to ‘agent workspace’ and click Night Vision, in the top right:
   • Click +, then Add new widget.
2. Enter Widget Attributes
   • Fill in the Widget name as ‘ASAPP’
   • Assign the conversation skill(s) to which ASAPP is being deployed in the Assigned skills dropdown menu.

• Enter the URL that contains the API key you were provided by your ASAPP account contact for your custom widget in the URL field.

• Click the Save button.

3. Move Widget to Top
   • Click the Organize button
   • Scroll down to the ASAPP widget, and click the Move top button:
   • Click the Done button
4. Enable Pop-in Composer
   • In the Agent Workspace, click the nut icon (similar to a gear shape) next to the + icon at the bottom of the AutoCompose panel widget.
   • Enable the Pop-in Composer option.

Press the escape key and reload the page to see the changes; the ASAPP widget should now be available across your LivePerson organization

Upon login to the Agent Workspace, the ASAPP widget for AutoCompose will appear in place of the standard LivePerson composer, underneath the conversation transcript. By default, the response panel for AutoCompose will appear to the right of the conversational panel.

​

3. Set Up Single Sign-On

ASAPP handles authentication through the customer’s SSO service to confirm the identity of the agent.

ASAPP acts as the Service Provider (SP) with the customer acting as the Identity Provider (IDP). The customer’s authentication system performs user authentication using their existing user credentials.

ASAPP supports SP-initiated SSO with either OIDC (preferred method) and SAML. Once the user initiates sign-in, ASAPP detects that the user is authenticated and requests an assertion from the customer’s SSO service.

Configuration Steps for OIDC (preferred method)

1. Create a new IDP OIDC application with type Web

2. Set the following attributes for the app:

   Attribute	Value*
   Grant Type	authorization code
   Sign-in Redirect URIs	Production: https://api.asapp.com/auth/v1/callback/\{company_marker\} Sandbox: https://api.sandbox.asapp.com/auth/v1/callback/\{company_marker\}-sandbox

   *NOTE: ASAPP to provide company_marker value

3. Save the application and send ASAPP the Client ID and Client Secret from the app through a secure communication channel

4. Set scopes for the OIDC application:

   • Required: openid
   • Preferred: email, profile

5. Tell ASAPP which end-user attribute should be used a unique identifier

6. Tell ASAPP your IDP domain name Configuration Steps for SAML

7. Create a new IDP SAML application.

8. Set the following attributes for the app:

   Attribute	Value*
   Single Sign On URL	Production: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml/endpoint/clients/asapp-saml Sandbox: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml-sandbox/endpoint/clients/asapp-saml-sandbox
   Recipient URL	Production: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml/endpoint/clients/asapp-saml Sandbox: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml-sandbox/endpoint/clients/asapp-saml-sandbox
   Destination URL	Production: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml/endpoint/clients/asapp-saml Sandbox: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml-sandbox/endpoint/clients/asapp-saml-sandbox
   Audience Restriction	Production: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml/endpoint/clients/asapp-saml Sandbox: https://sso.asapp.com/auth/realms/standalone-\{company_marker\}-auth/broker/saml-sandbox/endpoint/clients/asapp-saml-sandbox
   Response	Signed
   Assertion	Signed
   Signature Algorithm	RSA_SHA256
   Digest Algorithm	SHA256
   Attribute Statements	externalUserId: {unique_id_to_identify_the_user}

   *NOTE: ASAPP to provide company_marker value

9. Save the application and send the Public Certificate to validate Signature for this app SAML payload to ASAPP team

10. Send ASAPP team the URL of the SAML application

​

4. Configure Auto-Pilot Greetings

If you so choose, you can work with your ASAPP contact to enable Auto-Pilot Greetings in your AutoCompose installation.

Auto-Pilot Greetings automatically generates a greeting at the beginning of a conversation, and that greeting can be automatically sent to a customer on your agent’s behalf after a configurable timer elapses. 

Your ASAPP contact can:

• Turn Auto-Pilot Greetings on or off for your organization
• Set a countdown timer value after which the Auto-Pilot Greeting is sent if an agent does not cancel Auto-Pilot by typing or clicking a “cancel” button
• Set the global default messages that will be provided for Auto-Pilot Greetings across your organization (note that agents can optionally customize their Auto-Pilot Greetings messages within the Auto-Pilot tab of the AutoCompose panel)

​

Usage

​

Customization

​

LivePerson

For LivePerson, the standard process is to download ASAPP AutoCompose as a standalone widget. In the case that you already have your own LivePerson custom widget, ASAPP also provides the option for you to embed our custom widget inside your own custom widget, thus economizing on-screen real estate.

Conversation Attributes

Once the ASAPP AutoCompose widget is embedded, LivePerson shares the following conversation attributes with ASAPP: customer name, agent name and skill.

ASAPP can use name attributes to populate values into templated responses (e.g. “Hi [customer name], how can I help you today?”) and to selectively filter response lists based on the skill of the conversation.

Conversation Redaction

When message text in the conversation transcript is sent to ASAPP, ASAPP applies redaction to the message text to prevent transmission of sensitive information. Reach out to your ASAPP account contact for information on available redaction capabilities to configure for your implementation.

​

Data Security

ASAPP’s security protocols protect data at each point of transmission from first user authentication, to secure communications, to our auditing and logging system, all the way to securing the environment when data is at rest in the data logging system. Access to data by ASAPP teams is tightly constrained and monitored. Strict security protocols protect both ASAPP and our customers.

The following security controls are particularly relevant to AutoCompose:

1. Client sessions are controlled using a time-limited authorization token. Privileges for each active session are controlled server-side to mitigate potential elevation-of-privilege and information disclosure risks.
2. To avoid unauthorized disclosure of information, unique, non-guessable IDs are used to identify conversations. These conversations can only be accessed using a valid client session.
3. Requests to API endpoints that can potentially receive sensitive data are put through a round of redaction to strip the request of sensitive data (like SSNs and phone numbers).

​

Additional Considerations

​

Historical Conversation Data for Generating a Response List

ASAPP uses past agent conversations to generate a customized response list tailored to a given use case. In order to create an accurate and relevant list, ASAPP requires a minimum of 200,000 historical transcripts to be supplied ahead of implementing AutoCompose.

For more information on how to transmit the conversation data, reach out to your ASAPP account contact.

​

LivePerson

ASAPP uses a browser extension to replace the LivePerson composer with the ASAPP composer. In the unlikely event that the DOM of the LivePerson composer or its surrounding area changes, the LivePerson composer may no longer be replaced by the ASAPP composer.

In this case, the CSR has the option to toggle the ASAPP composer so that it ‘retreats’ into the ASAPP Custom Widget. In such a case, the ASAPP composer will continue to be fully functional, even if it is no longer ideally placed just below the LivePerson chat history.

In order to quickly restore the placement of the ASAPP composer directly beneath the LivePerson chat log, ASAPP deploys its extension so that the extension’s configuration is pulled down from our servers in real-time. If the LivePerson DOM does change, we can deploy a fix rapidly.