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

From PegaWiki
Jump to navigation Jump to search
(Light editing for capitalization, double spaces, etc.)
Tag: Visual edit
(adjusting the product name)
Tag: Visual edit
Line 1: Line 1:
{{Design pattern|Title=Sending automated emails using new case template framework|Description=Best practices for outbound case emails|Version=8.5|Applications=Pega Customer Service|Capability Area=Notifications|Owner=}}
+
{{Design pattern|Title=Sending automated emails using new case template framework|Description=Best practices for outbound case emails|Version=8.5|Applications=Customer Service|Capability Area=Notifications|Owner=}}
  
 
With the new case type templates, and the out-of-the-box (OOTB) 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 that ships 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 (OOTB) 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 that ships OOTB. Similar automatic notification steps can be added to various stages in a case life cycle.  

Revision as of 17:24, 6 October 2020

Sending automated emails using new case template framework

Description Best practices for outbound case emails
Version as of 8.5
Application Customer Service
Capability/Industry Area Notifications



With the new case type templates, and the out-of-the-box (OOTB) 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 that ships OOTB. Similar automatic notification steps can be added to various stages in a case life cycle.

Automated email notification.png

Pega Customer Service ships out-of-the-box email templates that capture most of the best practices we describe below. Implementation guide captures the steps on how to add an outbound email notification using the case template. In this article we showcase how any outbound email can leverage the templates, and the factors to consider for outbound emails.

Best practices to consider with any outbound email notification[edit]

  • Email clients: Pega 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 have to be tested based on your audience's preferred email client. You can check current email client usage trends at http://emailclientmarketshare.com/
  • Email client form factor: The web and mobile form factors are considered. Also, Dark mode in mobile apps has to be considered in terms of the way email is rendered.
    • Web look-n-feel: Here the information is centered with other portions deliberately left blank. This is done so that the rendering is uniform across all form factors.

Web-gmail-Intake-template.png

  • Mobile look-n-feel: The full horizontal space is used in the mobile form factor.

Pixel4XL-intake.jpg

  • Subject line: Short ( <50 characters with spaces) subject lines are recommended. Short subject lines convey information quickly. The other added advantage is that notifications will also be impacted with the option to Avoid dynamic text in the subject, unless the length of dynamic text is fixed. Per HubSpot, 46% of emails are read on mobile devices. Information beyond 60 characters definitely gets chopped off.
  • First line of email: The first line of the email is displayed along with the subject line in the notifications for end customers. It is recommended to place the key information in the first line.
  • Header logo: Logos as images have been known to cause issues. It is best advised to use a combination of div and text (as used in the template) for easier rendering across all email clients. Some clients disable image download by default.
    • Tip: Store images on content delivery network (CDN), as most email clients allow links but not actual images as part of email communications.
  • Linking Knowledge Management (KM) articles: In the samples above you will see KM articles being showcased dynamically. However, one needs to be careful and have an upper limit on the number of articles used, as this may result in an overflow, especially with the mobile form factor. Limiting to a max of 3 knowledge articles can be considered a best practice.
  • Signatures; Multi-line signatures increase the length of emails. Text-based, single-line signatures (2 lines at best ) are recommended. Images in signatures are again not recommended. If images need to be used, CDN-hosted images are recommended.
  • Legal clearances and disclaimers: The samples shipped OOTB are for demo purposes only and the disclaimers are reference text only. However, before sending the emails, please consult the legal team and add all the required clearances. Emails with marketing content, invariably is subject to The CAN-SPAM Act of 2003. If applicable, as part of this act you may have to additionally implement unsubscribe button
  • Beware of spam filters: If you send email campaigns for long enough, you’ll eventually run into spam-filter issues. As a rough estimate, consider keeping emails 2 scrolls' length in a standard mobile phone.
  • Test, Test and Test!: Use A/B or Multivariate Testing to learn how changes to your content affects delivery and engagement.