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.

Creating an Email channel

Updated on August 16, 2021

Ensure that your Email channel has integrations with necessary email accounts, and is properly configured for your system, for example, to support multiple languages. As a result, you ensure that users have an additional way to communicate with your application to ask for help or solve an issue.

For example, by creating an email bot for a travel agency you can help users book a flight by interacting with your application just by using email.
Before you begin: Set up an email account that you will use for the email bot.
  1. In the header of Dev Studio, click the name of the application, and then click Channels and interfaces.
  2. In the Create new channel interface section, click Email.
  3. In the Email channel name field in the Details section, enter a name for your Email channel.
  4. Optional: To explain the purpose of your email bot, in the Description field, enter a short description for the email bot.
  5. In the Email handling section, click Add email account, and then select an email account.
    You set up at least one email account for the Email channel so that users know which email address to send their requests to the email bot.
  6. Optional: To verify that you can use the email account that you selected, click Verify.Result: If the email account verification fails, you can view information about the reason why the process failed by clicking a link.
  7. If you want to define additional email accounts for the email bot, repeat steps 5 and 6.
  8. Optional: To enhance how information is presented in emails and triage cases and to enable rich HTML text for the email bot, in the Additional settings section, select the Allow rich text (html) in emails check box.
    Enabling this option enhances how important information in the email is presented in the system, for example, in triage cases displaying conversations details from users.
  9. In the Reference operator list, select a reference operator for your email bot.
    You select a reference operator so that the system automatically assigns the email triage case to a unique Pega Platform operator when an exception occurs. A reference operator is a Pega Platform user on behalf of whom service mails are created in the system.
  10. In the Languages list, select the languages in which the email bot interacts with users.
    You select the languages in which the email bot processes emails so that the system can perform text analysis and provide automatic responses in the correct language. By supporting multiple languages in an email bot, you increase the availability of your application to users who speak different languages. You configure reply email templates for each language separately. Note: By editing the pyGetDefaultLanguage data transform rule for the Data-Channel- class, you can select a default language other than English to use when creating an Email channel. For more information, see Overriding the default language for an Email channel.
  11. Click Save.
For example:
Email channel configuration for bank loan requests
The configuration tab for email channels showing configuration of a bank loan request email.
What to do next: Define Email channel behavior for the email bot. For more information, see Defining Email channel behavior.
  • Previous topic Implementing an email bot for an Email channel
  • Next topic Overriding the default language for an Email channel

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