Skip to content

Cooldown or Quiet Period

Timing rule — instantiates Signal Value Preservation

Enforces a minimum gap between firings — or a scheduled quiet window — so a channel cannot burst or nag its way into background noise even when many events qualify.

The Cooldown or Quiet Period spaces firings out in time: a minimum interval after each firing, a cap per rolling window, or protected quiet hours during which only critical signals pass. The one idea that makes it this mechanism is that it rations the channel along the time axis rather than in total volume — the same day's worth of alerts, spread out, reads as signal; bunched together, the identical set reads as spam. That temporal lever is what separates it from the quantity cap of a budget and the addressing logic of a routing filter. It buys value even when the underlying triggers can't be improved, because it attacks bursting, the fastest route to habituation.

Example

A consumer fitness app is losing users to uninstalls driven by its own push notifications — "You're close to your goal!", "Your streak is at risk!", several in an evening. Rather than cutting the content, the product team imposes cooldowns: at most one motivational push per user per day, none between 9pm and 8am (a protected quiet window echoing the phone's own Do Not Disturb), and a 72-hour cooldown on any notification type the user just dismissed. A qualifying trigger during a cooldown is coalesced or dropped rather than delivered. Open rates per notification recover, because each one now arrives when there is room for it — the channel stops feeling like nagging, which is what had been teaching users to swipe every push away unseen.

How it works

Each channel — or each individual receiver — carries a minimum inter-firing interval, an optional rolling-window cap, and optionally a set of protected quiet periods. A qualifying event that arrives inside a cooldown is dropped, queued, or coalesced with the pending firing rather than delivered immediately. Because the lever is spacing, even a flood of legitimately triggered events cannot collapse into a single overwhelming burst.

Tuning parameters

  • Cooldown length — the minimum gap between firings. Longer gaps protect attention but risk delaying a genuinely time-critical second event.
  • Scope — per-signal-type, per-channel, or per-receiver. Per-receiver spacing is the most faithful to real attention but requires per-user state.
  • Override rule — which classes (life-safety, security) may pierce the cooldown. A few exceptions are essential; too many dissolve the protection entirely.
  • Collision handling — drop, queue, or coalesce suppressed firings. Coalescing ("3 updates since you last looked") preserves the information a silent drop would lose.

When it helps, and when it misleads

Its strength is that it is the cheapest guard against burst-driven habituation, and it works without improving the underlying triggers at all — pure spacing. Its failure modes are that a cooldown can delay or drop a real, urgent second signal (a follow-on alarm arriving during the quiet window), and a blanket quiet period can mute a genuine emergency. It is also misused to paper over a systemic over-firing problem — spacing the noise instead of fixing why there is so much of it. The discipline that guards against this is to give life-safety classes an explicit bypass, prefer coalescing over silent drops, and treat any channel that is always saturating its cooldown as a signal to fix issuance upstream, not merely to space it.[1]

How it implements the components

  • channel_scarcity_policy — its core: it keeps the channel scarce along the time axis, so firings stay spaced and each one lands with room around it.
  • receiver_attention_budget — it spends the receiver's attention as a per-interval ration, refusing to draw it down twice in quick succession.

It does not set the total-volume quota or the credibility budget (credibility_budget) — that's Alert or Label Budget — nor measure whether fatigue is actually setting in (habituation_and_adaptation_monitor) — that's Receiver Fatigue Survey.

References

[1] Habituation — the well-established tendency of a repeated stimulus to elicit progressively less response. A channel that fires in bursts habituates its receivers fastest, which is why spacing firings out, rather than making each one louder, is the direct behavioral countermeasure. ↩