Always-on Outbound Customer Engagement(Pega CPDC)

Share Post

Essential of Always Outbound :

Main Crux:

Poc — > Multiple Offer Email —→ Contact policy —> Volume Constraint —> File and DB template

Sending Offer Email:


1.Add Email treatment to Action


      1. Add Dynamic Flow

      1. Run primary Schedule


            1. Recurrences : Refresh audience for each Scheduled occurrence before running

      Starting Population : Segment of Each and Every Customer. (Sample of Customers)

      Segmentation :

      A segment is a reference to db table containing list of customer ID’s that match specific criteria.

      Segmentation path in studio: Audience —> Segment

                                                                   —> Group
                                                                  —> Criteria

      Refresh Types of Segments

      1.Refresable Segment : When other segment will run or reference a run this segment will also refresh

      2.Refresh Child Segment : Child Segments Also gets refreshed when parent Segment is refreshed

      3.Sample Segment option : Allows you to Select Random sample of a segment rule.

      Note : While Creating a email Segment its recommended to keep the Images in a hosted server and reference them in the treatment

      Contact policy Types:(Key phrase: irrespective of past responses)

      allow you to limit the number of actions that a customer can receive over a given period of time on a specific channel.


          • these customer contact limits prevent an action from reading a customer on a specific Channel , irrespective of past response to that action by the Customer

        Suppression policy :(Key phrase: Same Actions Should not be Sent)

        they determine when and for how long an action or group of actions should be shown to a customer.

        Volume Constraint:

        Can be set at Action, channel and property level.

        Action Constraint : It limits the volume of actions that can be sent to customers.

        Channel Constraint: It Limits the Volume of actions that can be delivered via a certain channel

        Property Constraint: it can limit the volume of a set of actions across different issues and groups by grouping them using a property value.

        Files and Database templates:

        why 3rd party vendors required :

        Some necessary infrastructure to send action messages directly to customers may not be available.

        So 3rd party are involved

        Pega writes to cloud

        1.Jfrog Artifactory

        2.Amason S3

        3.Microsoft Azure

        Note:** Multiple action details in a single location/file/db. do this we need to configure the same file/db table template in multiple action flows.**

        Leave a Comment

        Your email address will not be published. Required fields are marked *