Skip to main content

Creating a Web Chatbot channel

Suggest edit Updated on July 22, 2021

Create Pega Intelligent Virtual Assistant™ (IVA) for Web Chatbot so that users can interact with a Pega Platform application to answer questions, report an issue, or step through a process by sending messages in an embedded chat window. For example, with the IVA for Web Chatbot, users can create a case to inquire about a car price estimate or book a flight.

Before you begin: Update the Pega Platform application access group for an IVA for Web Chatbot. For more information, see Updating the access group for an IVA channel. Note: An IVA for Web Chatbot takes advantage of similar bot capabilities that are available in the IVA for Facebook. However, you have full control over the end-to-end communication and no additional accounts or third-party installation is necessary.
Design Patterns: To learn about configuring authentication for the IVA for Web Chatbot, see Authentication in Web Chatbot.
  1. In the navigation pane of App Studio, click Channels.
  2. In the Create new channel interface section, click Web Chatbot.
  3. In the Details section, in the Channel interface name field, enter a name for your channel.
  4. Optional: To describe the purpose of the channel, in the Description field, enter a short description of your IVA.
  5. In the channel, click the Connection tab.
  6. In the Template operator ID list, click the name of an existing Pega Platform operator to use as a template.
    The system uses this operator as a template to create all further accounts. Each account has a unique channel identifier set as its ID. For more information, see Template operator for IVA channel.
  7. Click Save.
  8. Embed a Web Chatbot channel chat window on a web page.
What to do next:
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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