Quiet Hours

Schedule periods when stream notifications are held or skipped entirely. Perfect for overnight hours, work times, or any period when your community doesn't want to be pinged.

Premium Feature

Quiet Hours is a Premium-only feature. Upgrade to Premium to unlock this and other advanced notification controls.

What Are Quiet Hours?

Quiet Hours lets you define time windows when stream notifications are handled differently. Instead of immediately pinging your server when a streamer goes live at 3 AM, you can:

  • Skip notifications entirely during quiet hours
  • Queue notifications and send a summary when quiet hours end

Use Cases:

  • Prevent late-night notification spam
  • Respect work hours for professional communities
  • Reduce notification fatigue during high-traffic streaming periods
  • Give your community peaceful sleep without missing important streams

How It Works

  1. Configure Window: Set a start time, end time, and timezone for your quiet hours
  2. Choose Action Mode: Decide whether to skip notifications or queue them for a summary
  3. Stream Goes Live: When a tracked streamer goes live during quiet hours:
    • Skip Mode: Notification is silently skipped (stream still tracked)
    • Summary Mode: Notification is queued for later
  4. Quiet Hours End: In Summary mode, a single summary notification lists all streams that went live

Setting Up Quiet Hours

Quiet Hours are configured through the Web Portal.

Step 1: Access Guild Settings

  1. Go to the Web Portal (/portal)
  2. Select your server
  3. Click "Settings" in the sidebar
  4. Scroll to the "Quiet Hours" section

Step 2: Enable Quiet Hours

Toggle "Enable Quiet Hours" to activate the feature.

Step 3: Configure Time Window

  1. Start Time: When quiet hours begin (e.g., 10:00 PM)
  2. End Time: When quiet hours end (e.g., 8:00 AM)
  3. Timezone: Select your server's primary timezone
Overnight Windows

The window can span midnight. Setting start to 22:00 and end to 08:00 creates a 10-hour overnight quiet period.

Step 4: Choose Action Mode

Skip Mode: Notifications during quiet hours are not sent at all.

  • Best for: Servers that don't care about overnight streams
  • Impact: Lower notification volume, some streams may be "missed"

Send Summary Mode: Queue notifications and send a summary when quiet hours end.

  • Best for: Communities that want to know what happened
  • Impact: Single notification catches up on all overnight activity

Step 5: Configure Summary Settings (Optional)

If using Summary mode:

Mention Role: Optionally ping a specific role when the summary is sent.

  • Create a dedicated role like @Stream Summaries for users who want to be notified
  • Leave blank to send the summary without pinging anyone

Configuration Options

Action Modes

ModeWhat HappensBest For
SkipNotifications silently skippedServers that don't need overnight notifications
Send SummaryQueued notifications sent as single summaryCommunities that want to catch up on missed streams

Summary Message Format

When quiet hours end and you have queued notifications, a summary is sent:

Good morning! Here's what happened while quiet hours were active:
 
Stream Summaries:
- StreamerA went live playing Minecraft
- StreamerB went live playing Valorant
- StreamerC went live playing Just Chatting
 
3 streams went live during quiet hours (10:00 PM - 8:00 AM EST)

The summary includes:

  • List of streamers who went live
  • Game/category they were streaming
  • Count of total streams
  • Time window reference

Per-Streamer Override

For important streamers who should always notify (even during quiet hours):

  1. Edit the streamer in the Web Portal
  2. Enable "Ignore Quiet Hours"
  3. This streamer will send immediate notifications regardless of quiet hours

Example Use Case: Your server owner streams occasionally and wants their streams announced immediately, even at 2 AM.


Analytics Integration

Quiet Hours activity is tracked in your Analytics dashboard:

Overview Tab

A dedicated "Quiet Hours" stats card shows:

  • Queued: Notifications held for summary
  • Skipped: Notifications that were skipped entirely
  • Summaries Sent: Number of summary messages delivered
  • Period-over-period trends for each metric

Activity Heatmap

