Difference between revisions of "Sending automated emails using new case template framework"

From PegaWiki
Jump to navigation Jump to search
(First draft)
Tag: Visual edit
 
(Image wrapping disabled)
Tag: Visual edit
Line 16: Line 16:
 
== Summary ==
 
== Summary ==
 
With the new case type templates, and the out-of-the-box case types that use these templates, you can modify the Send intake notification template in the Intake stage and the Send resolution notification template in the Resolution stage. The image below shows the Send intake notification shipped OOTB. Similar automatic notification steps can be added to various stages in a case life cycle.  
 
With the new case type templates, and the out-of-the-box case types that use these templates, you can modify the Send intake notification template in the Intake stage and the Send resolution notification template in the Resolution stage. The image below shows the Send intake notification shipped OOTB. Similar automatic notification steps can be added to various stages in a case life cycle.  
[[File:Automated email notification.png|left|826x826px|Notification email]]
+
[[File:Automated email notification.png|826x826px]]
  
 
As a best practice, customer service ships email templates out-of-the-box(OOTB). In this article we showcase how any outbound email can leverage the templates and factors to consider for outbound emails.  
 
As a best practice, customer service ships email templates out-of-the-box(OOTB). In this article we showcase how any outbound email can leverage the templates and factors to consider for outbound emails.  

Revision as of 05:17, 9 September 2020


Curator Assigned
Request to Publish
Description
Version as of
Application
Capability/Industry Area

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ Please Read Below ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Enter your content below. Use the basic wiki template that is provided to organize your content. After making your edits, add a summary comment that briefly describes your work, and then click "SAVE". To edit your content later, select the page from your "Watchlist" summary. If you can not find your article, search the design pattern title.

When your content is ready for publishing, next to the "Request to Publish" field above, type "Yes". A Curator then reviews and publishes the content, which might take up to 48 hours.

↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓ The above text will be removed prior to being published ↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓↓

Summary[edit]

With the new case type templates, and the out-of-the-box case types that use these templates, you can modify the Send intake notification template in the Intake stage and the Send resolution notification template in the Resolution stage. The image below shows the Send intake notification shipped OOTB. Similar automatic notification steps can be added to various stages in a case life cycle. Automated email notification.png

As a best practice, customer service ships email templates out-of-the-box(OOTB). In this article we showcase how any outbound email can leverage the templates and factors to consider for outbound emails.

Adding outbound email notification using the case template[edit]

  • Add a new notification process
  • Reuse OOTB email templates

Best practices to consider with email notification template[edit]

  • Email clients: Customer service considers some of the popular email clients like outlook, gmail and aws mail. These email clients present peculiar challenges when HTML rendering is enabled. The formatting errors in the clients has to be tested.
  • Email client form factor: The web and mobile form factors are considered. Also the dark mode in mobile has to be considered for the way the email is rendered.
    • Web look-n-feel.
Web-gmail-Intake-template.png
    • Mobile look-n-feel
    • Pixel4XL-intake.jpg
  • Subject line:
  • First line of email
  • Header logo
  • Store images on content delivery network (CDN)
  • Information blocks
  • Disclaimer