Skip to main content


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

Adding additional channels to Next-Best-Action Designer

Updated on August 4, 2022

In addition to the built-in channels provided by Pega Customer Decision Hub, you can implement additional channels by extending the ChannelSettings decision data rule. For example, if you send out physical product catalogs to your customers, you can create a Direct Mail channel for these types of treatments.

Pega Customer Decision Hub
  1. In Dev Studio, click RecordsDecisionDecision data.
  2. Open the ChannelSettings decision data rule that resides in the Data-Decision-Request-Customer class.
  3. Click Check out.
  4. Click New.
  5. Configure the channel details:
    • Name- For example, Direct Mail.
    • Description- An optional description of the channel, for example, Used for product catalogs related to the Household line.
    • Channel icon- An optional icon to visually identify the channel in Next-Best-Action Designer. Available icons include pi-forward, pi-mail, pi-picture, pi-mobile-phone, pi-notification, pi-money, pi-headset, and pi-chat-typing.
    • ModelName- Enter NBA.
    • SettingName- A unique identifier for the channel, for example, DirectMail.
    • SettingValue- Set to true to enable the new channel, or false to create the channel without enabling it.

      For more information about enabling channels, see Enabling channels.

  6. Save and check in your changes.
Result: The new channel now appears in the Channels tab of Next-Best-Action Designer. If it is enabled, you can also use it when configuring contact policies in the Constraints tab of Next-Best-Action Designer.

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