Pass the Pegasystems Pega Decisioning Consultant PEGAPCDC87V1 Questions and answers with ExamsMirror

Action Flow Template: To implement the requirement of using the same action flow template for all credit card actions, configure the email treatment. This allows you to define the desired flow pattern and reuse it across different credit card actions.

Configuration: Create an email treatment template that includes the specific flow pattern, and then apply this template to all the relevant credit card actions.

Pega Customer Decision Hub supports writing action details directly to cloud storage solutions such as Microsoft Azure and Amazon S3. This capability ensures that the offer messages selected by the Decision Hub can be seamlessly transferred to the preferred cloud storage location of the email service provider, facilitating efficient and secure delivery of customer communications.

To define a contact policy that suppresses an action for 20 days if it was rejected twice in any channel in the last 30 days, you need to specify the suppression rule as follows: "Suppress an action for 20 days if there are 2 rejects for any channel in the last 30 days." This rule ensures that the action is paused after it has been rejected a specified number of times across any channel within the given timeframe.

Decision Table Processing: The decision table is configured to evaluate the customer's credit score and average balance to determine the risk segmentation.

Conditions Evaluation:

For a credit score of 240 and an average balance of 35,000:

The first condition checks if the credit score is >= 400 and < 600, and average balance is >= 30,000, which does not match.

The second condition checks if the credit score is >= 200 and < 400, and average balance is >= 20,000, which matches both the credit score (240) and the average balance (35,000).

Therefore, the correct result for these conditions is "Fair".

References: This is derived from typical Pega Decision Table configuration and logical evaluation as described in Pega documentation on using decision tables for such scenarios .

 Placement Type in Treatment Design: To present the Rewards Card offer on the top right of the customer’s account page, you should use the "Tile" placement type. This type is specifically designed to position content in a compact, visually distinct block that can be placed in specific areas of a webpage, such as the top right corner.

 Implementation: In the treatment configuration within Pega, you can specify the placement type as "Tile" to ensure the offer is displayed correctly on the account page.

Score Mapping Tab - This tab in the scorecard rule is used to map the raw score to a property that can be used in decision strategies.

Steps to Map a New Property:

Open the scorecard rule in Dev Studio.

Navigate to the Score Mapping tab.

Add a new mapping for the raw score to a property (e.g., pyRawScore).

Save the scorecard rule.

Using the Mapped Property:

In the decision strategy, reference the mapped property to utilize the raw score value.

Apply this property in conditions, filters, or other decision components as needed.

To limit the number of emails sent to customers irrespective of past outcomes with a particular offer and customer, you can implement customer contact limits. Customer contact limits are used to control the number of interactions a customer can receive over a specific period on a particular channel, ensuring that customers are not overwhelmed with too many messages.

Real-Time Channels for Next-Best-Actions: Pega Customer Decision Hub supports presenting Next-Best-Actions through various real-time channels.

Retail Store: Actions can be presented to customers directly in the store through POS systems or store associates.

Call Center: Customer Service Representatives can receive real-time Next-Best-Action recommendations to present to customers during interactions.

SMS: Automated messages can be sent to customers with personalized Next-Best-Action offers via SMS.

 Requirement:

The bank wants to avoid sending promotional emails related to credit card offers to a customer if they have already received one within a limited time period.

 Configuring Suppression Policy:

A suppression policy needs to be defined to prevent over-contacting customers.

Suppression policies automatically put an action on hold after specific criteria are met, such as a customer having already received a promotional email.

This ensures that customers are not bombarded with repeated offers, improving customer experience and adhering to communication limits.

To define a suppression rule in Pega for the scenario where a group of mortgage offers should be suppressed for 15 days if a customer ignores three offers from the mortgage group, follow these steps:

Define the Suppression Rule:

Create a contact policy in Pega Customer Decision Hub to suppress the group of mortgage actions.

Specify the Condition:

Set the condition to suppress the group of actions if there are 3 rejects (ignored offers) for any channel. This means the suppression applies regardless of whether the offers were displayed on the web, mobile, email, etc.

Set the Suppression Duration:

Configure the suppression period to be 15 days. This ensures that the group of actions will not be shown to the customer for 15 days after they have ignored three offers.

Apply the Contact Policy:

Ensure the contact policy is associated with the relevant group of actions (mortgage offers) and that it is enforced by the strategy framework.

Test and Validate:

Test the suppression rule to verify it works as expected and that the offers are suppressed correctly after three rejects.

References:

Pega Customer Decision Hub User Guide 8.7: Adding more tracking time periods for contact policies, Creating a contact policy, Contact policy library​​.