The Next-Best-Action Designer user interface provides an easy to use, guided way to define, manage and monitor your next-best-actions across your inbound and outbound channels.

To accelerate the process of implementing next-best-action, use predefined templates that contain next-best-action settings.

Use the Next-Best-Action Designer to build the structure of business issues and groups in your organization.

An action holds various details about a particular offering, such as Start Date, End Date, and Expected Revenue. In addition to the proposition data, the Action rule enables the user to visually specify the flow of steps for a particular offering (Flow).

You can restrict the number of contacts a customer receives in a given period of time, or configure an automatic pause for actions after a specific number of outcomes.

Edit each group and define eligibility, relevancy, and suitability conditions for actions associated with this group.

Define eligibility, applicability, and suitability conditions for your actions. Engagement policies allow you to specify the conditions under which an action or group of actions is eligible for a customer.

On the Arbitration tab of the Next-Best-Action Designer, you can define the AI controls used to decision on the Next-Best-Action for each customer. The customer data and insights help provide proactive contextual actions according to the customer's propensity, context, and other factors.

Select the channels which you use to communicate with your customers, as well as the triggers that cause Pega Customer Decision Hub to decision on Next-Best-Actions.

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.

Use customer segments to identify a group of customer entities to use as audience in always-on outbound campaigns.

A Seed List is a collection of artificial entities (also called “seeds”) that can be used to test, monitor, and validate various aspects of the processing infrastructure. For example, such a list can be used to test the timeliness and reliability of processes being handled by a third party.

Address your customers' needs better by predicting customer behavior with predictions. For example, you can determine the probability of a customer accepting an offer or the likelihood of a customer discontinuing a subscription (churn).

Real-Time Containers provide an easy low-code or no-code way for marketers to manage content that appears in real-time channels, such as web and mobile. As an example, a marketer may define a Container to represent a region of a web page. They can then associate the Container with a Campaign or a Next-Best-Action in the Next-Best-Action Designer. In real-time when the Container is called (say on a web page), the associated Campaign or a Next-Best-Action is executed and the Container gets populated with results.

Events provide a mechanism for responding to real-time marketing opportunities. An Event is essentially an entry-point into the application which can be initiated by internal or external systems. Events can be mapped to Multi-Channel Campaigns and can trigger their execution.

A Microsite is a collection of one or more pages which can function as a standalone entity. Microsites can be also be embedded into existing websites. They can be used for various marketing purposes, such as product announcements and lead generation.

In Pega Customer Decision Hub, strategies are the underlying mechanism that determines which action are selected for which customers.

In Pega Customer Decision Hub, campaigns provide an additional mechanism to deliver actions to customers and monitor the action performance.

Customer journeys are a sum of the experiences that your customers go through when interacting with your organization. Rather than looking at just part of an experience or transaction, the customer journey documents the full spectrum of the customer experience.