Skip to main content

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

Conversational channel user roles

Updated on May 15, 2023

Pega Platform users with different roles create, train, and build Pega Intelligent Virtual Assistant™ (IVA) and Pega Email Bot™, as well as triage cases. For example, a channel developer creates an Email channel and builds its behavior, by training the text analytics model to better detect the correct topics, language, sentiment, and entities. Once the email bot is in a production environment, a customer service representative (CSR) then triages the cases so that customer emails are promptly and correctly addressed.

Supported roles

The following are the main user roles for creating, defining, and managing IVAs and email bots in Pega Platform:

Channel developer
Channel developers are in charge of developing the email bots and IVAs that interact with an application, before they are moved to a production environment. Channel developers typically perform the following tasks:
Customer service representative (CSR)
CSRs interact with the application run time environment for email bots, and also directly with customers once the email bot is moved to a production environment. They use the Case Manager portal or the Email Manager portal for this purpose, to more efficiently address customer emails. Amongst other things, CSRs perform the following task:
Channel administrator
Channel administrators manage the IVAs and email bots for a Pega Platform application, once the IVA or email bot is in a production environment. An administrator works together with the channel developers to keep the system secure, operable, and error free. Administrators perform the following tasks:

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