Skip to main content

Configuring the Email Manager portal


2 Tasks

15 mins

Visible to: All users
Beginner Pega Platform 8.5 English
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.


The U+ Bank email bot is set up, and you must configure the Email Manager portal to manually triage any emails that do not match the intelligent routing criteria.

Use the following credentials to log in to the exercise system:


User name


System Architect



Your assignment consists of the following tasks:

Task 1: Set the confidence threshold

In the Intelligent routing, set the confidence threshold to 0.85 to evaluate true only when the confidence score of the topic is greater than or equal to this number.

Task 2: Configure the Email Manager portal and triage emails

In the Portals list, select Email Manager to add the Email Manager portal to your operator access group.

Challenge Walkthrough

Detailed Tasks

1 Set the confidence threshold

  1. Log in to App Studio as the System Architect with user name EmailBotDev using password rules
  2. In the navigation pane of App Studio, click Channels.
  3. Click My Email Bot to access the channel.
  4. In the My Email Bot channel, click the Behavior tab.
  5. In the Intelligent routing section, to the right of the Address Change when condition, click the Gear icon.
    CH27216-2-EN-intelligent routing
  6. Set the confidence threshold to 0.85 to evaluate as true only when the confidence score of the topic is greater than or equal to this number.
  7. Click OK.   
  8. Repeat steps 5-7 to set the confidence threshold of the Complaint when condition. 
  9. Save the channel.

2 Configure the Email Manager portal and triage emails

  1. In the navigation pane of App Studio, click Users > Access to configure the Email Manager portal and triage emails.
    CH27216-2-EN-08-CH27216-2-EN-EmailAccess Group
  2. In the Portals list, select Email Manager to add the Email Manager portal to your operator access group.
  3. Save the access group.
  4. In the header of App Studio, click Preview application to access the Email Manager portal from the list.
Note: Send a few emails that do not meet any of the intelligent routing conditions in your channel. Ensure that the Otherwise condition in your channel is routed to your work queue. Example: Route to work queue as AwaitingResponse.
CH27216-2-EN-otherwise condition

Any inbound emails that are not automatically processed by the intelligent routing conditions are displayed in the triage portal.

  1. Open the exercise system landing page, and then click Email.
    CH27216-2-EN-email portal
  2. Log in as the Email Client user with username customer1 and password password.
  3. In the left pane, click Mail to access the Inbox.
  4. In the header, click Write mail to compose a new email.
    CH27216-2-EN-write email
  5. In the To: field, enter [email protected]
  6. In the Subject: field, enter Add user.
  7. In the message field, enter the following content:


    Can you please add my spouse to my brokerage account?



  8. Click Send message.
  9. Create a second email, and once again send it to [email protected]
  10. In the Subject: field, enter Misplaced my card.
  11. In the message field, state that you lost your card and want a new one. You can use the below text:

    Hello! I’ve misplaced my card; can you send me another one?
  12. Click Send message.
  13. In the left pane, click Log off to leave the email client.
  14. In the Email Manager, select Awaiting Response from the list on the upper-left corner.
  15. Open any email and reply to the message, create a case, or route the email triage case to a new work queue.
    CH27216-2-EN-reply case1

Available in the following mission:

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice