Week of February 9th

Features

Rich content consumer events are forwarded to the bots

Rich content events will now be processed by Third-Party Bots and the data will be made available to all bots through the context data. Exactly which events are supported depends on the channel, e.g., on WhatsApp the consumer can now share its location with the bot. Rich content messages can be identified by the com.liveperson.bot-connectors.consumer.send-rich-content identifier in the message payload. The data of such a message can be found inside the lpEvent sent on the context payload.

Support Conversational Cloud vanity domains

So far the Third-Party bots UI could only be fully accessed inside the Conversational Cloud if it was running under a LivePerson Domain. In order to support vanity domains this limitation has been removed. Be advised that the Third-Party Bots API will stay reachable only from LivePerson Domains and vanity domains.

Enhancements

Support new version of the Medallia adapter

The Medallia adapter is able to send survey data asynchronously via the public API and disables all of Third-Party Bots static system messages on surveys except in case of internal errors. It also improves the information provided on survey conversation errors inside the bot dashboard.

Dedicated wizard step for survey bots

All survey bot settings not related to the AI vendor (the Medallia Adapter) have been moved to a separate step. In this step the bot manager can configure which survey App ID and last conversation skill the bot accepts post conversation dialogues. Additionally, the consumer-facing error message is now configurable in order to support addtional user cases, e.g. non-English surveys.

Fixes

Prevent already assigned agents from being reused

The list of available agents in the wizard has been showing already assigned agents since the last release. This is fixed now and an additional check was added to the API to prevent bots from being assigned if they are already in use even in case the API is accessed directly.

No override of authenticated SDEs with ‘null’ values

The consumer profile data can contain multiple SDEs of the same type. When merging these entries Third-Party Bots has accepted ‘null’ values as valid data in the past. With this fix ‘null’ values will no longer override properties of another SDE entry of the same type.

Features

The Agent Assist application—now called Conversation Assist—introduces several exciting changes to make it easier to set up recommendations and evaluate how well they are serving your agents.

First, it’s now faster to access the application, as you can now do so directly from the Conversational AI applications page.

Second, Conversation Assist’s new Home page includes a dashboard of rich, diagnostic analytics. Use the dashboard to get an at-a-glance, holistic understanding of when and how recommendations are offered and used.

Finally, we’ve redesigned the UI to make it more intuitive: You’ll find your knowledge bases and bots on two different tabs of the new Recommendation Sources page. From here you can easily turn these sources on and off and assign skills to them.

You’ll find settings that impact all your recommendation sources on a redesigned Settings page. Use this page to:

• Temporarily suspend all recommendations if you need to.
• Configure the maximum number of recommendations to serve at one time.
• Set the minimum scores that answers and bots should have for them to be offered as recommendations.
• Customize the messages sent to the consumer when a bot is added to and removed from a conversation.

Features

Watch this short, 45-second video to learn how to send us feedback on the Conversation Builder documentation. It's quick and easy. We value your feedback, so thank you in advance!