Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Understanding Next-Best-Action Designer arbitration

Updated on September 15, 2022

Arbitration determines how the strategy framework prioritizes the list of eligible and appropriate actions that come out of each group. The configuration and metadata for your arbitration options are stored in several decision data rules (DDR) which are used by the strategy framework.

Pega Customer Decision Hub
Arbitration tab in Next-Best-Action Designer.

The Next-Best-Action strategy framework includes adaptive models that learn at the action as well as the treatment level. These models apply the principles of outcome optimization at the treatment level and can be extended if you wish to apply advanced techniques or challenge the default models. The models always learn, even if you decide not to apply analytics to your prioritization formula.

The propensity used in arbitration can be applied from the treatment level or at the action level. It is recommended to use treatment-level propensity, since it provides the best treatment on the best channel for a particular customer.

Note: In BOE environments, the Average Propensity values displayed in the PropensityThresholds section, retrieve their values from the ScenarioPlannerActuals data set. For other environment types, their values are retrieved from the Actuals data set.
Context weighting

Real-time contextual data is an important part of making highly relevant recommendations. Context weighting allows you to assign weighting for a specific context value to all actions within an issue or a group.

The contextual weighting definitions are stored in a decision data rule (DDR), which is managed by the Next-Best-Action Designer and used by the strategy framework.

Business value
You can specify the value of an action in the definition of that action. If more sophisticated calculations are needed, the extension strategy CalculateValueExtension can be customized to your specific requirements.
Business levers

To highlight or push a particular action or group of actions, specify a weight on the individual action or add a business purpose weighting and selecting an issue only or group and then the weighting value.

These levers can be toggled on or off, which determines whether or not these weightings are applied to the final prioritization formula.

Final priority
You can explore the results of next-best-action decisions by clicking Explore arbitration results. The Customer Profile Viewer displays information about a customer's decision history and interaction history, as well as provides the option to test your engagement policies, constraints, and propensity settings by checking the results of next-best-action decisioning for a specific customer.
Model maturity

For newly introduced outbound actions, AI models may not yet know which customers to target. To minimize the possibility of customers receiving actions that are not relevant, only 2% of the customer population are initially targeted with new actions. As the model collects the resulting learnings and matures, the targeted percentage increases until it reaches 100% for fully mature models. A model is considered mature after it has received 200 or more positive responses.

To prevent multiple new actions from having the same starting propensity, Pega Customer Decision Hub uses Thompson Sampling instead of the standard propensity smoothing formula. The propensity is initially set to a random value between 0 and 1. As the model matures, this quickly converges to the model propensity.

  • Previous topic Understanding Next-Best-Action Designer engagement policies
  • Next topic Understanding Next-Best-Action Designer channels

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us