Next-Best-Action and decision management design
Domain focus
This domain tests whether you can translate business goals into a Pega Customer Decision Hub Next-Best-Action design. The exam expects you to know how the business hierarchy, engagement policies, and arbitration cooperate to produce a ranked, context-aware action list.
Core design rules
- Build the hierarchy as Issue > Group > Action. Issues are broad objectives such as retention; groups narrow them; actions are concrete offers with propositions and treatments.
- Apply engagement policies in layers: eligibility at customer or group level, applicability at action level, and suitability as a score or threshold. Contact policy limits and suppression belong here, before arbitration.
- Arbitration ranks remaining actions using business levers plus propensity and value. Priority forces ordering; weight adjusts relative influence. Configure levers at issue, group, and action level so business teams can tune outcomes without code.
- A channel definition fixes direction (inbound or outbound), context, and available treatments; the same action can rank differently by channel.
Worked example
Maria is in a retention issue with two groups: 'high-value save' and 'contract renewal'. Eligibility passes, but the outbound contact policy blocks a third email this week. Applicability removes the renewal action because she has no contract. Suitability shows a low propensity for the save action, so arbitration ranks a lower-cost courtesy action first after weighting. Reasoning: policy filters run before scoring, and weights do not override an ineligible action.
Traps
Do not confuse eligibility with applicability; do not put contact limits in a strategy; do not use priority as a substitute for weight; and always confirm the channel direction before diagnosing a missing action.