Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Adding Web Chatbot custom responses

Updated on December 6, 2017

The Web Chatbot is a standalone widget that can be deployed on your website. This widget interacts with customers by using a text interface. The Web Chatbot can be used to help customers find information, send automated responses to their queries, and to create a case for escalations. You can configure custom responses for the Web Chatbot so that users, by entering a specific command in the chat window, perform an action such as view available menu options, log off from the current chat session, or restart the chat session. In most cases, simple text responses are used to create the Web Chatbot content.

  1. In Designer Studio, click the name of your application and then click Channels and Interfaces.
  2. Click a Web Chatbot channel interface.
  3. Click the Configuration tab.
  4. To add a custom response, click Add response.
  5. In the Name/Command field, enter or modify a user command for the response to provide.
  6. In the Response type list, click the name of the response to provide when a user enters a command.
  7. Optional: In the Response text field, enter the response text to display to the user. You can select a predefined response text by clicking Use existing.
  8. Optional: Add a command item to display in a menu:
    1. To add a command item, click Add response. To modify a command item, click its Configuration icon.
    2. From the Menu item list, click the menu command name.
    3. In the Label field, enter a label for the menu command item.
  9. Click Submit.
  10. Click Save.

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