Skip to main content

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

Save time while working in the Email Manager and Case Manager portals (8.5)

Updated on May 3, 2021

Customer service representatives (CSRs) now increase effectiveness working with Pega Email Bot™ by using several usability improvements in the Email Manager, Case Manager, and Case Worker portals. CSRs can reply to one or all the recipients by email, at any time. In addition, CSRs can also view the detected sentiment of each received email (positive, negative, or neutral), as well as view the sentiment pattern for the entire email thread. In the previous releases, the system showed only the sentiment analysis of the last received email in the email thread for a triage case.

The usability improvements add value to the email bot and help CSRs respond quicker to issues reported by customers. For example, when CSRs notice that the detected sentiment of an email for a triage case is negative, they can take immediate action by responding to the customer and escalating the issue to other relevant stakeholders by replying to all in the Email Manager portal.

The following figure shows the place in the Email Manager portal in which CSRs can view the sentiment of an email or an entire email thread:

The Email Manager portal showing the detected sentiment for emails
The Email Manager portal showing the detected sentiment for emails

For more information, see Understanding the email triage process and Replying to customers by email for an email bot.

  • Previous topic Build a chatbot and email bot in App Studio more easily (8.5)
  • Next topic Develop an IVA channel to chat across multiple social messaging platforms (8.4)

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