Sign in

Week of May 24th

New updates: Secure forms, Messaging Platform SDK Announcement & Third Party Bots

Exact delivery dates may vary, and brands may therefore not have immediate access to all features on the date of publication. Please contact your LivePerson account team for the exact dates on which you will have access to the features.

The timing and scope of these features or functionalities remain at the sole discretion of LivePerson and are subject to change.

Announcement

Features

Communications for Messaging Platform SDK

Effective 1st Oct 2023, The Node Agent SDK has reached the end of its engineering and technical support lifecycle. This means that we will no longer be providing ongoing assistance, updates, or maintenance for the product.

While we cannot offer extensive engineering and technical support moving forward, we still want to ensure that our brands have access to troubleshooting assistance when needed. LivePerson will welcome any support cases related to the Node Agent SDK's troubleshooting.

Many brands have already switched over but for those who have not, we strongly recommend that brands transition to the new Messaging Platform SDK. 

 Messaging Platform SDK has replaced Messaging Agent SDK (aka Node Agent SDK) as the recommended method for interacting with the LivePerson Messaging service from a Node.js application.

For more information on how to quick-start with the new Messaging SDK, please click here.

For general information on the capabilities of the new Messaging SDK, click here.


Secure Forms for Messaging

Fixes

LivePerson works hard to ensure that our customers around the world can safely and securely use our platform.

The following time limitations apply on LivePerson secure forms:

  • If it takes more than 5 minutes from the moment a consumer clicks to open the secure form until it loads, the secure form will expire. This can occur as the result of a bad network connection or server failure. The 5 minute variable is configurable. 
  • The consumer can submit the secure form up to 30 minutes from the time they first open it. The 30 minute variable is configurable. 

Both variables can be set to any time limit between 1 and 86400 seconds. Please contact LivePerson in order to change the default values.

The impact will be on brands that use the default values mentioned above. Till now, consumers could still open the form after 5 min as long as it is within the 30 min timeout to submit it. In the new release, if a consumer clicks to open the form after 5 min they will now receive an error. This change will be rolled out gradually over the coming weeks. 

Third-Party Bots

Enhancements

Reduce latency when processing consumer messages

A delay in the processing bot responses was removed when handling long bot messages, resulting in a slightly improved response latency performance

IBM Watson Connector: Support for Date response type

The IBM Watson connector will now recognize Watson responses of type "Date" and forward them to the LivePerson Messaging system as rich content of type Date Picker.

Fixes

Introduce separate rate limit when handling files as bot responses

When sending an array of files as a consumer to a bot connected via Third-Party Bots, a spam protection might have mistakenly triggered, discarding several files. With this release, file messages are not ignored when being sent as a list. 

Fix race condition when joining a conversation and send a message via public API at almost the same time

There was a race condition where the message event was received before the conversation change event in the joinConversationCommand, resulting in missed processing of conversation details. As a fallback, the worker fetched details from the Messaging History API, which was slow and not always reliable, potentially leaving conversationDetails empty.

The fix now ensures up to 3 retries to verify that the conversation is connected before resorting to the Messaging History API, leading to the correct order of handling events.