Skip to main content


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

Defining treatments for actions

Updated on September 15, 2022

A treatment represents how the action is presented and experienced by a customer in a specific communication channel. You can define treatments for a number of built-in and custom channels, such as email, web, and others.

Pega Customer Decision Hub

Once created, treatments are associated to a specific action on the Treatments tab of the action rule. Treatments added to the Treatments tab of the action will be prioritized by the next-best-action strategy, which uses adaptive models to determine the best channel and treatment. This is done by continuously testing the treatment success rate, by randomly increasing the propensity of certain treatments to allow the model to explore and learn about other situations that could yield positive results. If you use Next-Best-Action Designer, you do not need to manually test the effectiveness of your treatments. For more details, see Model learning for new actions.

The Flow tab of the action should utilize the Use associated treatment option on the appropriate shape in order to take advantage of the best treatment based on the strategy framework. To create a new treatment, the user simply needs to type in the desired name and click the magnifying glass to launch the Create form for the treatment.

Treatments can be defined at the top level or can be categorized into issues and groups. The system automatically selects the issue and group in the Create form using the corresponding values from the action rule. Users can change these selections to store the new treatment at a different hierarchical level.

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.

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

Close Deprecation Notice
Contact us