The Activity Heatmap includes a Quiet Hours overlay:

  • Toggle "Show Quiet Hours" to see your quiet hours window
  • Purple overlay highlights hours within your quiet hours window
  • Helps visualize how much streaming activity occurs during quiet hours

Notification Chart

The notification timeline shows event type breakdown:

  • Standard notifications (green)
  • Queued during quiet hours (purple)
  • Skipped during quiet hours (light purple)
  • Summary notifications (violet)

Best Practices

Choose the Right Timezone

Do This

  • Use your community's primary timezone
  • Consider where most members are located
  • Account for daylight saving time changes

Avoid This

  • Using UTC for a US-based server
  • Setting times that don't match member habits
  • Forgetting about international members

Create an Opt-In Role for Summaries

If using Summary mode with a mention role:

  1. Create a role like @Stream Summaries or @Morning Recap
  2. Let members opt-in by requesting the role
  3. Use reaction roles or a bot to automate role assignment
  4. Only interested members get pinged

Use "Ignore Quiet Hours" Sparingly

The per-streamer override is powerful but should be used carefully:

  • Reserve for truly important streamers
  • Too many overrides defeats the purpose of quiet hours
  • Consider using it for special events rather than permanently

Troubleshooting

Notifications Still Sending During Quiet Hours

Check These:

  1. Quiet Hours Enabled: Verify the toggle is on in Settings
  2. Correct Timezone: Ensure the timezone matches your expectations
  3. Time Window: Double-check start and end times
  4. Per-Streamer Override: Check if the streamer has "Ignore Quiet Hours" enabled

Summary Not Sending

Possible Causes:

  • No streams went live during quiet hours (nothing to summarize)
  • Bot doesn't have permission to send messages in the notification channel
  • Quiet hours window hasn't ended yet

Solutions:

  1. Wait for quiet hours to end
  2. Check bot permissions in the notification channel
  3. Verify there were queued notifications

Wrong Timezone Behavior

If notifications are being held at the wrong times:

  1. Go to Settings > Quiet Hours
  2. Verify the timezone is correct
  3. Remember that timezones adjust for daylight saving automatically
  4. Test by checking if current time is "within" quiet hours

How It Affects Metrics

Quiet Hours changes how notifications are counted:

MetricWhat It Shows
Notifications SentOnly delivered messages (not queued/skipped)
Analytics DashboardOnly delivered messages
Quiet Hours StatsSeparate tracking for queued/skipped

Example: If 50 streams go live during quiet hours:

  • Skip mode: 0 notifications sent, 50 skipped
  • Summary mode: 1 notification sent (the summary), 50 queued

Frequently Asked Questions

Does this work with all streamers?

Yes, Quiet Hours applies to all tracked streamers unless they have "Ignore Quiet Hours" enabled.

What happens if a stream starts before quiet hours and continues into them?

The notification is sent when the stream goes live. If that's before quiet hours, it sends normally. Quiet Hours only affects notifications that would be sent during the quiet window.

Can I have different quiet hours for different streamers?

Not directly. Quiet Hours is a guild-wide setting. However, you can use "Ignore Quiet Hours" on specific streamers to bypass the window.

Does the summary include streams that ended during quiet hours?

The summary includes streams that started during quiet hours. If a stream started before quiet hours, it was already notified.

What if no one streamed during quiet hours?

No summary is sent. Summaries only send when there are queued notifications.

Can I test quiet hours without waiting?

Currently, quiet hours are time-based. To test, you can temporarily set the window to include the current time and track when a streamer goes live.


Quiet Hours vs Notification Cooldowns

Both features help control notification frequency, but serve different purposes:

FeaturePurposeScope
Quiet HoursBlock notifications during specific timesTime-based, guild-wide
CooldownsPrevent rapid repeat notificationsPer-streamer, always active

Use Both Together:

  • Quiet Hours handles overnight/work hours
  • Cooldowns prevent spam from connection issues
  • They complement each other for complete notification control

Need Help?

Questions about Quiet Hours?

Our support team can help you configure the perfect quiet hours setup for your community.