Skip to content

Quiet hours

Quiet hours prevent messages from being sent during a specified time window. You can use them to avoid contacting users at inconvenient times (like overnight or early in the morning) while still sending at an optimal time outside that window.

How quiet hours work

You can configure quiet hours at the campaign or Canvas level in the campaign or Canvas composer. When quiet hours are enabled and a message would otherwise be sent during the restricted window, Braze holds the message and delivers it at the next available time after quiet hours end.

For example, if quiet hours run from 10 pm to 6 am and a message is scheduled for 5:30 am, Braze delivers it at 6 am instead.

Quiet hours and Intelligent Timing

Quiet hours and Intelligent Timing operate independently. Enabling quiet hours does not require Intelligent Timing to be on, and the same is true in reverse. In general, we recommend choosing one or the other rather than using both together, unless there are policy, compliance, or other requirements that make quiet hours necessary alongside Intelligent Timing.

  • Without Intelligent Timing: Quiet hours act as a no-send window for your scheduled send time. If the scheduled time falls within quiet hours, the message is held and sent when the window closes.
  • With Intelligent Timing: Braze still calculates each user’s optimal send time. If that time falls within quiet hours, the message is held and delivered at the nearest edge of the quiet window instead.

For more information on configuring quiet hours within an Intelligent Timing campaign, see Intelligent Timing.

Quiet hours and API sends

Quiet hours also apply to messages you send through the REST API. The following table shows which window applies to each send type and what happens when a message falls in quiet hours.

Send type Quiet hours that apply If the send time falls in quiet hours
API-triggered campaign The campaign’s quiet hours, or workspace quiet hours for the channel Braze doesn’t send the message.
API-triggered Canvas The Canvas or Message step quiet hours, or workspace quiet hours for the channel Braze follows the Canvas fallback setting (Abort message or Send at next available time).
API campaign (/messages/send or /messages/schedule/create) Workspace quiet hours only. Campaign-level quiet hours don’t apply. Braze doesn’t send the message. To send anyway, set ignore_workspace_quiet_hours to true in a request to the /messages/send endpoint.
  • API-triggered campaigns don’t hold messages. The Send at next available time option is only available for action-based campaigns, so Braze doesn’t send a message that falls in quiet hours. To deliver outside quiet hours, schedule the send for a time outside the window, or use at_optimal_time, which factors quiet hours into each user’s send time.
  • The API call still succeeds. Braze checks quiet hours when it processes the send, after it returns the API response. If quiet hours stop a message, the API doesn’t return an error. These messages appear in the Message Activity Log.

Considerations

  • Messages send at the same time when quiet hours end. If a large audience has messages held during quiet hours, all of those messages send at once when the window closes. For time-sensitive campaigns, consider how this affects delivery timing.
  • Quiet hours are not the same as aborting a message. Aborting a message discards it entirely. Quiet hours hold the message and deliver it later.
  • Quiet hours do not re-evaluate segment membership for a held send. Braze checks segment membership when the message is triggered. If the user is eligible then, Braze holds the message and sends it when quiet hours end. This is separate from re-evaluating segment membership at send-time or Canvas delivery validations.
  • Quiet hours are separate from frequency capping and rate limiting. Each of these delivery controls applies independently. A message that clears frequency and rate limits can still be held by quiet hours, and a message held by quiet hours is evaluated against frequency capping and rate limits when it eventually sends. For how Braze evaluates frequency capping relative to quiet hours, see When frequency capping is checked.
New Stuff!