Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Legacy Webchat to Web Messaging migration best practices

Updated on December 3, 2021

Legacy Webchat was deprecated in Pega Platform™ and Pega Customer Service™ 8.6 and de-supported in version 8.7. As its replacement, you must use Web Messaging in the Digital Messaging channel interface as its replacement. Contact your organization’s Pega account team to begin the migration process to Web Messaging if not already in progress.

Pega Customer Service Implementation Guide

Note: Pega Customer Service will sunset the Legacy Webchat servers on October 31, 2023.
Note: There are some feature differences between Web Messaging and Legacy Webchat. Some are related to the display of the chat window to your customers and to the functionality available to them. For example, support for forms is being added in Pega Infinity™ '23. There are also differences resulting from changes in later versions of Pega Platform and Pega Customer Service, in some cases, functionality that was available for Legacy Webchat in 7.x or early 8.x versions is no longer available as of 8.4 or later. For example, URL- based routing is one such difference. For more information on the differences and ways to address them, see Troubleshooting checklist for Legacy Webchat to Web Messaging migration.

To learn about the Legacy Webchat to Web Messaging migration procedure, see Migrating from Legacy Webchat to Web Messaging.

  • Previous topic Configuring audio notifications
  • Next topic Recommended process to migrate from Legacy Webchat to Web Messaging

Tags

Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us