Send Windows Map
A thematic guide to how we study when notifications should land—then turn that study into a calendar your team can keep.
What a send window is
A send window is a stretch of hours when a defined audience is more likely to open and act on a notification. It is not a single magic minute. It is a protected range you schedule into—and a set of hours you deliberately leave alone.
Morning lift
Often strong for transactional confirmations and planning prompts when people first check devices.
Midday trough
Meetings and lunch can flatten opens; useful for low-urgency digests that can wait.
Evening recovery
In Bangkok, early evening dips often recover later—worth measuring before cutting.
How we walk a timing engagement
Every project follows a clear path from inventory to a usable schedule.
1. Stream inventory
List live notification types, channels, owners, and current schedule rules.
2. Clock audit
Confirm which timestamps analytics trust—device, locale, or server—before drawing conclusions.
3. Window discovery
Map opens and same-day actions by hour and cohort; mark holidays separately.
4. Quiet-hour policy
Define silence and the few alert classes allowed to break it.
5. Cadence check
If frequency is the question, design a fair experiment rather than stacking more sends.
Want this map applied to your streams?
Browse services or tell us which notifications feel poorly timed.