Skip to main content

 –

Next-Best-Action Designer enhancements

Suggest edit Updated on January 22, 2021

Enhanced multi-level decisioning

Next-Best-Action Designer now supports multi-level context decisioning. You can define multiple context entities in the Context Dictionary to better reflect the decisions that you want to make as you engage customers. These customer contexts can represent, for example, individual subscribers, as well as households or accounts, all treated as different audiences that must be communicated with in different ways. Actions are associated to a specific context and separate engagement policies can be defined for each.

For more information, see Understanding multilevel decisioning and the Context Dictionary.

Separate engagement policies for different customer contexts

You can now create separate engagement policies for different customer contexts that you defined for your application. For example, to offer the account owner a family data plan that applies to the whole household, and also send out new phone offers to individual household members, you can define separate engagement policies for the Account and Subscriber contexts.

For more information, see Configuring engagement policies for actions and the Tutorial: Understanding capabilities.

Simulation results available for different customer contexts

After you run a simulation in Pega Customer Decision Hub, you can drill down to the results for each customer context in your application. In this way, you can check how many potential actions for the customer context are filtered out by each component of the policy, and discover if a particular criterion is too broad or too narrow for your requirements.

For more information, see Testing Next-Best-Action configuration with audience simulations.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us