These two settings look similar and mean opposite things. Getting them the wrong way round is one of the few configuration mistakes in this product that can hide a genuine emergency, so it's worth thirty seconds.
| Store hours | Quiet hours | |
|---|---|---|
| Belongs to | A store | A person |
| Describes | When the building is occupied and heat threatens somebody | When that person would rather not be woken |
| Effect on an alert | Alerts outside opening hours are held and delivered when the store opens | Non-urgent notifications wait; the level still escalates underneath |
The reasoning behind holding off-hours alerts: at 3am in a closed restaurant there is nobody to protect, and waking a manager teaches them to mute the next one. The reading is still recorded, and it still counts toward your compliance record — it simply doesn't page anyone at the moment when paging serves no purpose.
You can see it rather than having to trust it. Each unit — on its own page and on its dashboard card — shows the store's own wall clock and whether it is open right now. A company spanning four time zones cannot do that arithmetic in its head, and a red reading at a closed restaurant means something entirely different from the same reading at one mid-shift.
- Hours and timezone are set on the store, under Stores & locations — open the store and edit it there.
- A store with no hours set says so, because it is treated as open around the clock: alerts fire at 3am, and a cellular unit reports on the faster, costlier cadence all night.
- The clock is the store's, not yours. A manager in Louisville and one in Los Angeles see the same store showing the same local time.