Attention is a budget. Spend it carefully.
I watched a list do real work and still get smaller most weeks. Frequency caps treated everyone the same. That was not enough.
Talk to usSame count, different risk
Two people who received three notifications today may have very different fatigue risk. One clicked all three. The other ignored the last ten. A simple frequency cap treats them the same.
Why frequency caps alone are not enough
Caps limit volume, but they do not understand relevance or recent behavior. EngageNudge also considers ignored streaks, recent clicks, topic cooldowns, quiet hours, and how relevant the current story is before recommending a send.
- Protect overexposed people who keep ignoring notifications.
- Suppress weak-relevance sends even when the daily cap has room.
- Respect quiet hours and topic-specific cooldowns.
- Allow explicit breaking-news overrides when urgency matters.
Fatigue protection
Daily and weekly exposure limits
Set boundaries on how often anyone can be reached in a given period.
Minimum time between Nudges
Prevent back-to-back interruptions even when stories keep publishing.
Ignored-streak signals
People who repeatedly ignore notifications get rested automatically.
Dormant protection
Do not waste sends on subscribers who have not engaged in a long time.
Topic-specific cooldown
Avoid sending three football Nudges in a row to the same segment.
Quiet hours
Respect when people are unlikely to welcome an interruption.
Breaking-news override
Teams can explicitly override fatigue rules when urgency is real and auditable.
Opt-out monitoring
Track opt-outs and invalid endpoints so fatigue does not turn into churn.
You stay in control
Fatigue rules are transparent and versioned. You see who is protected and why. The system recommends restraint. You decide whether to send.
Know when to nudge.
Know when a notification is worth sending.
The useful question is who should not get this one.