PEGAPCDC87V1 Exam Dumps : Certified Pega Decisioning Consultant (PCDC) 87V1

 Understanding the Context: Myco, a telco, wants to introduce new plans without handsets. Currently, their business structure under the sales issue/plans group contains actions that are handsets.

 Business Structure: In Pega Customer Decision Hub, the business structure is organized into issues and groups.

 Action Naming: To reflect the new situation where plans do not include handsets, the term "handsets" needs to be changed.

 Level of Change: The appropriate level for renaming the plans to reflect this new structure is at the Issue level. At this level, the business context for actions is defined, and changes here will apply to all actions under that issue.

 Reference: As per the documentation, changes to business issues and groups should be done at the issue level to ensure that the new context is accurately represented across all relevant actions​​.

If the volume constraint shown in the image (Maximum 75 Daily with Channel: Action: StandardCard, Maximum 50 Daily with Channel: Email, Maximum 50 Daily with Channel: SMS) is applied, the outbound run will deliver 75 actions in total. This includes actions across different channels, adhering to the specified limits.

 Requirement:

U+ wants to show a retention offer to customers likely to leave the bank based on historical interaction data.

 Model Types:

Entity Model: Used for recognizing entities within data.

Text Analytics Model: Used for analyzing text data.

Predictive Model: Used for making predictions based on historical data.

Adaptive Model: Used for real-time adaptation based on new data.

 Suitable Model:

For predicting customer churn (likelihood of leaving), a predictive model is best suited because it leverages historical data to make future predictions.

 Verification from Pega Documentation:

Pega documentation on leveraging predictive models for customer retention and churn analysis.