Skip to main content


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

Template operator for IVA channel

Updated on August 10, 2021

Each conversational channel (Alexa, Unified Messaging, or Web Chatbot) user that interacts with a Pega Platform application is mapped to a separate operator and a user account. This unique account is created automatically when a user interacts with Pega Intelligent Virtual Assistant™ (IVA) for the first time. The account is used in all subsequent interactions with the configured IVA channel.

The selected operator must at the minimum have the PegaRULES:User4 access role, taking into consideration the application settings, for example, providing access to the application's cases. For more information, see Standard access roles. Each operator that you define in the system, including a template operator, uses a language locale specified in the Localization section. Because each conversational channel uses a template operator, the chatbot works in the language that you specify in the operator locale setting.

The value selected in the Template operator ID list in the channel configuration specifies the name of an existing Pega Platform operator and is used as a template from which all accounts are created. Each account has a unique Alexa, Unified Messaging, or Web Chatbot channel identifier set as its ID. You need to distinguish these types of accounts in Pega Platform so that for each Alexa, Unified Messaging, or Web Chatbot channel instance, the account is unique. To do so, set the full name a template operator account to, for example, Web Chatbot Operator and add it to the designated operator group.

  • Previous topic Configuring on-premises or internal access only environments for Digital Messaging access
  • Next topic Defining conversational channel behavior

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