Quiet Hours & Frequency Capping: Send Web Push Without Annoying Users

The fastest way to ruin a healthy web push channel is to send too much, too often, at the wrong time. A 2 a.m. buzz or the fifth notification of the day teaches subscribers one lesson: tune you out. Quiet hours and frequency capping are the two guardrails that keep your list engaged, your click-through rates strong, and your unsubscribe rate low.

This guide walks through how to implement both, plus the cadence guidance that ties them together.

Why Restraint Beats Volume

Web push works because it reaches subscribers outside your app or site. That reach is a privilege, not a right. Every notification spends a little of the trust a user gave you when they clicked "Allow."

Send too often and three things happen:

• Click-through rate drops. Fatigued users swipe notifications away without reading. Healthy web push CTRs typically land in the low single digits to low double digits depending on relevance — over-sending pushes you toward the bottom of that range.
• Unsubscribes climb. On most browsers, blocking a site's notifications is permanent and hard to reverse. A lost subscriber is usually lost for good.
• Browser-level penalties appear. Persistent over-messaging can hurt how a site's notifications are surfaced.

Capping and quiet hours are how you protect the channel from your own enthusiasm.

Frequency Capping: Per-User Daily Limits

A frequency cap is a hard ceiling on how many notifications a single subscriber can receive in a window — usually per day, sometimes per week.

Good starting points:

• 1–2 per day for most consumer audiences (news, e-commerce, content).
• Up to 3–4 per day only for high-intent, opted-in use cases like price-drop alerts or breaking news, where users expect frequency.
• A weekly cap as a backstop, so a burst of triggered campaigns can't stack into a bad week even if daily limits technically pass.

The key word is per-user. A global "we'll send three campaigns today" rule ignores that one subscriber might match all three segments and another none. Track sends at the individual subscription level and stop delivering once a user hits their ceiling — regardless of how many campaigns are in flight.

It also helps to prioritize. When transactional and marketing messages compete for the same slot, let the transactional one win. Capping should drop the least important message, not a random one.

With relaybell, frequency rules apply across all your campaigns automatically, so a user enrolled in several segments never gets buried.

Timezone-Aware Quiet Hours

A quiet window is a span of the day when you never deliver — typically overnight. The catch: "overnight" depends entirely on where the subscriber is.

If you schedule against your own server time, a 9 a.m. send in your office is the middle of the night for someone eight zones away. The fix is to store each subscriber's timezone (inferred at opt-in from the browser, or from their profile) and evaluate quiet hours against their local clock.

A sensible default quiet window is roughly 9 p.m. to 8 a.m. local time. Within quiet hours you have two choices:

• Hold and release — queue the message and deliver it when the window opens, so morning subscribers get a fresh batch instead of a 3 a.m. ping.
• Drop — skip time-sensitive messages whose value expires (a flash sale ending overnight) rather than delivering them stale.

Hold-and-release is the safer default for most content.

Cadence Guidance That Keeps Lists Healthy

Caps and quiet hours are the floor. Cadence is the strategy on top.

• Earn frequency with relevance. A perfectly targeted message can be sent more often than a generic blast without fatiguing anyone. Segmentation is your best frequency tool.
• Warm up new subscribers. Don't hit a day-one opt-in with your maximum cadence. Ease in over the first week.
• Watch the leading indicators. Rising dismiss rates and falling CTR show fatigue before unsubscribes spike. Treat them as your early-warning system and pull back.
• Pick your best window. Mid-morning and early evening tend to perform well for consumer audiences — test against your own data rather than assuming.
• Give users control. A simple preference center (daily digest vs. real-time, topic opt-outs) lets people self-select a cadence they'll tolerate, which beats guessing.

Putting It Together

The model is layered: relevance decides whether to send, the per-user cap decides if there's room, and quiet hours decide when. Run every notification through all three gates and you protect both engagement and the long-term size of your list.

Restraint isn't the opposite of a high-performing push program — it's the foundation of one.

Ready to try web push with quiet hours and frequency caps built in? Get started with relaybell — free to deliver, live in minutes.