A bank has been running traditional marketing campaigns for many years. One such campaign sends an offer email to qualified customers on day 1. On day 3, it sends a reminder email to customers who haven't responded to the first email. On day 7, it sends a second reminder to customers who haven't responded to the first two emails. If you were to re-implement this requirement using the always-on outbound customer engagement paradigm, how would you approach this scenario?
Requirement Analysis: U+ Bank wants to display a specific credit card offer (Standard Card) to every customer who logs in to the bank website using Pega Customer Decision Hub.
Identify Mandatory Artifacts: To implement this requirement in Pega Customer Decision Hub, certain artifacts are necessary:
Business Structure: This defines the business hierarchy in Pega CDH, such as issues and groups. For this scenario, a relevant business issue and group must be defined (e.g., Credit Cards -> Standard Card).
Action and Associated Web Treatment: The specific credit card offer (Standard Card) must be created as an action, and it must have an associated web treatment to display on the bank's website.
Real-time Containers: These containers facilitate real-time interactions by displaying the appropriate offers to customers when they log in to the website.
Not Mandatory Artifacts:
Customer Contact Policies: These policies are used to limit the number of interactions with customers over a period. However, they are not mandatory for simply displaying an offer upon login.
Customer Engagement Policies: While important for determining eligibility, applicability, and suitability of offers, they are not specifically mandatory for the basic requirement of displaying an offer upon login.
Conclusion: The three mandatory artifacts to implement the requirement are a business structure, an action and the associated web treatment, and real-time containers.
Lindsey
1 days agoVal
1 days agoFannie
5 days agoVal
7 days ago