Use Quiet Hours to specify a period of time during which users shouldn't receive the campaign you're creating. Quiet Hours is enabled at the campaign level, and only applies to the campaign you're actively editing.
When Quiet Hours is enabled for a campaign, Iterable checks each user's local time before sending the campaign. If the send time in the user's time zone falls within your Quiet Hours window, Iterable holds the message instead of sending it. When the Quiet Hours window ends, Iterable can either send the message at the first eligible time or cancel the send.
You can set Quiet Hours for all campaign types: blast, triggered, and journey.
If you enable Quiet Hours and Send Time Optimization for a campaign, and a user's optimized send time falls within your Quiet Hours window, Iterable holds the send until the Quiet Hours window ends. For example, if Send Time Optimization selects 5:00 a.m., but Quiet Hours are from 9:00 p.m. to 9:00 a.m., the campaign will be sent at 9:00 a.m.
To pause campaign sends during a campaign's quiet hours, Iterable needs
to know each user's time zone. Their
timeZone user profile field provides this
information. For more information, see Sending in Different Time Zones.
When to use Quiet Hours
Some types of messages may not be urgent enough to send in the middle of the night. For these types of messages, consider using Quiet Hours. For example:
- Upcoming sale alerts
- Special offers
- Back-in-stock notices
Other types of messages — usually transactional — should be delivered immediately, no matter the time. These types of messages are not good candidates for Quiet Hours. For example:
- Fraud alert notices
- Two-factor authentication
- Delivery updates
Learn about other delivery optimization settings and how to enable Quiet Hours from the Campaign Review page in Optimizing Campaign Delivery.