• Retail Banking
  • Customer – can have multiple Accounts
    • Account – one per card or account
• Telecommunications
  • Account – can have multiple Subscribers
    • Subscriber – one for each phone number, can have multiple Devices
      • Device, for example, phone, tablet, watch
• Healthcare
  • Policy – can have multiple Members
    • Member – can have multiple Claims
      • Claim

As such, limits can be applied to combinations of action contexts (using the CombineContexts setting), and to individual contacts, or across all contacts (using the LimitByContact setting).

Also, since all outbound channels are evaluated together, a limit can be applied across all outbound channels, whereas for inbound channels, only a single channel will be processed during any interaction.

• Each - The same Action Limit is to be applied to each channel for the Action Context. This removes the need to define a separate limit for each channel.
• <Channel Name> (for example, Web, Email, and so on) - Applies the Action Limit to the specific channel. This setting overrides any value already set by the Each functionality.
• <Blank> - Indicates that the Action Limit is to be applied over the combination of all channels. That is, it sets a limit for the Action Context regardless of channel. This limit is applied after individual channel limits have been applied, and is only available for Outbound processing, since for Inbound only a single channel is processed at a time.

• true - Apply the limit n to each contact separately so that the top n actions ordered by descending priority are emitted for each contact.
• false - Apply the limit n to the interaction across all contacts, so that the top n actions ordered by descending priority within contact priority are emitted. Contact priority is determined by whether the contact is a primary contact or not, with primary contacts having a higher priority; the order for contacts with equal priority would be undefined.