Setting Up Notification Type Algorithms

Suppression Criteria

Notification types can be suppressed from appearing in a list for a particular customer. This is done by plugging in a suppression criteria algorithm on the notification type.

The base product provides the C1-ALWY-SUP (Always Suppressed) algorithm, which suppresses the notification type for all customers. This does not impact active contact preferences for the notification type, nor does it prevent processes from creating notifications of this type. This should be used with business process changes to stop sending notifications of this type. This can also be used temporarily after a notification type has been configured, but before it should be used.

The base product provides the C1-CKSP-PPB (Check Prepaid Biller Suppression) algorithm, which suppresses the notification type if the customer does not have an active prepaid biller task. This should be used on prepaid related notification types so that only customers on prepaid billing receive these notifications.

If your implementation's business rules require additional notification type suppression rules, you may introduce your own algorithm.

Override Do Not Disturb

Do not disturb information can be captured on person contacts. Person contacts are associated with a notification type to define a contact preference. When notifications are sent out, do not disturb information is included in the message to the receiving system. Some notification types might be important enough to not honor the customer’s do not disturb information. For example, a notification might be sent to a subset of customers to warn of a gas leak and evacuation and needs to be sent regardless of the customers do not disturb wishes. This is done by plugging in an override do not disturb algorithm on the notification type. Note: this does not actually override the customer’s information, but sends an indicator in the message to the receiving system that the do not disturb information should be overridden or ignored.

The base product provides the C1-OVR-DND (Override Do Not Disturb) algorithm, which returns a value of true that is passed to the receiving system in the notification.

If your implementation has more specific business rules related to overriding a customer's do not disturb preference, you may introduce your own algorithm.