Send Blockouts

Set a period during which your MobileConnect account doesn’t send outgoing messages, such as when subscribers might be asleep. This feature prevents you from scheduling sends or beginning an immediate send during a specified send blockout period.

MobileConnect prevents you from sending immediately during the send blockout, based on the time zone set for your account within Marketing Cloud Engagement. MobileConnect also prevents you from scheduling a send that starts during the send blockout in any time zone. Sends don’t pause at the send blockout. For example, if your send starts at 9 PM and takes two hours, and your send blockout starts at 10 PM, the send continues into the send blockout time period until 11 PM.

Any send blockout time specified in the MobileConnect app doesn’t affect sends conducted using MobileConnect API calls. Specify blockout times separately on the API call for your message. Any messages triggered during an API send blockout window occur after the send blockout period elapses. If you attempt to send during the blockout window, the message is scheduled to send one second after the blockout window ends.

Note
Note

In Journey Builder, a send blockout window completely prevents messages from sending. Messages don’t queue for sending at a later time. Send blockouts set in Journey Builder are independent of send blockouts set in MobileConnect. Journey Builder doesn't honor blockouts set in MobileConnect.

In Journey Builder, when you set a send blockout window for an SMS activity, the displayed current account time doesn't automatically adjust for Daylight Savings Time (DST).