Skip to main content

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

Configuring the Web Chatbot

Updated on March 25, 2020
Important: Legacy Webchat previously known as Web Chatbot is deprecated. You can contact your account team to start the migration to Web Messaging.

With Web Chatbot customers can type their questions or requests into a chat window that is accessible from a customer-facing web page and then get answers and guidance. In situations where customers cannot self-serve, it is possible to escalate the interaction through chat to a relevant queue.

Pega Customer Service provides a sample web chatbot channel so that you can quickly get started with the web chatbot configuration. The sample chatbot channel consists of the most frequently used case types and response commands, such as greeting, help, escalate, and thank you, to enable your web chatbot to handle real-time problems. Natural language processing (NLP) is used to detect the sentiments and trigger the corresponding actions. Some sentiments, such as greetings, escalation, thank you and help, are detected using artificial intelligence (AI) models and not using keywords. The AI models are more flexible and can learn based on the past usage.

This saves you time when setting up an initial web chatbot channel and helps you to directly start configuring the web chatbot widgets using this pre-defined channel.

If you do not want to use the sample web chatbot channel, you can configure a new web chatbot channel. For more information about creating a web chatbot, see Creating the Web Chatbot channel.

Note: In Pega Customer Service version 8.6 and later, Web Chatbot is called Legacy Webchat.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us