Skip to main content


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

Sending Pulse messages for an email bot

Updated on January 12, 2022

Ensure that information reported in a triage case for an email bot is addressed in a timely manner by communicating with other application operators, by posting Pulse messages. A customer service representative (CSR) or other operator can send Pulse messages internally to specific users, or to everyone that has access to the email bot.

  1. Open a portal by performing one of the following actions:
    • To open the Case Manager portal, in App Studio, click Case Manager.
    • To open the Email Manager portal, in App Studio, click Case Manager, 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-291.
  3. In the right panel, click the Pulse tab.
  4. In the Pulse section, select the recipients of the message:
    • To send a message to everyone, in the Post list, select Post.
    • To send a message to specific users only, in the Post list, select Private post, and then in the field below, press the Down arrow key and select user names.
  5. In the Start conversation field below, enter the text for the Pulse message.
  6. Click Post.
What to do next: Once a CSR takes actions to address the issue reported in the triage case, for example, they spin off a related business case, send Pulse messages, and reply to the user, they can mark the triage case as completed. For more information, see Resolving triage cases.

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