Published Release Notes

Email bots now support multiple languages

You can now configure Pega Email Bot™ to perform text analysis, use training data and triage emails in multiple languages, for example, English, French, German, and Spanish. By detecting topics and entities from emails in different languages, the system can suggest the correct business case and provide an email response in the user's own language.

For more information, see Selecting languages for an Email channel and Enabling automatic language detection for text analysis.

Support for seamless transitions between IVAs and customer service representatives

To ensure the best user experience in chat sessions with a Pega Intelligent Virtual Assistant™ (IVA), customer service representatives (CSRs) can now step in and take control of a chat session multiple times, when the chatbot is not capable of correctly answering the user. After the user problem is resolved, the CSR can seamlessly switch control of the chat session back to the chatbot.

Unified Messaging Desktop integration with Pega Platform

You can now use the Pega Unified Messaging Desktop™ customer service solution with a Pega Platform™ application so that customer service representatives (CSRs) and other users, such as managers, can respond to user requests more quickly and in a more consistent manner. With integrated Pega Unified Messaging Desktop, CSRs can escalate user requests from Pega Intelligent Virtual Assistants™ (IVAs) by using case processing and artificial intelligence alongside Pega Customer Service™

For more information, see Develop a single IVA channel to chat across different messaging platforms.

Upgrading to the secure threading mechanism for email bots

In Pega Platform™ version 8.6, Pega Email Bot™ includes a more secure threading mechanism to help track emails from customers and other stakeholders in separate threads for an email triage case.

Upgrade impact

If you upgrade from Pega Platform version 8.5 or earlier, in which you configured an Email channel, perform the following steps to ensure that your system uses the new secure threading mechanism:

• Update the service email rule that the system uses to send an email reply as the initial acknowledgment.
• Update the email reply template in the data transform rule that the system uses when a customer service representative (CSR) sends the reply.

For more information about creating an initial acknowledgment email and email reply template, see Creating outbound email templates. For more information about the secure threading mechanism, see Use a secure threading mechanism in emails.

What steps are required to update the application to be compatible with this change?

For the initial acknowledgment email used by your email bot, update the service method for your email listener rule. On the Response tab for this service email rule, expand the Message contents section. In the Message data section, you specify the rule that defines the structure of the content of the email body. In Pega Platform version 8.6, you use for this purpose the pyEmailAcknowledgement correspondence rule that takes into account the selected built-in template. This template includes the security code tag that the system uses for the secure threading mechanism. If your application uses a different rule in the Message data section, update this definition to match one of the built-in correspondence template rules, for example, EmailAckTemplate_Clear.

The pySetEmailBotReplyTemplate data transform rule sets the name of the email correspondence rule that the system uses as the email reply template. If you do not want to use the default approach using the Classic, Cobalt, or Clear outbound email template themes, override this data transform rule to set the email correspondence rule name for the Param.ReplyTemplate target in the Source column field.

For more information about how to update the service email rule and the data transform rule to ensure that your system uses the secure threading mechanism, see Upgrading to the threading mechanism available in the 8.6 version.