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.

Resolving triage cases

Updated on July 22, 2021

Once a customer service representative (CSR) carries out all of the necessary actions during the email triage process, they can mark the triage case as completed by resolving it. By properly resolving triage cases, the CSR ensures that Pega Email Bot™ manages user emails more efficiently, and that only the currently unresolved requests from users are tracked.

For example, a CSR sends an email reply to the user, and then spins off a related business case, before resolving the triage case in the system.
Before you begin: Perform any of the following actions for a triage case:
  1. Open a portal by performing one the following actions:
    • To open the Case Manager portal, in Dev Studio, click Launch web interface, and then click Case Manager.
    • To open the Email Manager portal, in Dev Studio, click Launch web interface, and then click Email Manager.
  2. Open a triage case by performing one of the following actions:
    • To edit a triage case in the Case Manager portal, in the dashboard view in the list of cases, click a case name.
    • To edit a triage case in the Email Manager portal, in the list of emails, click an email.
    For example: Click ET-961.
  3. In the toolbar above the text of the email message, click Resolve.
    Result: The status of the triage case changes to resolved.
What to do next: If there are more triage cases to process, the CSR can address the other user requests saved in the email bot. For more information, see Triaging incoming emails.

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