# Quiet hours can now be bypassed for transactional traffic

> A new value for window.quiet_hours lets codes, alerts and receipts leave at any hour while marketing keeps waiting for the local window.

Published 2026-09-14 by SMSMeteor Product team.

Quiet hours exist for marketing. A verification code at 23:40 is not marketing, and holding it until 08:00 helps nobody. Until now the only way around the default window was to disable quiet hours for the whole campaign, which meant losing them for the marketing part of a mixed send.


From today, `window.quiet_hours` accepts a third value, `bypass`. Messages flagged this way are treated as transactional: they leave immediately, in every destination, whatever the local hour. The default behaviour for everything else is unchanged.



## How to use it

In the composer, tick Transactional on the schedule step. In the API, set `"window": { "quiet_hours": "bypass" }` on a message or on a batch. The flag is recorded on the message and shown in reports, so you can audit what was sent outside the window and why.



## What it is not

It is not a way to send marketing at night. Our acceptable use policy already treats promotional content sent as transactional as abuse, and the content filters that decide what is promotional apply regardless of the flag. If a campaign flagged transactional starts looking like a sale, expect a message from us.

---
Source: https://smsmeteor.com/blog/quiet-hours-bypass-for-transactional (HTML). Generated by SMSMeteor from the same data as the page. Summary of the whole site: https://smsmeteor.com/llms.txt