Routing email based on content

4 Tasks

15 mins

Pega Customer Service 8.8

Pega Customer Service '24.2 Pega Customer Service '24.1 Pega Customer Service '23 Pega Customer Service 8.7 Pega Customer Service 8.6 Pega Customer Service 8.5 Pega Customer Service 8.4

Visible to: All users

Intermediate

Pega Customer Service 8.8

English

Scenario

U+ is a major company in the financial industry that wants to improve engagement with customers. U+ has recently opened an email channel where customers can initiate contact for any needs or issues. Issues include administrative emails (for example, an address or email change), transaction disputes, and complaints. Due to the large volume of incoming emails, U+ has decided to use AI and use intelligent email routing to simplify their work.

Currently, only a basic email routing system is in place — all emails are routed to a single department. A human must scan through the email and manually route it to the appropriate department. Also, several entities, such as account numbers and email addresses, are extracted.

In this phase of the implementation, U+ wants to set up automatic routing for two topics. Emails detected as address changes must be routed to the Account Maintenance department, and emails detected as transaction disputes must be routed to the Dispute Transactions department.

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

Role	User name	Password
Email Client user	Customer1	password
Customer Service Representative	CACSR	password123!
Customer Service Application Administrator	CSAppAdmin	password123!

Your assignment consists of the following tasks:

Task 1: Send emails to test current routing rules

As a customer, send two emails to U+. In the first email, you request an address change. In the second email, you dispute a transaction.

Task 2: Verify that the emails are routed to the same queue

As a Customer Service Representative, verify that both emails are routed to the same work queue. Also, notice that the current system can already use text analytics to detect the Account Address Change topic in the email requesting an address change.

Task 3: Add a new topic and configure keywords

As a CS Application Administrator, add a new topic called Dispute Transaction, which is valid when the keywords wrong, invalid, false, credit card, transaction are found.

Task 4: Route emails based on the topic detected

Configure the email interface to route emails to Account Maintenance department when the topic detected is Account Address Change and to route emails to the Transaction Disputes department when the topic detected is Dispute Transaction.

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

• Log In

Challenge Walkthrough

Detailed Tasks

1 Send emails to test current routing rules

1. Open the exercise system landing page, and then click Email.
2. Log in as the Email client user with user name 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.

   To: [email protected] Subject: Moving to a new house Body: Dear U+, My customer number is: 123456789. I would like to inform you that I have a new address: 222 West Las Colinas Blvd., Irving, TX 75039, USA. Also, I have a new email address: [email protected] Cheers, Sara

5. Click Send message.
6. Compose the second email.

   To: [email protected] Subject: Something went wrong Body: Dear U+, I am a very happy customer of yours. I always had good experiences. Last month, however, I have noticed an invalid transaction. The amount is small, but could you please check? Again, in general, I am happy with your services. Cheers, Sara

7. Click Send message.
8. In the left pane, click Log off, and then click Log off again to leave the email client.

2 Verify that the emails are routed to the same place

1. Log in as a Customer Service Representative with user name CACSR using password password123!.
2. At this time, the user does not have any assigned cases in the My Cases tab. Click the My workbaskets tab.
3. In the View Queue for list, select Inbound correspondence.
4. Verify that two cases are created for the emails sent. This occurs because the Intelligent routing is set up for all types of emails to be routed to a single queue: Inbound correspondence.
   Note: It can take up to 2 minutes for the case to get created after you send the email.

5. In the Inbound Correspondence queue, click the Moving to a new house case.
6. In the case, click the See more icon next to Customer1.
   
   
   Note that the email is correctly categorized as Account address change and that entities like the account number and email address are identified.
   
7. On the tab, click the Close Tab icon to close the case.
8. In the My workbaskets tab, click the Something went wrong case.
9. In the case, click the See more icon next to Customer1.
   
   
   Notice that no topic is detected.
   
10. In the upper-right corner, click CC > Logout.

3 Add a new topic and configure keywords

1. Log in to App Studio as CS Application Administrator with user name CSAppAdmin using password password123!
2. In the navigation pane of App Studio, click Channels.
   
3. On the Channels landing page, click MySupport to open the email channel configuration.
4. In the MySupport channel, click the Behavior tab. Notice the configured case types, including Account address change.
5. In the Suggested cases section, click Add suggested case.
6. In the Case type list, select Dispute transaction.
7. In the Text analysis tab, in the Approximate match field, make sure that the following keywords are entered: wrong, invalid, false, credit card, transaction.
8. Click Submit to add the keywords.
9. Click Save to update the configuration.
10. In the upper-right, click Test and retest the email:
    1. Use any value for the From (email), To (email) and From (name) fields.

       To: [email protected] Subject: Something went wrong Body: Dear U+, I am a very happy customer of yours. I always had good experiences. Last month, however, I have noticed an invalid transaction. The amount is small, but could you please check? Again, in general, I am happy with your services. Cheers, Sara

    2. Note that the topic is Dispute Transaction.

11. Click Close to close the Test routing conditions area.

4 Route emails based on the topic detected

1. In the Intelligent routing section, click Add condition.
   Note: Observe the routing configuration for all emails. They are currently routed to a single queue: Inbound Correspondence.
   
2. In the Action list, select Route to work queue.
3. From the Value list, select Account Maintenance.

Tip: In a value field like this, just place the cursor in the field and press the down arrow button to select a valid value from the list.

5. In the When list, select NLP > Topic.
6. To the right of the condition drop-down list, click in the text box, and then enter or select Account Address Change.
7. Similarly, route the topic Dispute Transaction to the TransactionDisputes work queue.
   
8. In the header of the MySupport channel, click Save.
9. Click Test and retest the two emails.
10. In the Outcomes section, verify that the email requesting an address change is routed to the AccountMaintainance work queue, and the email disputing a transaction to the TransactionDisputes work queue.

---

---

Available in the following mission:

• Email Bots for Pega Customer Service v5