Skip to main content

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

Specifying the context for inbound applications with the Inbound Call Center shape

Updated on August 4, 2022

The Inbound shape provides a means to specify the content that should be returned when an inbound application, such as Next-Best-Action Advisor (NBAA), requests this action to display within their application.

Pega Customer Decision Hub

The following configuration options are available for this shape:

SectionName of the Section rule to use. The content of this section is returned when an inbound application (such as NBAA) requests action content from the system.
ChannelInbound channel for the Treatment (Default value for this shape is CallCenter).
Work StatusStatus of the action after executing this step in the flow.
Note: There should be only one Inbound shape in a flow. Having multiple Inbound shapes in the same flow could cause non-deterministic behavior in resolving the content that should be returned to the inbound application.

The Inbound shape, by itself, simply serves as a determining point for the content to be returned for external requests. However, this shape can be (and typically is) combined with the InboundTicket ticketing mechanism to provide a branch of flow execution for processing an inbound request. Refer to Branching the action flow based on the channel for more details.

  • Previous topic Configuring the delivery of push notifications with the Push Notification shape
  • Next topic Pausing the flow execution with the Wait shape

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