PEGACPDC88V1 practice question 7 of 15

Which of the following reasons explains why a customer might receive an action that they already accepted?

Full set: 60 questions
Answer options
A: The action suitability conditions are not defined.
B: The volume constraint is not set to exclude previously accepted offers. Correct answer
C: The suppression rules are not defined to exclude previously accepted actions.
D: The actions are filtered based on eligibility.
Correct Answer:
B. The volume constraint is not set to exclude previously accepted offers.
Explanation

Contact Policies, which are a type of business constraint, are the primary mechanism in Pega Customer Decision Hub for managing customer communication based on their interaction history. A contact policy can be configured to limit the number of times actions are shown to a customer after they provide a specific response, such as "Accepted." If this policy (referred to in the option as a "volume constraint") is not configured to track acceptances and prevent subsequent offers, the system will not filter out the action, leading to the customer receiving an offer they have already accepted.

Why Incorrect

A. The action suitability conditions are not defined. Suitability determines an action's relevance based on factors like propensity. It does not inherently track historical acceptances, so an action could still be deemed suitable.
C. The suppression rules are not defined to exclude previously accepted actions. Suppression rules typically check a customer's state (e.g., they own the product), whereas contact policies are specifically designed to react to interaction events (e.g., they accepted an offer).
D. The actions are filtered based on eligibility. Eligibility is a prerequisite check (e.g., age, location). A customer who previously accepted an action was, by definition, eligible; this filter does not prevent re-offering.

References

1. Pega Customer Decision Hub (8.8) Implementation Guide: In the section "Defining constraints," the subsection on "Contact policies" details their function: "Contact policies are rules that define the number of times a customer can be contacted... A contact policy suppresses an action or a group of actions for a specific channel when a customer is over the contact limit." This includes tracking responses like "Accepted" to prevent re-offering.

2. Pega Academy - Pega Certified Decisioning Consultant (8.8) Mission: The module "Controlling the outbound customer conversation" and the specific topic "Contact policies and constraints" explain how to configure these rules. An example use case provided is: "Once a customer accepts a credit card offer, you do not want to show them any credit card offers for the next 3 months." This directly aligns with using a constraint/contact policy to handle previous acceptances.

Scroll to Top