AJO quiet hours now cover everything – and the 2 a.m. text becomes a leadership decision

One corner of Adobe’s marketing platform used to ignore night-time sending rules. On August 18, Adobe closed it. Since then, every 2 a.m. text a bank sends is a decision – not a technical excuse.

Quiet hours in Journey Optimizer block messages during set time windows – across email, SMS, push and WhatsApp. The feature has been generally available since January 29, 2026. What changed in August: Orchestrated Campaigns, AJO’s batch campaign type and the last exempt send type, now support quiet hours too. One protection now covers campaigns, journeys and batch orchestration alike.

What shipped, exactly

• January 29, 2026 – GA: quiet-hours rules in rule sets for email, SMS, push and WhatsApp; queue or discard per rule; preview of the activated rule.
• August 18, 2026 – Orchestrated Campaigns: the earlier “not supported for Orchestrated campaigns” limitation is gone.
• Timezone logic: one fixed window for all recipients, or the recipient’s local time from the profile timezone field.

One night under quiet hours

Picture a German retail bank, six million customers, quiet hours set to 21:00–08:00. The featured architecture above walks through a single night:

1. 20:55 – a payment-reminder SMS batch starts; part of it gets out before the window.
2. 21:00 – the rest is held automatically and waits. The rule says queue, not delete.
3. Classification – every action has been classified beforehand: marketing, service or security – hold, drop or bypass. This is the human decision in the middle of the diagram.
4. 03:12 – a card gets flagged; the fraud alert carries no quiet-hours rule and fires immediately.
5. 08:00 – the held reminders release into the morning.

The expensive part is step three – and it isn’t software. The platform cannot know which message is marketing noise and which one means “your card just got blocked.” Someone has to classify everything the company sends, across every channel and every team. A CMO who skips that inventory gets the dark side of the switch: fraud alerts held politely until breakfast.

The architecture behind it

The setup path in AJO: Journey Optimizer → Business rules → custom rule set (Channel domain – the global rule set can’t hold quiet hours) → Add rule → type Quiet hours. Up to five time periods per rule, weekly or custom dates, optional all-day. Choose queue or discard, activate, then attach the rule set per channel action – in campaigns via the Actions tab, in journeys on the channel action itself.

Architecturally, quiet hours are opt-in per action: the rule category is read-only “Marketing”, so service and security actions bypass the window by simply not carrying the rule. That is the mechanism that lets the fraud alert through at 03:12 – and the reason the classification inventory is the real project, not the rule setup.

The fine print

• A profile with no timezone value is not protected – the rule silently doesn’t apply.
• Messages queued for more than seven days are discarded.
• Discard on a journey action means the profile exits the journey entirely.
• Rule updates take up to 12 hours to reach actions already using the rule – tonight’s window can’t be fixed this afternoon.
• On high-volume sends, suppression enforcement can lag; quiet-hours exclusions show up in the CJA channel report and the Live report.

Six questions to settle before switching it on

1. Who owns the classification list – which sends are marketing, service, security?
2. Hold or drop per message class – and what does a dropped payment reminder do to the dunning process downstream?
3. How many profiles carry no timezone value today? That is the share of your base with zero protection.
4. Fixed window vs. recipient local time – one national market may not need profile timezones; twelve markets do.
5. Who monitors the queue – which held messages are approaching the 7-day discard?
6. Does anything downstream assume the message went out the moment the journey passed the action?

Quiet hours aren’t a politeness setting. They’re a forced decision about which messages matter at 3 a.m. – and that decision belongs to the business, not the platform.

Also from AJO’s August release: the journey-level holdout – the feature that sends nothing and proves everything.

Frequently asked questions

Which send types do quiet hours cover in Journey Optimizer?

Since 18 August 2026, Orchestrated Campaigns as well – the last exempt send type. Quiet hours have been generally available since 29 January 2026 for email, SMS, push and WhatsApp, so one protection now covers campaigns, journeys and batch orchestration alike.

Do quiet hours apply to every profile?

No. A profile with no time zone value is not protected and the rule silently does not apply. Quiet hours are also opt-in per action: the rule category is read-only Marketing, so service and security actions bypass the window simply by not carrying the rule. That is the mechanism that lets a fraud alert through at three in the morning.

What happens to messages that quiet hours hold back?

Per rule they are either queued or discarded. Messages queued for more than seven days are discarded. A discard on a journey action means the profile exits the journey entirely. And rule updates take up to 12 hours to reach actions already using the rule, so tonight’s window cannot be fixed this afternoon.

Sources: Adobe Journey Optimizer release notes (August 2026 section and 2026 archive) and “Set quiet hours” on Adobe Experience League – fetched August 31, 2026. Adobe, Adobe Journey Optimizer and Real-Time CDP are trademarks of Adobe Inc. This is an independent analysis; no partnership with or endorsement by Adobe.