Skip to main content


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

Adding a conversational channel to a case type process

Updated on July 22, 2021

To improve the accuracy of Pega Intelligent Virtual Assistant™ (IVA) responses to a case, add a conversational channel to a process for a case type. You can also define the conditions that control when the conversation begins in the IVA.

For example, you can add an IVA for Web Chatbot to the car insurance case type. The system creates a parallel process for this IVA channel and, as a result, you can later define a set of simple questions to collect information for a car insurance case.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click Life cycle.
  3. Click the stage to which you want to add a conversational channel:
    • To add a conversational channel to the Create stage, click MoreAdd create processChannel name.
    • To add a conversational channel to any other stage, click MoreAdd channel processChannel name.
    Result: A parallel process for the IVA channel is added to the stage.
  4. Optional: To define the conditions that control when the conversation begins, update the process settings:
    1. On the Workflow tab, click the parallel process for the IVA channel.
    2. Select Custom condition, and then define the condition that determines when the conversation in the IVA starts.
      The custom condition must reference the pxActiveChannel property for the conversational channel.
  5. Click Save.
Result: At run time, the system asks a series of questions to collect information about a Pega Platform case.
What to do next: Add questions to the IVA conversation. For more information, see Adding questions to a conversation.

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