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.

Testing email routing conditions

Updated on April 5, 2022

When you configure an Email channel, define routing conditions to improve the responses that Pega Email Bot™ provides to an email that you receive. Before training and moving the email bot natural language processing (NLP) model to a production environment, you can use the test console to verify all the routing conditions for intelligent email routing.

Before you begin: Define routing conditions for the email bot based on email header content, NLP text analysis, or a when rule. For more information, see Configuring intelligent email routing.

You can test whether your email bot triggers the correct routing actions that you define for each routing condition case. In addition, you can verify sentiment detection.

  1. In the navigation pane of App Studio, click Channels.
  2. In the Current channel interfaces section, click the icon that represents your existing Email channel.
  3. In the Email channel, click the Behavior tab.
  4. Click Test.
  5. In the Test routing conditions window, verify a routing condition:
    1. Challenge criteria for a routing condition by entering the parameters of a sample email.
    2. Click Test.
    3. In the Outcomes section, verify that the correct action occurs for the routing condition.
    4. Click Close.
  6. Optional: To test all routing conditions, repeat step 5 for each routing condition.
What to do next: After verifying that each of the routing actions occurs when the criteria hold true, train the model for the email bot by using sample data. For more information, see Training data for the 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