> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://fyno.io/docs/delivery-limit/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://fyno.io/_mcp/server. # Delivery Limit > Configure intelligent notification pacing, regional compliance guardrails, and user-centric delivery throttles using Do Not Disturb (DND) windows, group-level DND overrides, and Frequency Capping. ## Do Not Disturb (DND) Do Not Disturb (DND) allows you to configure idle hours at which time notifications should not be sent to users. You can now configure your Do Not Disturb settings for all channels from the following navigation: Workspace Settings (bottom left corner in menu) -> Delivery Limit -> Do not disturb ### Why DND? Engaging your users with notifications is one of the most effective ways to drive increased adoption, retention and conversions. However, there are instances when you'd prefer your notifications not to reach them at inconvenient times, such as 3:00 am when your users are sound asleep.. > **Tip** > > According to regulations, the "Do Not Disturb" (DND) time for sending **SMS marketing messages is between 9 PM and 9 AM** > **Tip** > > According to regulations, the "Do Not Disturb" (DND) time for sending **RCS marketing messages is between 10 PM and 7 AM** ### How it works? You now have the option to configure "Do Not Disturb" (DND) hours for both transactional and marketing communications. Currently, this feature is applicable to SMS, WhatsApp, Email, Push, RCS and Voice channels. When DND is active, Fyno will not trigger notification during the specified hours. You have the flexibility to decide whether to **drop** (discard) notifications that were triggered during the DND period or **queue** their delivery until after the DND window. Queued messages will be sent at the end of DND period with 30 seconds additional delay. Select a channel from the list on the left to configure it. Marketing and Transactional are configured independently, each with its own toggle in the Notification Event Type column, so you can enable DND for one without enabling it for the other. For example, if you want to set DND time for Marketing notifications from 8 PM till 10 AM for SMS and send notifications after the DND window, follow these steps. Under SMS channel, turn on the toggle next to Marketing in the Notification Event Type column. Set From Time as 8 PM Set To Time as 10 AM. Under If triggered during DND period, select **Drop it** if you don't want to send notifications during DND hours and discard them. Select **Queue it**, if you want to queue the notifications triggered during DND hours and send them after the DND window. ![](/docs/_fern-img/dfc6810090759b7bfd3ea22832b9163b55adff4c556f388a6fe0be41436cd25e.webp) If you want to add DND settings for Transactional notification also for SMS, turn on the toggle next to Transactional and set its own From Time, To Time and behaviour. > **Info** > > This setting will only apply to Notification Events triggered in LIVE environment. ### Group-based DND The DND settings above apply to every notification event on a channel, separated only by notification type. Group-based DND lets you override that behaviour for a specific set of notification events. ![](/docs/_fern-img/5f144bc30bfef9ad86a22c5c08d6598cc093e60337556b9be56ccb5956688f0b.webp) The **Group based DND** panel sits directly below the notification event type table for the selected channel. Turning on the toggle reveals a table where you add one rule per group. As the panel itself states, notification events in these groups will ignore any event type configuration above. Groups are managed from Workspace Settings -> Groups. When you attach a DND rule to a group, every notification event in that group follows the group's rule instead of the Marketing or Transactional configuration above. This covers two common requirements: * **Custom Hours** - a shorter or shifted DND window for a set of events. For example, your workspace SMS DND runs from 12 AM to 6 AM, but events in a **Critical Notifications** group are allowed to send until 1 AM. * **Skip DND** - events that should never be held back. For example, events in an **Emergency Notifications** group are delivered at any hour, regardless of the workspace DND window. For example, if you want events in the **Critical Notifications** group to follow a DND window of 1 AM till 6 AM for SMS instead of the workspace window, follow these steps. Under Do not disturb, select the SMS channel. Turn on the **Group based DND** toggle. Select **Critical Notifications** from the Group drop down. Select **Custom Hours** from the DND Rule drop down. Set From Time as 1 AM and To Time as 6 AM. Under If triggered during DND period, select **Drop it** to discard notifications triggered during the group's DND hours, or **Queue it** to queue them and send them after the group's DND window. If you want to add a rule for another group on the same channel, you can do it by clicking the '+ Add Group' button. The DND Rule drop down defaults to **Custom Hours**. To exempt a group from DND entirely, select **Skip DND**. The following fields are available for each group. | Field | Description | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Group** | The group whose notification events this rule applies to. | | **DND Rule** | **Custom Hours** applies the window defined in this row. **Skip DND** exempts the group from DND entirely. | | **From Time** | Start of the group's DND window. Available only with **Custom Hours**. | | **To Time** | End of the group's DND window. Available only with **Custom Hours**. | | **If triggered during DND period** | **Queue it** queues the notification and sends it once the group's DND window ends. **Drop it** discards the notification and no further attempt is made once the DND period ends. Available only with **Custom Hours**. | #### Which DND applies? For a given channel, Fyno resolves DND in the following order. **Group rule** - if the notification event belongs to a group that has a DND configuration for the channel, that rule applies. It applies whether the notification event is marketing, transactional or OTP. **Notification type rule** - if the notification event does not belong to such a group, the Marketing or Transactional window enabled for the channel applies. **No restriction** - if neither is enabled, the notification is sent immediately. | Notification event | Event type | Group | Rule that applies | | -------------------- | ------------- | --------------------------------------------------- | ------------------------------ | | Order shipped | Transactional | Not in a group | Workspace Transactional window | | Weekend sale | Marketing | Not in a group | Workspace Marketing window | | Payment failed | Transactional | Critical Notifications (Custom Hours, 1 AM to 6 AM) | 1 AM to 6 AM | | Login OTP | OTP | Critical Notifications (Custom Hours, 1 AM to 6 AM) | 1 AM to 6 AM | | Account breach alert | Transactional | Emergency Notifications (Skip DND) | Sent at any time | Notifications set to **Queue it** are sent at the end of the group's DND window with 30 seconds additional delay, the same as the workspace-level configuration. > **Info** > > A group rule replaces the notification type rule. The two windows are not combined, and the notification type rule is not applied as an additional restriction on top of the group's window. > **Info** > > Marketing Frequency Capping is applied separately. A group configured to skip DND is still subject to any frequency cap configured for the channel. > **Warning** > > **Skip DND** overrides the DND configuration in Fyno only. Make sure notifications sent by a group configured to skip DND comply with the regulatory DND windows applicable to your channel and region. > **Info** > > This setting will only apply to Notification Events triggered in LIVE environment. #### Removing a group's DND configuration In the Group based DND table, click the delete icon on the row you want to remove. In the "Delete Configuration for \" dialog, click **YES, DELETE**. Removing a DND configuration does not delete the group and does not change the notification events assigned to it. Notification events in that group fall back to the workspace-level Marketing or Transactional DND configured for the channel. If you want to stop applying group rules on a channel without removing each row, turn off the **Group based DND** toggle. ## Marketing Frequency Capping You can now configure your Marketing Frequency Capping for all channels from the following navigation: Workspace Settings(bottom left corner in menu) -> Delivery Limit -> Marketing Frequency Capping ![](/docs/_fern-img/f32392f3dd2395fe2a7ecd90dbf51fb065e8839920f9d9f498f4ca490a3323ec.webp) ### Why Frequency Capping? When multiple campaigns are created, some users may fall into multiple segments/cohorts and thus receive more than one notification in a day. Frequency Capping allows limits to be placed on the number of notifications users will receive during a particular period from a particular channel (Push/Email/SMS/WhatsApp). ### How it works? You now have the option to configure Frequency Capping for marketing communications. Currently, this feature is applicable to SMS, WhatsApp, Email, and Push channels. For example, if you want to set Frequency Capping as "*10 Notifications per destination per day for SMS*" , follow these steps. Under SMS channel, turn on the Marketing frequency capping toggle. Enter 10 in the Count field. Enter 1 in the Time field. Select Day(s) from the drop down. The available options are Second(s), Minute(s), Hour(s) and Day(s). 11th notification sent to the same destination on the same day will be dropped and won't be sent to the user. > **Info** > > We support time frames ranging from a minimum of 30 seconds to a maximum of 30 days. The Notification Count can range from a minimum of 1 to a maximum of 255. > **Info** > > This setting will only apply to Notification Events triggered in LIVE environment. > Configure intelligent notification pacing, regional compliance guardrails, and user-centric delivery throttles using Do Not Disturb (DND) windows, group-level DND overrides, and Frequency Capping.