Quiet hours

Quiet hours are the tenant-wide window in which outbound campaign sends are deferred. A campaign scheduled to fire inside the quiet window holds and starts at the next allowed time outside the window.

Transactional and authentication category templates are exempt — they fire regardless of quiet hours so password resets, OTPs, and order confirmations always reach the customer.

Configuring the window

1. Settings → Quiet hours.
2. Start (local time) — when outbound campaigns should pause. Default 22:00.
3. End (local time) — when sending can resume. Default 08:00.
4. Timezone (IANA) — the timezone the start and end times are evaluated against (e.g. Asia/Dubai, Asia/Riyadh). Daylight savings is handled automatically.
5. Default drift threshold (%) — applies per campaign on creation; range 10–50. When a campaign’s resolved audience size differs from its creation-time estimate by more than this percentage, the campaign holds for admin review instead of launching.
6. Click Save.

The window wraps midnight: 22:00 → 08:00 means “from 10 PM tonight to 8 AM tomorrow.”

How a deferred send resolves

When a campaign is scheduled inside the quiet window:

1. The send is held — not cancelled.
2. At the end of the window, the campaign starts as if it had been scheduled for that moment.
3. The audit log captures the original time, the defer reason, and the actual launch time.

Drift threshold

The drift threshold isn’t strictly about quiet hours — it’s the per-campaign safety check that lives on this page because campaign admins manage it together with the quiet window.

When a campaign is created, CraftBot estimates the audience size. At launch time, the audience is re-resolved against the current contact database. If the new size deviates by more than the threshold (default 25%), the campaign holds for admin review instead of launching. This catches:

• Audience filters that turned out broader than expected.
• Sudden contact list inflation (e.g. an import that just landed).
• Stale estimates on long-deferred campaigns.

Each campaign can override the default on creation, within the 10–50 range.

Best practices

• Pick a tight quiet window. 22:00 → 08:00 is the launch default and covers most use cases.
• Keep the timezone matched to the audience’s local time, not the operator’s. A Saudi-Arabia-only tenant uses Asia/Riyadh; a multi-region tenant picks the timezone of the majority audience.
• Don’t loosen the drift threshold to suppress holds. If your audience estimates keep failing, fix the audience definitions — the hold is doing its job.
• Use Blackout dates for full-day stops, quiet hours for nightly windows. They compose: a campaign on a blackout date is skipped entirely, and on a non-blackout date it respects the quiet window.