Skip to main content


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

Replying to emails directly from Pega Sales Automation

Updated on May 10, 2021

Reply to emails directly from Pega Sales Automation to reduce context switching between Pega Sales Automation and Microsoft Outlook, and increase sales representatives productivity while performing daily tasks.

Pega Sales Automation Implementation Guide
Before you begin: Ensure that you configure the synchronization between Microsoft Exchange email and Pega Sales Automation. For more information, see Synchronizing Pega Sales Automation email with Microsoft Exchange.
To reply to emails as a sales representative, perform the following steps:
  1. In the User portal navigation pane, perform any of the following steps:
    ChoicesAction
    Reply to emails from Pulse
    1. Click Contact, Lead, or Opportunity
    2. Click the Pulse section to see any email exchanges.
    UI-Kit only: Replying to emails from the Emails screen
    1. Click Emails.
  2. Open any email, and then click either Reply or Reply all.
    Note: You cannot see emails that the sender has not shared publicly because, by default, only email recipients can see their content. To set emails as public, in the Cosmos design system, on any open contact, click ActionsMark as public. In UI-Kit, on any open contact, click Mark as public.
  3. Enter the necessary email details, select an email template if necessary, and then click Send.
    For more information about email templates, see Creating email templates.
  • Previous topic Sending emails by using the Microsoft Exchange web service
  • Next topic Email sentiment and NLP suggested actions

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