Quiet hours are often a paragraph in a policy and a rumour in the send panel. Someone heard that nothing should go out after 21:00. Someone else has a flash sale that “has to” land when inventory drops. The lock screen does not care about the policy document.
Read dismissals by hour first
Before you legislate, ask for a week of dismissals (or shade-clears, or whatever your vendor named the “go away” event) split by hour. In several Klang Valley programmes we have read, the angry hour was not midnight. It was 19:30 to 20:30, when a household phone is on the table and a tuition reminder collides with a grocery promo. The 22:00 cap, faithfully copied, was protecting a quieter part of the night and missing the argument.
Transactional exceptions need names
A card-decline alert is not a hamper. If your quiet-hour rule cannot name the exceptions, the exceptions will be improvised by whoever is on shift. Improvised exceptions become a second programme. We have sat with banks where “security” was the magic word that let a marketing template through. The user only saw two pings.
A modest experiment
Pick seven days. Hold the commercial sends inside a window you actually observed in the dismissal file. Leave true account alerts outside it. Do not change copy at the same time. If the opt-out line does not move, your problem was never the clock.
This is the sort of question a team briefing can hold in a morning, provided you bring the hourly file and not a vibe.