The Suppression List allows you to prevent specific users from receiving certain types of notifications. This is useful to protect delivery rates and avoid sending notifications to unreachable customers.
Users added to the suppression list are excluded from notifications based on the configured event types, channels, and duration.
When the Suppression List is enabled, you can choose which types of notifications to block for the users added to this list. Any user included will not receive the selected notification types.
The Suppression List Configuration modal opens.
You can select one or more of the following:
Blocks users from receiving authentication or verification codes.
Important Note: Suppressing OTP notifications is not recommended, as OTPs are critical for authentication and other essential user communications. Enable this option only if you fully understand the impact.
Blocks system-related messages such as order confirmations, receipts, or account updates.
Blocks promotional messages, offers, newsletters, and campaigns.
Once confirmed, the Suppression List is enabled with the selected event types and reasons.
The dialog includes a Reasons section where users can:
The View List section allows you to see and manage all users whose notifications are currently suppressed.
When you click View List, the Suppression List dashboard is displayed, where each row represents a user (Destination / Distinct ID) that has been blocked from receiving certain notification types.
NOTE: Select Distinct ID if you manage User Profiles in Fyno. Otherwise, select Destination.
The Configure option allows you to add, update, or delete suppression settings after the Suppression List has been enabled. Once saved, these settings apply as the global suppression list configuration for the workspace.
When you first enable the Suppression List, you select which notification types (OTP, Transactional, Marketing) should be blocked. However, business needs and communication policies can change over time.
The Configure option allows you to:
Correct initial settings
If the wrong notification types were selected during setup, you can quickly fix them.
Adapt to policy or compliance changes
If your organization updates its communication rules, you can adjust the suppressed notification types without recreating the list.
Respond to user preferences
You may decide to allow transactional messages again while keeping marketing messages blocked.
Avoid rebuilding the suppression list
Instead of removing users and starting over, you can simply update the notification types in one place.
NOTE: Custom suppression reasons cannot be edited once created. They can only be deleted. If a custom reason is deleted, any users previously associated with that reason must be added again with the correct suppression reason.
The Add Users option allows you to manually add one or more users to the Suppression List. Any user added here will be blocked from receiving the notification types defined in your suppression configuration.
This is useful when:
When this option is checked, the user will be suppressed based on the notification types selected in the Configure settings (OTP, Transactional, Marketing).
Checked (Default): The user follows the same rules as the global suppression list.
Unchecked: You can manually choose the notification event types for this specific user.
The user will:
Uncheck this box when:
There are three possible scenarios depending on how the “Adhere to the notification event types in the configuration” option is used.
When the checkbox is enabled, the user automatically follows the global suppression configuration.
You do not need to manually choose notification types.
The user will be blocked from receiving the same notification types defined in the global configuration.
Example:
If the global configuration suppresses Transactional and Marketing notifications, any user added with the checkbox enabled will be blocked from those two types.
Assume the global suppression configuration is set to suppress OTP and Transactional notifications.
When the checkbox is disabled:
The user will be suppressed only for the manually selected notification types.
Example:
If the global configuration suppresses OTP and Transactional, and you disable the checkbox and select only OTP:
When the checkbox is enabled, the user does not have individual suppression settings. Their suppression behavior is always determined by the current global configuration.
If the global configuration is updated after the user is added, the user’s suppression settings automatically update to match the new global configuration.
The user is suppressed only for the notification types currently selected in the global configuration.
Example: