Avoid Redundant Product Offers in PEGA Decisioning Strategy
To
avoid the same product recommendation which customers own already, from PEGA we
need to define the data relationship using DataFlow. For example, to cater to a
use case where a customer owns multiple products and details of all products
are available in a Product master table. So, there is a one-to-one relationship
between the ProductHoldings and Product entities.
Now
to implement the business case discussed (Filter the products already owned by
the customer), you must filter out the products already owned by the customer.
For this, you use a strategy pattern that is composed of three components: Data
Import, Data Join and Filter, we can filter out the products which customer is
holding already. DataImport+DataJoin+Filter
is the Strategy design pattern used to achieve.
Making NBA more relevant using Interaction History - Learn from IH (Interaction History)
Update the Strategy to include a component that retrieves Interaction History data for previous phone offers. We then filter out phone offers for customers that have accepted a phone offer in the past. We can of course make the filtering process much more sophisticated by considering phone upgrades, etc. But for the sake of our demonstration, we will keep the strategy simple; anyone who has been made a phone offer within the last 120 days will not be made another phone offer of any kind. IH+GroupBy+Filter is the Strategy pattern used to prevent Redundant offer recommendation in PEGA Strategy logic.
